WO2015193988A1 - 計算機システム - Google Patents
計算機システム Download PDFInfo
- Publication number
- WO2015193988A1 WO2015193988A1 PCT/JP2014/066112 JP2014066112W WO2015193988A1 WO 2015193988 A1 WO2015193988 A1 WO 2015193988A1 JP 2014066112 W JP2014066112 W JP 2014066112W WO 2015193988 A1 WO2015193988 A1 WO 2015193988A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- time
- data store
- request
- information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1023—Server selection for load balancing based on a hash applied to IP addresses or costs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/282—Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
Definitions
- the present invention relates to a computer system and a management method for managing access to a plurality of types of data necessary for system monitoring.
- Virtualization technology has also become widespread in networks, and network monitoring has become complicated. Therefore, in the network monitoring system, there is a demand for grasping various types of detailed data for network monitoring processing and failure analysis processing. More specifically, there is a demand for grasping data and history data collected in real time.
- various types of data are stored in the data store.
- the user can acquire data from the data store according to the contents of the monitoring process.
- Patent Document 1 describes “a query issuing unit 11a that makes a query in a database language from a client computer 10-1, a DBMS server group 23 that manages a plurality of different types of databases on a server computer 13, and a non-management that manages a plurality of different types of data.
- the query from the DBMS server group 24 and the query issuing unit 11a is converted into a database language specific to the corresponding DBMS, or converted into a specific access method, and an access request is issued to the DBMS server group 23 or the non-DBMS server group 24
- a multimedia database access unit 14 for returning the access result to the client computer 10-1, and accessing the multimedia database 15 composed of a plurality of different types of DBMS and non-DBMS in a unified manner by a database language. It has been described. As a result, multimedia data including a plurality of different types of databases can be uniformly accessed from applications on the client computer.
- the log is stored in the data store as it is. Therefore, when aggregated data is required, the computer that has received the request needs to execute two processes, a search process and an aggregate process. Therefore, data cannot be acquired efficiently.
- a method of constructing a data store for each aggregation process can be considered.
- management of the data store becomes complicated. Therefore, the user cannot determine from which data store the data should be acquired.
- Patent Document 1 can acquire data from a plurality of databases or non-databases that manage different types of data, but cannot efficiently acquire data in a computer system that requires complicated data management.
- the user needs to grasp the attributes of data stored in the data store in advance, in a computer system having a plurality of data stores that are dynamically updated and manage data for each of a plurality of aggregation processes, It is difficult to grasp the attributes of data stored in the store.
- the present invention provides a system and method capable of specifying an appropriate data store and acquiring data from the data store without making the user aware of the attribute of data stored in the data store, particularly the time attribute.
- the purpose is to do.
- a typical example of the invention disclosed in the present application is as follows. That is, a computer system including a plurality of computers and a management computer, wherein each of the plurality of computers includes a first processor, a first memory connected to the first processor, and the first processor. A first network interface to be connected; and the management computer includes a second processor, a second memory connected to the second processor, and a second network interface connected to the second processor.
- a plurality of data stores are configured using the plurality of computers, and each of the plurality of data stores stores data obtained from a data source and having different attributes
- the management computer receives a data acquisition request for acquiring request data from the plurality of data stores, and receives the data acquisition.
- a request distribution unit that determines a data store that acquires the request data by analyzing the request; and metadata management information that includes a time attribute of data stored in each of the plurality of data stores, and the request
- the distribution unit receives the data acquisition request including the time attribute of the request data
- the distribution unit refers to the metadata management information based on the analysis result of the data acquisition request, selects a candidate data store, and selects the candidate It is determined whether the request data can be acquired from a data store, and based on the determination result, a data store that issues a request for acquiring the request data is determined, and the determined data store It is characterized by issuing a request.
- the management computer acquires request data from the plurality of data stores based on an arbitrary data acquisition request. You can decide which data store to use.
- FIG. 3 is a block diagram illustrating an example of a hardware configuration and a software configuration of a computer according to the first embodiment.
- FIG. 3 is a block diagram illustrating a processing flow in the computer system according to the first embodiment. It is explanatory drawing which shows an example of real-time statistical data_metadata of Example 1. It is explanatory drawing which shows an example of the historical statistics data_metadata of Example 1. FIG. It is explanatory drawing which shows an example of raw data_metadata of Example 1. 6 is a flowchart illustrating an example of processing executed by a metadata setting unit according to the first embodiment.
- FIG. 10 is an explanatory diagram illustrating an example of a setting command for setting metadata in the metadata_database according to the first embodiment.
- 6 is a flowchart illustrating an outline of processing executed by a request distribution unit according to the first embodiment.
- 6 is a flowchart illustrating an example of a data store determination process according to the first embodiment.
- 6 is a flowchart illustrating an example of a data store determination process according to the first embodiment.
- 6 is a flowchart illustrating an example of a request determination process according to the first embodiment. It is explanatory drawing which shows an example of the data acquisition request of Example 1.
- FIG. 10 is an explanatory diagram illustrating an example of a setting command for setting metadata in the metadata_database according to the first embodiment.
- 6 is a flowchart illustrating an outline of processing executed by a request distribution unit according to the first embodiment.
- 6 is a flowchart illustrating an example of a data store determination process according to the first embodiment.
- 6 is a flowchart
- FIG. 6 is a flowchart illustrating an example of processing executed by an output processing unit according to the first embodiment. It is a block diagram explaining the flow of a process in the computer system of Example 2.
- FIG. 10 is a flowchart illustrating an example of processing executed by a data store management unit according to the second embodiment.
- FIG. 1 is a block diagram illustrating a configuration example of a computer system according to the first embodiment.
- the computer system includes a plurality of computers 100, 110, 120, and 130 and a plurality of client terminals 140.
- the computer 100, the plurality of computers 110, the plurality of computers 120, the plurality of computers 130, and the plurality of client terminals 140 are connected to each other via a network 160.
- the network 160 may be any network as long as the computer 100, the plurality of computers 110, 120, and 130 and the plurality of client terminals 140 can communicate with each other.
- the type of network may be either WAN or LAN, and the network connection method may be either wireless or wired.
- the client terminal 140 is a computer used by a user, and includes hardware such as a processor (not shown), a memory (not shown), a network interface (not shown), and the like.
- the client terminal 140 operates a display unit 141 for referring to various data and displaying the data.
- the user transmits a data acquisition request to the computer 100 using the display unit 141 and inputs various information.
- Each of the plurality of computers 110, 120, and 130 is a computer that constitutes a data store that stores various types of data.
- a plurality of computers 110 are used to configure one or more data stores
- a plurality of computers 120 are used to configure one or more data stores
- a plurality of computers 130 are used to configure one or more data stores.
- a plurality of data stores are managed as one data store group.
- Data acquired from the data source 150 is managed in the data store.
- the data source 150 indicates an acquisition source of data managed in the data store group.
- the data center corresponds to the data source 150.
- the sensor corresponds to the data source 150.
- a switch or the like constituting the network corresponds to the data source 150.
- Each of the plurality of computers 110 is a computer that acquires real-time data from the data source 150 and manages real-time statistical data calculated using the acquired real-time data. That is, each computer 110 is a computer that implements a data store that stores real-time statistical data. Each computer 110 has a real-time data totaling unit 111.
- the real-time data totaling unit 111 manages a data store that stores real-time statistical data. Specifically, the real-time data aggregation unit 111 calculates real-time statistical data by aggregating real-time data acquired from the data source 150 every predetermined aggregation unit time according to a previously specified aggregation process, and the buffer 112 Real-time statistical data is stored in In the real-time data totaling unit 111, a holding time is set as a parameter for determining the time range of the real-time statistical data stored in the buffer 112. The buffer 112 stores real-time statistical data from the current time to the time that goes back the holding time.
- the real-time data totaling unit 111 generates real-time statistical data using the real-time data, and stores the generated real-time statistical data in the computer 120. Further, when receiving a request from the computer 100, the real-time data totaling unit 111 reads the real-time statistical data stored in the buffer 112 in accordance with the request, and transmits the read real-time statistical data to the computer 100 as a response.
- Each of the plurality of computers 120 is a computer that manages the history of real-time statistical data. That is, each computer 120 is a computer that implements a data store that stores a history of real-time statistical data. Each computer 120 includes a database management unit 121 and history statistical data_database 122. In the following description, the history of real-time statistical data is also referred to as historical statistical data.
- History history data_database 122 stores history statistics data.
- the database management unit 121 manages a data store that stores historical statistical data.
- the database management unit 121 stores the real-time statistical data received from the real-time data totaling unit 111 in the historical statistical data_database 122. Further, when receiving a request from the computer 100, the database management unit 121 reads the historical statistical data from the historical statistical data_database 122 according to the request and transmits the read historical statistical data to the computer 100 as a response.
- the history statistical data may be a history of data other than real-time statistical data.
- the database management unit 121 may acquire data from the data source 150 and store statistical data calculated by executing predetermined statistical processing as historical statistical data.
- the database management unit 121 may acquire raw data from a computer 130 described later and store statistical data calculated by executing predetermined statistical processing as historical statistical data.
- Each of the plurality of computers 130 is a computer that manages raw data acquired from the data source 150.
- the raw data refers to real-time data itself acquired from the data source 150. That is, each computer 130 is a computer that implements a data store that stores raw data.
- Each computer 130 includes a database management unit 131 and a raw data_database 132.
- Raw data_database 132 stores raw data from the present to the past.
- the database management unit 131 manages a data store that stores raw data.
- the database management unit 131 acquires raw data from the data source 150 and stores the acquired raw data in the raw data_database 132. Further, when receiving a request from the computer 100, the database management unit 131 reads the raw data from the raw data_database 132 according to the request, and transmits the read raw data to the computer 100 as a response.
- each data store constituting the data store group of the first embodiment data having different data attributes such as total contents, total unit time, and retention time are managed.
- the computer 100 specifies a candidate data store as a data acquisition destination based on the data acquisition request transmitted from the display unit 141.
- the identified candidate data store is also referred to as a candidate data store.
- the computer 100 determines whether or not data can be acquired from the candidate data store, and determines a data store from which data is acquired based on the determination result.
- the computer 100 has a data store management unit 101.
- the data store management unit 101 manages access processing for data stores included in the data store group.
- the data store management unit 101 includes a metadata setting unit 102, a request distribution unit 103, an output processing unit 104, and a metadata_database 105.
- the metadata setting unit 102 sets metadata indicating attributes of data stored in the data store.
- the request distribution unit 103 receives a data acquisition request from the display unit 141, the request distribution unit 103 specifies a data store that acquires data that is a target of the request, and issues a request to the specified data store.
- the output processing unit 104 generates response information using the data acquired from the data store, and transmits the generated response information to the display unit 141.
- the metadata_database 105 stores metadata for managing attributes of data stored in the data store.
- FIG. 2 is a block diagram illustrating an example of a hardware configuration and a software configuration of the computer 100 according to the first embodiment.
- the computer 100 includes a processor 201, a memory 202, a storage device 203, and a network interface 204.
- the processor 201 executes a program stored in the memory 202.
- the functions of the computer 100 can be realized by the processor 201 executing the program.
- the processing when the processing is mainly described with respect to a program, it indicates that the program is being executed by the processor 201.
- the memory 202 stores a program executed by the processor 201 and various information necessary for executing the program.
- the memory 202 stores programs that realize the metadata setting unit 102, the request distribution unit 103, and the output processing unit 104.
- the memory 202 stores the metadata_database 105.
- the storage device 203 stores various programs and various information used by the computer 100. Programs and information stored in the memory 202 may be stored in the storage device 203. In this case, the processor 201 reads a program and information from the storage device 203, loads the program and information into the memory 202, and executes the program loaded on the memory 202.
- the network interface 204 is an interface for connecting to a network.
- the computers 110, 120, and 130 also have the same hardware configuration as the computer 100. However, the programs and information stored in the memory 202 and the storage device 203 are different. Specifically, a program for realizing the real-time data totaling unit 111 is stored in the memory 202 of the computer 110. A program for realizing the database management unit 121 is stored in the memory 202 of the computer 120, and history statistical data_database 122 is stored in the storage device 203. A program for realizing the database management unit 131 is stored in the memory 202 of the computer 130, and a raw data_database 132 is stored in the storage device 203.
- the data store is realized as a disk store using the storage area of the storage device 203, but the data store may be realized as a memory store using the storage area of the memory 202.
- FIG. 3 is a block diagram illustrating a processing flow in the computer system according to the first embodiment.
- the data store management unit 101 has a plurality of dedicated adapters 304 for accessing each data store.
- the data store management unit 101 transmits a request to each data store using each adapter 304 and receives data from each data store.
- the data store management unit 101 includes three adapters 304-1, 304-2, and 304-3.
- the adapter 304-1 is an adapter for acquiring the real-time statistical data 310 managed by the real-time data totaling unit 111.
- the adapter 304-2 is an adapter for acquiring the historical statistical data 320 managed by the database management unit 121.
- the adapter 304-3 is an adapter for acquiring the raw data 330 managed by the database management unit 131.
- the metadata setting information 350 is input to the data store management unit 101 in advance. Based on the input metadata setting information 350, the metadata setting unit 102 sets metadata indicating the attribute of data managed in the data store group in the metadata_database 105.
- the metadata setting unit 102 sets real-time statistical data_metadata 301, historical statistical data_metadata 302, and raw data_metadata 303 in the metadata_database 105.
- Real-time statistical data_metadata 301 is real-time statistical data metadata managed by the computer 110.
- the historical statistical data_metadata 302 is metadata of historical statistical data managed by the computer 120.
- Raw data_metadata 303 is metadata of raw data managed by the computer 130.
- Metadatabase 105 Details of the metadata_database 105 including real-time statistical data_metadata 301, history statistical data_metadata 302, and raw data_metadata 303 will be described later with reference to FIGS.
- the data store management unit 101 When the data store management unit 101 receives a data acquisition request from the display unit 141, the data store management unit 101 operates as follows.
- the request distribution unit 103 analyzes the data acquisition request.
- the request distribution unit 103 refers to the metadata_database 105 based on the analysis result and determines a data store from which data is acquired.
- the request distribution unit 103 outputs a request issue instruction to the adapter 304 for accessing the determined data store.
- the adapter 304 When the adapter 304 receives a request issuance instruction, the adapter 304 issues a request to the data store based on the instruction and acquires data from the data store. The adapter 304 outputs the acquired data to the output processing unit 104.
- the output processing unit 104 generates response information using the analysis result of the data acquisition request and the data input from each adapter. At this time, if necessary, the output processing unit 104 generates data requested by the data acquisition request by processing the data acquired from the data store. The output processing unit 104 transmits the response information generated on the display unit 141.
- the first embodiment is characterized in that the request distribution unit 103 determines a data store from which data is acquired based on the analysis result of the data acquisition request and the metadata_database 105.
- the request distribution unit 103 is characterized in that data requested by a data acquisition request is generated using data stored in the data store.
- FIG. 4 is an explanatory diagram illustrating an example of real-time statistical data_metadata 301 according to the first embodiment.
- the real-time statistical data_metadata 301 of the first embodiment is data in a table format, and includes a process name 401, a column name 402, a total content 403, a total unit time 404, and a holding time 405. Note that the real-time statistical data_metadata 301 may include columns other than the columns described above.
- the process name 401 is the name of the aggregation process executed by the real-time data aggregation unit 111.
- the column name 402 is the content of the real-time statistical data 310 that is totaled by the real-time data totaling unit 111.
- the total content 403 is the content of the total processing executed by the real-time data totaling unit 111.
- the total content 403 stores, for example, a totalization function.
- the total unit time 404 is a total time interval in the totaling process.
- the holding time 405 is a time width of the real-time statistical data 310 held in the buffer 112 of the real-time data totaling unit 111.
- the metadata corresponding to the first entry in FIG. 4 is a data store that manages, as the real-time statistical data 310, the usage rate calculated by summing the packet sizes in units of one second. Also, it can be seen that the data store stores the utilization rate from the current time to the time going back one minute in the past.
- the metadata corresponding to the second entry in FIG. 4 indicates that the data store manages the number of packets calculated by measuring the number of packets per second as the real-time statistical data 310. Further, it can be seen that the data store stores the number of packets from the current time to the time going back one minute in the past.
- FIG. 5 is an explanatory diagram illustrating an example of the history statistical data_metadata 302 according to the first embodiment.
- the historical statistical data_metadata 302 of the first embodiment is data in a table format, and includes a table name 501, a column name 502, a total content 503, a time interval 504, and a total unit time 505.
- the historical statistical data_metadata 302 may include columns other than the columns described above.
- the column name 502, the total content 503, and the total unit time 505 are the same as the column name 402, the total content 403, and the total unit time 404.
- the table name 501 is the name of the aggregation process for aggregating the real-time statistical data 310 stored as the history statistical data 320 and corresponds to the process name 401.
- the time interval 504 is a history period of the history statistical data 320.
- the historical statistical data 320 is added to the historical statistical data_database 122 of the computer 120. Therefore, when new history statistical data 320 is added, the database management unit 121 notifies the computer 100 of the updated time interval. As a result, the time interval 504 is updated. The computer 100 may update the time interval 504 by making an inquiry to the database management unit 121.
- FIG. 6 is an explanatory diagram illustrating an example of the raw data_metadata 303 according to the first embodiment.
- the raw data_metadata 303 in the first embodiment is file format data.
- schema definition information of the raw data 330 acquired by the computer 130 is stored.
- the raw data_metadata 303 may store information other than the definition information described above.
- the present embodiment is not limited to the data formats of real-time statistical data_metadata 301, historical statistical data_metadata 302, and raw data_metadata 303.
- the real-time statistical data_metadata 301 and the historical statistical data_metadata 302 may be file format data.
- a column to be registered as metadata can be arbitrarily set using the metadata setting information 350.
- FIG. 7 is a flowchart illustrating an example of processing executed by the metadata setting unit 102 according to the first embodiment.
- FIG. 8 is an explanatory diagram illustrating an example of a setting file for setting metadata in the metadata_database 105 according to the first embodiment.
- FIG. 9 is an explanatory diagram illustrating an example of a setting command for setting metadata in the metadata_database 105 according to the first embodiment.
- the metadata setting unit 102 starts processing upon receiving a metadata setting instruction (step S701).
- the metadata setting instruction is input by an administrator who operates the computer 100, a user who operates the client terminal 140, or the like.
- the metadata setting instruction includes a setting file or a setting command related to data of each data store as metadata setting information 350.
- the metadata setting unit 102 starts a data store loop process (step S702). Specifically, the metadata setting unit 102 refers to the metadata setting information 350 included in the metadata setting instruction and selects one data store to be processed.
- the metadata setting unit 102 sets the metadata of the selected data store in the metadata_database 105 based on the metadata setting information 350 (step S703).
- the metadata setting unit 102 extracts columns from the setting file.
- the metadata setting unit 102 generates real-time statistical data_metadata 301 in which the extracted column is set in the metadata_database 105. Further, the metadata setting unit 102 sets a value for each column based on the setting file.
- the metadata setting unit 102 determines whether or not the metadata setting has been completed for all the data stores included in the metadata setting information 350 (step S704).
- the metadata setting unit 102 If it is determined that the metadata setting has not been completed for all the data stores included in the metadata setting information 350, the metadata setting unit 102 returns to step S702 and sets one data store to be processed next. Select and execute the same process.
- the metadata setting unit 102 ends the process.
- FIG. 10 is a flowchart illustrating an outline of processing executed by the request distribution unit 103 according to the first embodiment.
- the request distribution unit 103 starts processing upon receiving a data acquisition request from the display unit 141.
- the data acquisition request includes a specified time that specifies the time range of the requested data and data attribute information (aggregation information).
- the specified time includes a start time (ts) and an end time (te), and the data attribute information includes at least one of a process name, a total unit time, a total content, or a raw data schema.
- the data requested by the data acquisition request is also described as request data.
- the specified time can be set arbitrarily.
- the specified time is specified as either absolute time or relative time.
- the opening time “2014/02/01 19:00” and the end time “2014/03/01 11:00” are included as specified times, and in the case of relative time, the start time “now- 1 min ”and end time“ now ”are included as the designated time.
- “Now” indicates the current time.
- the current time indicates the time when the request distribution unit 103 starts processing.
- the request distribution unit 103 analyzes the data acquisition request and acquires information for specifying the data store from which the request data is acquired (step S1001). Specifically, the request distribution unit 103 acquires specified time and data attribute information. Further, the request distribution unit 103 determines whether the specified time is a relative time or an absolute time.
- the request distribution unit 103 executes data store determination processing for specifying a data store from which data is acquired based on the acquired specified time (step S1002). In the data store determination process, the request distribution unit 103 determines a candidate data store based on a time attribute included in each metadata stored in the metadata_database 105. Details of the data store determination process will be described later with reference to FIGS. 11A and 11B.
- the request distribution unit 103 executes a request determination process for determining a data store that actually issues a request (step S1003), and ends the process.
- the request distribution unit 103 determines whether the request data can be acquired from the candidate data store based on the metadata, and determines the data store that actually issues the request based on the determination result. Details of the request determination process will be described later with reference to FIG.
- 11A and 11B are flowcharts for explaining an example of the data store determination process according to the first embodiment.
- the request distribution unit 103 determines whether or not the specified time is a relative time based on the analysis result of the data acquisition request (step S1101).
- the request distribution unit 103 determines whether there is a possibility that the request data can be acquired from the real-time data totaling unit 111 (step S1102). Specifically, the following processing is executed.
- the request distribution unit 103 acquires the current time. Also, the value of the holding time 405 is acquired by referring to the real-time statistical data_metadata 301. The request distribution unit 103 selects one value of the holding time 405 and determines whether or not the following expression (1) is satisfied.
- the request distribution unit 103 determines that there is data that can be acquired from the real-time data totaling unit 111. This is because when the expression (1) is satisfied, the request data specified by the specified time may be stored in the buffer 112 of the real-time data totaling unit 111.
- the request distribution unit 103 adds a flag to the real-time statistical data_metadata 301.
- the above is the description of the processing in step S1102.
- the request distribution unit 103 may add a flag only to an entry that satisfies Expression (1).
- Expression (1) the determination method using Expression (1) is an example, and any condition may be used as long as the same determination can be made.
- the request distribution unit 103 determines a data store that manages the historical statistical data 320 as a candidate data store (step S1103), and then The request determination process is started (step S1104).
- the request distribution unit 103 proceeds to step S1106.
- step S1101 If it is determined in step S1101 that the specified time is an absolute time, the request distribution unit 103 acquires the current time and determines whether or not the current time is included in the specified time (step S1105).
- the request distribution unit 103 determines the data store that manages the historical statistical data 320 as a candidate data store (step S1103), and then starts the request determination process. (Step S1104).
- step S1106 If it is determined that the current time is included in the specified time, the request distribution unit 103 proceeds to step S1106.
- step S1102 determines whether or not the history statistical data 320 needs to be acquired (step S1106). Specifically, the following processing is executed.
- the request distribution unit acquires the current time and the value of the holding time 405.
- the request distribution unit 103 selects one value of the holding time 405 and determines whether or not the following expression (2) is satisfied.
- ts is a variable indicating the start time. If there is at least one holding time 405 that satisfies Expression (2), the request distribution unit 103 determines that it is necessary to acquire historical statistical data. This is because when the expression (2) is satisfied, not all the request data is stored in the buffer 112 of the real-time data totaling unit 111. Note that the determination method using Expression (2) is an example, and any condition may be used as long as the same determination can be made.
- the request distribution unit 103 determines the data store that manages the real-time statistical data 310 and the data store that manages the historical statistical data 320 as candidate data stores (Step S103). Thereafter, the request determination process is started (step S1104). Specifically, the following processing is executed.
- the request distribution unit 103 identifies a time t0 that satisfies the following expression (3).
- the request distribution unit 103 determines the data store that manages the historical statistical data 320 as the candidate data store for the request data from ts to t0, and manages the real-time statistical data 310 for the request data from t0 to te. Determine the data store as a candidate data store.
- the request distribution unit 103 adds a flag to the history statistical data_metadata 302.
- the above is the description of the process in step S1107. Note that the determination method using Expression (3) is an example, and any condition may be used as long as the same determination can be made.
- the request distribution unit 103 determines a data store that manages the real-time statistical data 310 as a candidate data store (step S1108), and then starts a request determination process. (Step S1104).
- the candidate data store issuing the request can be determined by referring to the metadata_database 105 based on the specified time included in the data acquisition request. Accordingly, the user can select an appropriate data store without being aware of the attribute of data stored in the data store, particularly the time attribute.
- FIG. 12 is a flowchart illustrating an example of a request determination process according to the first embodiment.
- the request distribution unit 103 determines whether or not the data store that manages the real-time statistical data 310 is a candidate data store (step S1201).
- the request distribution unit 103 determines whether a flag is assigned to the real-time statistical data_metadata 301.
- the request distribution unit 103 refers to the real-time statistical data_metadata 301 and sets the attribute information of the data included in the data acquisition request. It is determined whether there is matching real-time statistical data 310 (step S1202). Specifically, the following processing is executed.
- the request distribution unit 103 determines whether or not a process name, a total content, and a total unit time have been acquired as data attribute information. When the process name, the total content, and the total unit time have not been acquired, the request distribution unit 103 determines that there is no real-time statistical data 310 that matches the data attribute information of the data acquisition request.
- the request distribution unit 103 determines whether the process name 401 and the total content 403 of the real-time statistical data_metadata 301 are acquired. Search for matching entries. When there is no matching entry, the request distribution unit 103 determines that there is no real-time statistical data 310 that matches the data attribute information of the data acquisition request.
- the request distribution unit 103 determines whether or not the value of the total unit time 404 of the retrieved entry is equal to or less than the acquired total unit time and is a time that can be aggregated.
- the above-described determination condition is also referred to as a first determination condition.
- the processing described above will be described by taking as an example the case where the acquired total unit time is “1 min”.
- the request distribution unit 103 determines that the first determination condition is satisfied.
- the request distribution unit 103 determines that the first determination condition is satisfied. This is because the request distribution unit 103 can generate two pieces of real-time statistical data 310 of “1 min” by acquiring two pieces of real-time statistical data 310 having a total unit time of “30 sec” and totaling the two real-time statistical data 310. Because.
- the request distribution unit 103 determines that the first determination condition is not satisfied. This is because the real-time statistical data 310 of “1 min” cannot be generated from the real-time statistical data 310 of the total unit time “50 sec”.
- the request distribution unit 103 determines that the first determination condition is satisfied.
- the above is the description of the processing in step S1202.
- the request distribution unit 103 issues a request to the real-time data totaling unit 111 (step S1203), and then step S1204. Proceed to
- the request distribution unit 103 outputs a request issuance instruction including information of the searched entry to the adapter 304-1.
- the adapter 304-1 issues a request to the predetermined real-time data totaling unit 111.
- the request distribution unit 103 issues a request to the database management unit 131 that manages the raw data (step S1207). Thereafter, the process proceeds to step S1204. Specifically, the following processing is executed.
- the request distribution unit 103 refers to the raw data_metadata 303 and specifies the raw data_database 132 from which the requested data can be acquired. At this time, the first determination condition may be applied.
- the request distribution unit 103 outputs a request issuance instruction including the identifier of the computer 130 that manages the specified raw data_database 132 to the adapter 304-3.
- the adapter 304-3 issues a request to the database management unit 131 of the predetermined computer 130. The above is the description of the processing in step S1207.
- step S1204 the request distribution unit 103 determines whether the data store that manages the historical statistical data 320 is a candidate data store (step S1204).
- the request distribution unit 103 determines whether or not a flag is assigned to the history statistical data_metadata 302.
- the request distribution unit 103 ends the process.
- the request distribution unit 103 refers to the historical statistical data_metadata 302 and sets the attribute information of the data included in the data acquisition request. It is determined whether there is matching history statistical data 320 (step S1205).
- the process in step S1205 is the same as the process in step S1202.
- the request distribution unit 103 issues a request to the database management unit 121 (step S1206), and then ends the processing. To do.
- the request distribution unit 103 outputs a request issuance instruction including information of the searched entry to the adapter 304-2.
- the adapter 304-2 issues a request to the predetermined database management unit 121.
- step S1208 If it is determined that there is no real-time statistical data 310 that matches the attribute information of the data included in the data acquisition request, the request distribution unit 103 issues a request to the database management unit 131 that manages the raw data (step S1208). Then, the process ends.
- the process in step S1208 is the same as the process in step S1207.
- the data store determination process and the request determination process are executed separately, but the two processes may be executed simultaneously.
- the request distribution unit 103 executes the process of step S1205 after the process of step S1103, executes the processes of step S1202 and step S1205 after the process of step S1107, and executes the process of step S1202 after executing the process of step S1108. Execute.
- 13A, 13B, 13C, 13D, 13E, 13F, and 13G are explanatory diagrams illustrating an example of a data acquisition request according to the first embodiment.
- step S1101 (Data acquisition request in FIG. 13A)
- the opening time and the end time are “now”, and the specified time is a relative time. Therefore, the determination result in step S1101 is Yes.
- the determination result in step S1102 is Yes.
- the determination result of step S1106 is No. Therefore, the candidate data store is a data store that manages the real-time statistical data 310.
- step S1201 Since the candidate data store is a data store for managing the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. Since the candidate data store is only the data store that manages the real-time statistical data 310, the determination result in step S1204 is No.
- the request distribution unit 103 issues a request to the real-time data totaling unit 111.
- step S1101 is Yes.
- step S1102 is Yes.
- step S1106 is No. Therefore, the candidate data store is a data store that manages the real-time statistical data 310.
- step S1201 Since the candidate data store is a data store for managing the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. Since the candidate data store is only the data store that manages the real-time statistical data 310, the determination result in step S1204 is No.
- the request distribution unit 103 issues a request to the real-time data totaling unit 111.
- step S1101 (Data acquisition request in FIG. 13C)
- the start time is “2014/02/01 19:00:00”
- the end time is “2014/02/01 19:01:00”
- the specified time is an absolute time. Therefore, the determination result in step S1101 is No.
- the candidate data store is a data store that manages the real-time statistical data 310.
- the candidate data store is a data store that manages the historical statistical data 320.
- step S1201 If the candidate data store is a data store that manages the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. Since the candidate data store is only the data store that manages the real-time statistical data 310, the determination result in step S1204 is No. From the above result, the request distribution unit 103 issues a request to the real-time data totaling unit 111.
- step S1201 If the candidate data store is a data store that manages the historical statistical data 320, the determination result in step S1201 is No, and the determination result in step S1204 is Yes. In step S1205, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. From the above result, the request distribution unit 103 issues a request to the database management unit 121.
- step S1101 is Yes.
- the determination result in step S1102 is Yes.
- Expression (2) is satisfied, the determination result in step S1106 is Yes. Therefore, the candidate data store is a data store that manages the real-time statistical data 310 and a data store that manages the historical statistical data 320. Note that t0 is “now ⁇ 1min”.
- step S1201 Since the candidate data store is a data store for managing the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. Since the data store that manages the historical statistical data 320 is also a candidate data store, the determination result in step S1204 is Yes. In step S1205, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes.
- the request distribution unit 103 issues a request to the real-time data totaling unit 111, and issues a request to the database management unit 121 for request data from “now-1hour” to “now-1min”.
- step S1101 (Data acquisition request in FIG. 13E)
- the start time is “2014/02/01 19:00:00”
- the end time is “2014/02/01 19:10:00”
- the specified time is an absolute time. Therefore, the determination result in step S1101 is No.
- the candidate data store is a data store that manages the real-time statistical data 310 and a data store that manages the historical statistical data 320.
- the candidate data store is a data store that manages the historical statistical data 320.
- step S1201 If the candidate data store is a data store that manages the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. If the data store that manages the historical statistical data 320 is also a candidate data store, the determination result in step S1205 is Yes. From the above results, the request distribution unit 103 issues a request to the real-time data totaling unit 111, and requests from “2014/02/01 19: 00: 00: 00” to “2014/02/01 19:09:00”. For data, a request is issued to the database management unit 121.
- step S1201 If the candidate data store is a data store that manages the historical statistical data 320, the determination result in step S1201 is No, and the determination result in step S1204 is Yes. In step S1205, since the process name, the total content, and the total unit time coincide with the top entry of the real-time statistical data_metadata 301, the determination result is Yes. From the above result, the request distribution unit 103 issues a request to the database management unit 121.
- step S1101 (Data acquisition request in FIG. 13F)
- the start time is “2014/02/01 19:00:00”
- the end time is “2014/02/01 19:10:00”
- the specified time is an absolute time. Therefore, the determination result in step S1101 is No.
- the candidate data store is a data store that manages the real-time statistical data 310 and a data store that manages the historical statistical data 320.
- the candidate data store is a data store that manages the historical statistical data 320.
- step S1201 If the candidate data store is a data store that manages the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since there is no entry that matches the total unit time, the determination result is No. If the data store that manages the historical statistical data 320 is also a candidate data store, the determination result in step S1205 is No. From the above result, the request distribution unit 103 issues a request to the database management unit 131.
- step S1201 If the candidate data store is a data store that manages the historical statistical data 320, the determination result in step S1201 is No, and the determination result in step S1204 is Yes. In step S1205, the determination result is No because there is no entry that matches the total unit time. From the above result, the request distribution unit 103 issues a request to the database management unit 131.
- step S1101 (Data acquisition request in FIG. 13G)
- the start time is “2014/02/01 19:00:00”
- the end time is “2014/02/01 19:10:00”
- the specified time is an absolute time. Therefore, the determination result in step S1101 is No.
- the candidate data store is a data store that manages the real-time statistical data 310 and a data store that manages the historical statistical data 320.
- the candidate data store is a data store that manages the historical statistical data 320.
- step S1201 If the candidate data store is a data store that manages the real-time statistical data 310, the determination result in step S1201 is Yes. In step S1202, since the process name, the total content, and the total unit time are not acquired, the determination result is No. If the data store that manages the historical statistical data 320 is also a candidate data store, the determination result in step S1205 is No. From the above result, the request distribution unit 103 issues a request to the database management unit 131.
- step S1201 If the candidate data store is a data store that manages the historical statistical data 320, the determination result in step S1201 is No, and the determination result in step S1204 is Yes. In step S1205, since the process name, the total content, and the total unit time are not acquired, the determination result is No. From the above result, the request distribution unit 103 issues a request to the database management unit 131.
- the user can acquire request data from an appropriate data store by performing only a specified time.
- FIG. 14 is a flowchart illustrating an example of processing executed by the output processing unit 104 according to the first embodiment.
- the output processing unit 104 executes the processing described below after all the data is acquired from the data store. For example, the request distribution unit 103 monitors responses of issued requests, and if the request distribution unit 103 detects that it has received responses of all issued requests, it instructs the output processing unit 104 to start processing.
- the output processing unit 104 starts a data store loop process (step S1401).
- the output processing unit 104 determines whether or not the data acquired from the target data store needs to be aggregated (step S1402). Specifically, the following processing is executed.
- the output processing unit 104 determines whether or not the target data store is a data store that manages the real-time statistical data 310 or the historical statistical data 320. If the target data store is a data store that manages the raw data 330, the output processing unit 104 determines that there is no need to aggregate data.
- the output processing unit 104 determines the metadata corresponding to the target data store, that is, the real-time statistical data_meta
- the value of the total unit time 404 or the value of the total unit time 505 is acquired by referring to the data 301 or the history statistical data_metadata 302.
- the output processing unit 104 determines whether the value of the total unit time 404 or the value of the total unit time 505 is smaller than the total unit time of the attribute information of the data included in the data acquisition request.
- the output processing unit 104 determines that the data needs to be aggregated. The above is the description of the processing in step S1402.
- step S1404 If it is determined that the data acquired from the target data store does not need to be aggregated, the output processing unit 104 proceeds to step S1404.
- the output processing unit 104 When it is determined that the data acquired from the target data store needs to be aggregated, the output processing unit 104 generates the requested data using the acquired data (step S1403).
- the output processing unit 104 merges three pieces of acquired data.
- One request data is generated by Further, the output processing unit 104 rearranges the generated request data in time order.
- the contents of the collection process may be designated in advance.
- the output processing unit 104 determines whether or not processing has been completed for all data stores from which data has been acquired (step S1404).
- the output processing unit 104 selects a new data store (step S1401) and executes the same processing.
- the output processing unit 104 When it is determined that the processing has been completed for all the data stores from which data has been acquired, the output processing unit 104 generates response information (step S1405) and transmits the generated response information to the display unit 141 (step S1405). S1406). Thereafter, the output processing unit 104 ends the process.
- the output processing unit 104 generates response information based on the request from the display unit 141.
- the output processing unit 104 generates graph data, a time chart, and CSV format file data as response information.
- the content of the response information to be generated is not limited.
- the output processing unit 104 generates the data requested in step S1403, but the database management unit 121 and the database management unit 131 may generate the requested data.
- the request distribution unit 103 determines the data aggregation method and instructs the adapter 304 to issue a request including the determined aggregation method.
- the adapter 304 issues a predetermined request such as SQL to the database management unit 121 or the database management unit 131.
- the database management unit 121 or the database management unit 131 acquires data from the database according to the received request, aggregates the acquired data based on a predetermined aggregation method, and transmits the aggregated data to the data store management unit 101. To do.
- step S1401 to step S1404 the processing from step S1401 to step S1404 can be omitted.
- the data store management unit 101 analyzes the data acquisition request and compares the result of the analysis with the attribute of the data stored in the data store, thereby You can properly determine the data store to get
- the user does not need to set detailed data attributes in the data acquisition request, so the request data can be easily acquired.
- the management burden on the user can be reduced.
- the data store management unit 101 can generate the requested data using data such as raw data.
- Example 2 In the second embodiment, a process of the data store management unit 101 when a real-time aggregation process is newly added will be described. Hereinafter, the second embodiment will be described focusing on differences from the first embodiment.
- the configuration of the computer system of the second embodiment, the hardware configuration of the computer 100, and the software configuration are the same as those of the first embodiment, description thereof will be omitted.
- the real-time statistical data_metadata 301, the historical statistical data_metadata 302, and the raw data_metadata 303 of the second embodiment are the same as those of the first embodiment, description thereof is omitted.
- the data store determination process and the request determination process of the second embodiment are the same as the processes of the first embodiment, and thus description thereof is omitted.
- FIG. 15 is a block diagram illustrating a processing flow in the computer system according to the second embodiment.
- FIG. 16 is a flowchart illustrating an example of processing executed by the data store management unit 101 according to the second embodiment.
- Example 2 is different from Example 1 in that an aggregation process is temporarily added.
- existing real-time statistical data 310 and new real-time statistical data 1510 are stored in the buffer 112 of the real-time data totaling unit 111.
- the new real-time statistical data 1510 is not stored in the historical statistical data 320 and is discarded from the buffer 112 after a predetermined time has elapsed.
- a method of temporarily adding the aggregation process a method in which the display unit 141 adds a real-time aggregation process using a data acquisition request is conceivable. For example, it is conceivable to add a real-time aggregation process temporarily when drilling down the currently referenced data.
- processing executed by the data store management unit 101 according to the second embodiment will be described with reference to FIG.
- the data store management unit 101 starts processing upon receiving a data acquisition request from the display unit 141.
- the request distribution unit 103 of the data store management unit 101 analyzes the received data acquisition request (step S1601).
- the request distribution unit 103 executes the processing shown in the first embodiment.
- the data acquisition request includes the process name, the content of the real-time statistical data 310, the total content, the total unit time, and the retention time. Further, the request distribution unit 103 outputs an update instruction including the analysis result of the data acquisition request to the metadata setting unit 102.
- the data store management unit 101 instructs the predetermined real-time data totaling unit 111 to add a new real-time totaling process and start the real-time totaling process based on the analysis result of the data acquisition request (step S1602).
- the metadata setting unit 102 of the data store management unit 101 updates the real-time statistical data_metadata 301 based on the analysis result of the data acquisition request included in the update instruction (step S1603). Thereafter, the data store management unit 101 ends the process.
- the metadata setting unit 102 adds a new entry to the real-time statistical data_metadata 301, and based on the analysis result of the data acquisition request, the process name 401, the column name 402, Values are set for the total contents 403, the total unit time 404, and the holding time 405, respectively.
- the metadata setting unit 102 of the data store management unit 101 deletes the added entry from the real-time statistical data_metadata 301.
- the data store management unit 101, the real-time data totaling unit 111, the historical statistical data_database 122, and the raw data_database 132 are realized by using different computers, but the present invention is not limited to this. .
- the computers 100, 110, 120, and 130 may be virtual computers.
- One computer may include the data store management unit 101, the real-time data totaling unit 111, the historical statistical data_database 122, and the raw data_database 132. Further, the computers 100, 110, 120, and 130 may be realized using a virtual computer generated on one computer. Further, the computer 100 may include the display unit 141.
- this invention is not limited to the above-mentioned Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. Further, a part of the configuration of each embodiment can be added to, deleted from, or replaced with another configuration.
- each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
- the present invention can also be realized by software program codes that implement the functions of the embodiments.
- a storage medium in which the program code is recorded is provided to the computer, and a processor included in the computer reads the program code stored in the storage medium.
- the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention.
- Examples of storage media for supplying such program codes include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A non-volatile memory card, ROM, or the like is used.
- program code for realizing the functions described in this embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, Perl, Shell, PHP, Java, and the like.
- the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R.
- a processor included in the computer may read and execute the program code stored in the storage unit or the storage medium.
- control lines and information lines indicate those that are considered necessary for the explanation, and do not necessarily indicate all the control lines and information lines on the product. All the components may be connected to each other.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Signal Processing (AREA)
- Probability & Statistics with Applications (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Life Sciences & Earth Sciences (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Evolutionary Biology (AREA)
- Computer Hardware Design (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Fuzzy Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
[実施例1]
開時時刻及び終了時刻が「now」になり、指定時間は相対時間である。したがって、ステップS1101の判定結果はYesとなる。また、式(1)を満たすエントリが存在するため、ステップS1102の判定結果はYesとなる。また、式(2)を満たさないため、ステップS1106の判定結果はNoとなる。したがって、候補データストアは、リアルタイム統計データ310を管理するデータストアとなる。
開始時刻が「now-1min」、終了時刻が「now」になり、指定時間は相対時間である。したがって、ステップS1101の判定結果はYesとなる。また、式(1)を満たすエントリが存在するため、ステップS1102の判定結果はYesとなる。また、式(2)を満たさないため、ステップS1106の判定結果はNoとなる。したがって、候補データストアは、リアルタイム統計データ310を管理するデータストアとなる。
開始時刻が「2014/02/01 19:00:00」、終了時刻が「2014/02/01 19:01:00」になり、指定時間は絶対時間である。したがって、ステップS1101の判定結果はNoとなる。
開始時刻が「now-1hour」、終了時刻が「now」になり、指定時間は相対時間である。したがって、ステップS1101の判定結果はYesとなる。また、式(1)を満たすエントリが存在するため、ステップS1102の判定結果はYesとなる。式(2)を満たすため、ステップS1106の判定結果はYesとなる。したがって、候補データストアは、リアルタイム統計データ310を管理するデータストア及び履歴統計データ320を管理するデータストアとなる。なお、t0は「now-1min」となる。
開始時刻が「2014/02/01 19:00:00」、終了時刻が「2014/02/01 19:10:00」になり、指定時間は絶対時間である。したがって、ステップS1101の判定結果はNoとなる。
開始時刻が「2014/02/01 19:00:00」、終了時刻が「2014/02/01 19:10:00」になり、指定時間は絶対時間である。したがって、ステップS1101の判定結果はNoとなる。
開始時刻が「2014/02/01 19:00:00」、終了時刻が「2014/02/01 19:10:00」になり、指定時間は絶対時間である。したがって、ステップS1101の判定結果はNoとなる。
実施例2では、新たにリアルタイム集計処理を追加された場合のデータストア管理部101の処理について説明する。以下、実施例1との差異を中心に実施例2について説明する。
Claims (10)
- 複数の計算機、及び管理計算機を備える計算機システムであって、
前記複数の計算機の各々は、第1のプロセッサ、前記第1のプロセッサに接続される第1のメモリ、前記第1のプロセッサに接続される第1のネットワークインタフェースを有し、
前記管理計算機は、第2のプロセッサ、前記第2のプロセッサに接続される第2のメモリ、前記第2のプロセッサに接続される第2のネットワークインタフェースを有し、
前記計算機システムには、前記複数の計算機を用いて複数のデータストアが構成され、
前記複数のデータストアの各々は、データソースから取得され、かつ、属性が異なるデータを格納し、
前記管理計算機は、
前記複数のデータストアから要求データを取得するためのデータ取得リクエストを受け付け、前記データ取得リクエストを解析することによって前記要求データを取得するデータストアを決定するリクエスト振り分け部と、
前記複数のデータストアの各々に格納されるデータの時間属性を含むメタデータ管理情報と、を有し、
前記リクエスト振り分け部は、
前記要求データの時間属性を含む前記データ取得リクエストを受け付けた場合、前記データ取得リクエストの解析結果に基づいて前記メタデータ管理情報を参照して、候補データストアを選択し、
前記候補データストアから前記要求データを取得できるか否かを判定し、
前記判定の結果に基づいて、前記要求データを取得するためのリクエストを発行するデータストアを決定し、
前記決定されたデータストアに前記リクエストを発行することを特徴とする計算機システム。 - 請求項1に記載の計算機システムであって、
前記複数のデータストアは、
前記データソースからリアルタイムデータを取得し、所定の集計単位時間分のリアルタイムデータを集計することによって算出されたリアルタイム統計データを格納する第1のデータストアと、
前記リアルタイム統計データの履歴である履歴統計データを格納する第2のデータストアと、を含み、
前記第1のデータストアは、現在の時刻から保持時間だけさかのぼった時刻までの時間範囲の前記リアルタイム統計データを格納し、
前記メタデータ管理情報は、前記第1のデータストアに格納される前記リアルタイム統計データに関する前記保持時間を管理する第1のメタデータ情報を含み、
前記データ取得リクエストに含まれる前記要求データの時間属性は、取得するデータの時間範囲を示す指定時間を含み、
前記リクエスト振り分け部は、
前記第1のメタデータ情報に含まれる前記保持時間、及び前記データ取得リクエストに含まれる前記指定時間に基づいて、前記第1のデータストアから前記要求データを取得できる可能性があるか否かを判定し、
前記第1のデータストアから前記要求データを取得できると判定された場合、前記第1のデータストアを前記候補データストアとして選択し、
前記第1のデータストアから前記要求データを取得できないと判定された場合、前記第2のデータストアを前記候補データストアとして選択することを特徴とする計算機システム。 - 請求項2に記載の計算機システムであって、
前記データ取得リクエストに含まれる前記指定時間は、開始時刻と終了時刻とを含み、
前記リクエスト振り分け部は、
現在の時刻を取得し、
前記現在の時刻から前記第1のメタデータ情報に含まれる前記保持時間を減算することによって第1の時刻を算出し、
前記第1の時刻が前記終了時刻以前の時刻であるか否かを判定し、
前記第1の時刻が前記終了時刻以後の時刻であると判定された場合、前記第2のデータストアを前記候補データストアとして選択し、
前記第1の時刻が前記終了時刻以前の時刻であると判定された場合、前記第1の時刻が前記開始時刻以後の時刻であるか否かを判定し、
前記第1の時刻が前記開始時刻以前の時刻であると判定された場合、前記第1のデータストアを前記候補データストアとして選択し、
前記第1の時刻が前記開始時刻以後の時刻であると判定された場合、前記開始時刻から前記第1の時刻までの前記要求データを取得する前記候補データストアとして前記第2のデータストアを選択し、前記第1の時刻から前記終了時刻までの前記要求データを取得する前記候補データストアとして前記第1のデータストアを選択することを特徴とする計算機システム。 - 請求項3に記載の計算機システムであって、
前記複数のデータストアは、前記データソースから取得された前記リアルタイムデータの履歴を格納する第3のデータストアを含み、
前記第1のメタデータ情報は、前記リアルタイム統計データの算出時に集計されるデータの種別及び集計単位時間を第1の集計情報として含み、
前記メタデータ管理情報は、前記履歴統計データに対応する前記リアルタイム統計データの算出時に集計されるデータの種別、及び集計単位時間を第2の集計情報として含む第2のメタデータ情報を含み、
前記データ取得リクエストは、前記要求データを特定するためのデータの種別及び集計単位時間を第3の集計情報として含み、
前記リクエスト振り分け部は、
前記候補データストアとして前記第1のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第1の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第1の集計情報の集計単位時間と一致する第1の判定条件を満たすか否かを判定し、
前記第1の判定条件を満たすと判定された場合、前記第1のデータストアを前記リクエストを発行するデータストアに決定し、
前記第1の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定し、
前記候補データストアとして前記第2のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第2の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第2の集計情報の集計単位時間と一致する第2の判定条件を満たすか否かを判定し、
前記第2の判定条件を満たすと判定された場合、前記第2のデータストアを前記リクエストを発行するデータストアに決定し、
前記第2の判定条件を満たさないと場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定することを特徴とする計算機システム。 - 請求項4に記載の計算機システムであって、
前記管理計算機は、前記複数のデータストアから取得されたデータを用いて前記データ取得リクエストに対する応答として応答情報を生成する出力処理部を有し、
前記リクエスト振り分け部は、
前記候補データストアとして前記第1のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第1の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第1の集計情報の集計単位時間の約数である第3の判定条件を満たすか否かを判定し、
前記第3の判定条件を満たすと判定された場合、前記第1のデータストアを前記リクエストを発行するデータストアに決定し、
前記第3の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定し、
前記候補データストアとして前記第2のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第2の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第2の集計情報の集計単位時間の約数である第4の判定条件を満たすか否かを判定し、
前記第4の判定条件を満たすと判定された場合、前記第2のデータストアを前記リクエストを発行するデータストアに決定し、
前記第4の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定し、
前記出力処理部は、
前記第1のデータストアからデータが取得された場合、前記第1のメタデータ情報を参照し、
前記第1のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいか否かを判定し、
前記第1のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいと判定された場合、前記第1のデータストアから取得されたデータを集計することによって、前記要求データを生成し、
前記第2のデータストアからデータが取得された場合、前記第2のメタデータ情報を参照し、
前記第2のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいか否かを判定し、
前記第2のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいと判定された場合、前記第2のデータストアから取得されたデータを集計することによって、前記要求データを生成し、
前記要求データを用いて、前記データ取得リクエストに対する応答として応答情報を生成することを特徴とする計算機システム。 - データを格納する複数の計算機、及び管理計算機を備える計算機システムにおけるデータアクセス管理方法であって、
前記複数の計算機の各々は、第1のプロセッサ、前記第1のプロセッサに接続される第1のメモリ、前記第1のプロセッサに接続される第1のネットワークインタフェースを有し、
前記管理計算機は、第2のプロセッサ、前記第2のプロセッサに接続される第2のメモリ、前記第2のプロセッサに接続される第2のネットワークインタフェースを有し、
前記計算機システムには、前記複数の計算機を用いて複数のデータストアが構成され、
前記複数のデータストアの各々は、データソースから取得され、かつ、属性が異なるデータを格納し、
前記管理計算機は、
前記複数のデータストアから要求データを取得するためのデータ取得リクエストを受け付け、前記データ取得リクエストを解析することによって前記要求データを取得するデータストアを決定するリクエスト振り分け部と、
前記複数のデータストアの各々に格納されるデータの時間属性を含むメタデータ管理情報と、を有し、
前記データアクセス管理方法は、
前記リクエスト振り分け部が、前記要求データの時間属性を含む前記データ取得リクエストを受け付けた場合、前記データ取得リクエストの解析結果に基づいて前記メタデータ管理情報を参照して、候補データストアを選択する第1のステップと、
前記リクエスト振り分け部が、前記候補データストアから前記要求データを取得できるか否かを判定し、前記判定の結果に基づいて前記要求データを取得するためのリクエストを発行するデータストアを決定する第2のステップと、
前記リクエスト振り分け部が、前記決定されたデータストアに前記リクエストを発行する第3のステップと、を含むことを特徴とするデータアクセス管理方法。 - 請求項6に記載のデータアクセス管理方法であって、
前記複数のデータストアは、
前記データソースからリアルタイムデータを取得し、所定の集計単位時間分のリアルタイムデータを集計することによって算出されたリアルタイム統計データを格納する第1のデータストアと、
前記リアルタイム統計データの履歴である履歴統計データを格納する第2のデータストアと、を含み、
前記第1のデータストアは、現在の時刻から保持時間だけさかのぼった時刻までの時間範囲の前記リアルタイム統計データを格納し、
前記メタデータ管理情報は、前記第1のデータストアに格納される前記リアルタイム統計データに関する前記保持時間を管理する第1のメタデータ情報を含み、
前記データ取得リクエストに含まれる前記要求データの時間属性は、取得するデータの時間範囲を示す指定時間を含み、
前記第1のステップは、
前記第1のメタデータ情報に含まれる前記保持時間、及び前記データ取得リクエストに含まれる前記指定時間に基づいて、前記第1のデータストアから前記要求データを取得できる可能性があるか否かを判定するステップと、
前記第1のデータストアから前記要求データを取得できると判定された場合、前記第1のデータストアを前記候補データストアとして選択するステップと、
前記第1のデータストアから前記要求データを取得できないと判定された場合、前記第2のデータストアを前記候補データストアとして選択するステップと、を含むことを特徴とするデータアクセス管理方法。 - 請求項7に記載のデータアクセス管理方法であって、
前記データ取得リクエストに含まれる前記指定時間は、開始時刻と終了時刻とを含み、
前記第1のステップは、
現在の時刻を取得するステップと、
前記現在の時刻から前記第1のメタデータ情報に含まれる前記保持時間を減算することによって第1の時刻を算出するステップと、
前記第1の時刻が前記終了時刻以前の時刻であるか否かを判定するステップと、
前記第1の時刻が前記終了時刻以後の時刻であると判定された場合、前記第2のデータストアを前記候補データストアとして選択するステップと、
前記第1の時刻が前記終了時刻以前の時刻であると判定された場合、前記第1の時刻が前記開始時刻以後の時刻であるか否かを判定するステップと、
前記第1の時刻が前記開始時刻以前の時刻であると判定された場合、前記第1のデータストアを前記候補データストアとして選択するステップと、
前記第1の時刻が前記開始時刻以後の時刻であると判定された場合、前記開始時刻から前記第1の時刻までの前記要求データを取得する前記候補データストアとして前記第2のデータストアを選択し、前記第1の時刻から前記終了時刻までの前記要求データを取得する前記候補データストアとして前記第1のデータストアを選択するステップと、を含むことを特徴とするデータアクセス管理方法。 - 請求項8に記載のデータアクセス管理方法であって、
前記複数のデータストアは、前記データソースから取得された前記リアルタイムデータの履歴を格納する第3のデータストアを含み、
前記第1のメタデータ情報は、前記リアルタイム統計データの算出時に集計されるデータの種別及び集計単位時間を第1の集計情報として含み、
前記メタデータ管理情報は、前記履歴統計データに対応する前記リアルタイム統計データの算出時に集計されるデータの種別、及び集計単位時間を第2の集計情報として含む第2のメタデータ情報を含み、
前記データ取得リクエストは、前記要求データを特定するためのデータの種別及び集計単位時間を第3の集計情報として含み、
前記第2のステップは、
前記候補データストアとして前記第1のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第1の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第1の集計情報の集計単位時間と一致する第1の判定条件を満たすか否かを判定するステップと、
前記第1の判定条件を満たすと判定された場合、前記第1のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記第1の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記候補データストアとして前記第2のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第2の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第2の集計情報の集計単位時間と一致する第2の判定条件を満たすか否かを判定するステップと、
前記第2の判定条件を満たすと判定された場合、前記第2のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記第2の判定条件を満たさないと場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定するステップと、を含むことを特徴とするデータアクセス管理方法。 - 請求項9に記載のデータアクセス管理方法であって、
前記管理計算機は、前記複数のデータストアから取得されたデータを用いて前記データ取得リクエストに対する応答として応答情報を生成する出力処理部を有し、
前記第2のステップは、
前記候補データストアとして前記第1のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第1の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第1の集計情報の集計単位時間の約数である第3の判定条件を満たすか否かを判定するステップと、
前記第3の判定条件を満たすと判定された場合、前記第1のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記第3の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記候補データストアとして前記第2のデータストアが選択された場合、前記第3の集計情報のデータの種別が前記第2の集計情報のデータの種別と一致し、かつ、前記第3の集計情報の集計単位時間が前記第2の集計情報の集計単位時間の約数である第4の判定条件を満たすか否かを判定するステップと、
前記第4の判定条件を満たすと判定された場合、前記第2のデータストアを前記リクエストを発行するデータストアに決定するステップと、
前記第4の判定条件を満たさないと判定された場合、前記第3のデータストアを前記リクエストを発行するデータストアに決定するステップと、を含み、
前記データアクセス管理方法は、
前記出力処理部が、前記第1のデータストアからデータが取得された場合、前記第1のメタデータ情報を参照し、
前記出力処理部が、前記第1のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいか否かを判定するステップと、
前記出力処理部が、前記第1のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいと判定された場合、前記第1のデータストアから取得されたデータを集計することによって、前記要求データを生成するステップと、
前記出力処理部が、前記第2のデータストアからデータが取得された場合、前記第2のメタデータ情報を参照するステップと、
前記出力処理部が、前記第2のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいか否かを判定するステップと、
前記出力処理部が、前記第2のデータストアから取得されたデータの集計単位時間が、前記第3の集計情報の集計単位時間より小さいと判定された場合、前記第2のデータストアから取得されたデータを集計することによって、前記要求データを生成するステップと、
前記出力処理部が、前記要求データを用いて、前記データ取得リクエストに対する応答として応答情報を生成するステップと、を含むことを特徴とするデータアクセス管理方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016528708A JP6193491B2 (ja) | 2014-06-18 | 2014-06-18 | 計算機システム |
PCT/JP2014/066112 WO2015193988A1 (ja) | 2014-06-18 | 2014-06-18 | 計算機システム |
US15/303,236 US10664496B2 (en) | 2014-06-18 | 2014-06-18 | Computer system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2014/066112 WO2015193988A1 (ja) | 2014-06-18 | 2014-06-18 | 計算機システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015193988A1 true WO2015193988A1 (ja) | 2015-12-23 |
Family
ID=54935020
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/066112 WO2015193988A1 (ja) | 2014-06-18 | 2014-06-18 | 計算機システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US10664496B2 (ja) |
JP (1) | JP6193491B2 (ja) |
WO (1) | WO2015193988A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPWO2021230346A1 (ja) * | 2020-05-15 | 2021-11-18 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000148779A (ja) * | 1998-11-11 | 2000-05-30 | Mitsubishi Electric Corp | 運転履歴データ管理方法およびそのプログラムを記録した記録媒体と装置 |
JP2002259681A (ja) * | 2001-03-05 | 2002-09-13 | Toshiba Tec Corp | 入出金管理システム |
JP2011505615A (ja) * | 2007-11-09 | 2011-02-24 | アリババ グループ ホールディング リミテッド | Oltp環境における統計アプリケーション |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0883206A (ja) | 1994-09-14 | 1996-03-26 | Toshiba Corp | マルチメディアデータベースシステム及びマルチメディアデータアクセス方法 |
JP3569992B2 (ja) * | 1995-02-17 | 2004-09-29 | 株式会社日立製作所 | 移動体検出・抽出装置、移動体検出・抽出方法及び移動体監視システム |
US6295527B1 (en) * | 1998-02-13 | 2001-09-25 | Cisco Technology, Inc. | Real-time user-defined creation of network device information collections |
US7512673B2 (en) * | 2001-01-11 | 2009-03-31 | Attune Systems, Inc. | Rule based aggregation of files and transactions in a switched file system |
US7509322B2 (en) * | 2001-01-11 | 2009-03-24 | F5 Networks, Inc. | Aggregated lock management for locking aggregated files in a switched file system |
US7733366B2 (en) * | 2002-07-01 | 2010-06-08 | Microsoft Corporation | Computer network-based, interactive, multimedia learning system and process |
US8417678B2 (en) * | 2002-07-30 | 2013-04-09 | Storediq, Inc. | System, method and apparatus for enterprise policy management |
US8209680B1 (en) * | 2003-04-11 | 2012-06-26 | Vmware, Inc. | System and method for disk imaging on diverse computers |
US7865485B2 (en) * | 2003-09-23 | 2011-01-04 | Emc Corporation | Multi-threaded write interface and methods for increasing the single file read and write throughput of a file server |
US8171101B2 (en) * | 2005-09-30 | 2012-05-01 | Cleversafe, Inc. | Smart access to a dispersed data storage network |
US8285878B2 (en) * | 2007-10-09 | 2012-10-09 | Cleversafe, Inc. | Block based access to a dispersed data storage network |
US7546427B2 (en) * | 2005-09-30 | 2009-06-09 | Cleversafe, Inc. | System for rebuilding dispersed data |
WO2007120738A2 (en) * | 2006-04-11 | 2007-10-25 | Medox Exchange, Inc. | Systems and methods of managing specification, enforcement, or auditing of electronic health information access or use |
JP5352513B2 (ja) * | 2010-03-31 | 2013-11-27 | 株式会社日立製作所 | 無線通信システム及びハンドオーバー制御方法 |
US9606858B2 (en) * | 2010-04-26 | 2017-03-28 | International Business Machines Corporation | Temporarily storing an encoded data slice |
FR2976379B1 (fr) * | 2011-06-08 | 2019-04-26 | Schneider Electric Industries Sas | Systeme et procede de partage de donnees stockees dans une base de donnees |
US9882980B2 (en) * | 2013-10-22 | 2018-01-30 | International Business Machines Corporation | Managing continuous priority workload availability and general workload availability between sites at unlimited distances for products and services |
-
2014
- 2014-06-18 WO PCT/JP2014/066112 patent/WO2015193988A1/ja active Application Filing
- 2014-06-18 US US15/303,236 patent/US10664496B2/en active Active
- 2014-06-18 JP JP2016528708A patent/JP6193491B2/ja active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000148779A (ja) * | 1998-11-11 | 2000-05-30 | Mitsubishi Electric Corp | 運転履歴データ管理方法およびそのプログラムを記録した記録媒体と装置 |
JP2002259681A (ja) * | 2001-03-05 | 2002-09-13 | Toshiba Tec Corp | 入出金管理システム |
JP2011505615A (ja) * | 2007-11-09 | 2011-02-24 | アリババ グループ ホールディング リミテッド | Oltp環境における統計アプリケーション |
Also Published As
Publication number | Publication date |
---|---|
JPWO2015193988A1 (ja) | 2017-04-20 |
JP6193491B2 (ja) | 2017-09-06 |
US20170039263A1 (en) | 2017-02-09 |
US10664496B2 (en) | 2020-05-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6697392B2 (ja) | 半構造データスキーマのトランスペアレントディスカバリ | |
CN110032604B (zh) | 数据存储装置、转译装置及数据库访问方法 | |
JP7046172B2 (ja) | シャード・データベースのシャード・テーブルにレコードを記憶するためのコンピュータ実装方法、コンピュータ・プログラム製品、およびシステム、シャード・データベースのシャード・テーブルからレコードを検索するためのコンピュータ実装方法、コンピュータ・プログラム製品、およびシステム、ならびにシャード・データベースを記憶するためのシステム | |
JP5999574B2 (ja) | データベース管理システム及び計算機システム | |
US10877810B2 (en) | Object storage system with metadata operation priority processing | |
JP6281225B2 (ja) | 情報処理装置 | |
US11797483B2 (en) | Data pruning based on metadata | |
US20140214890A1 (en) | Database shard arbiter | |
WO2016016944A1 (ja) | データベース管理システム及びデータベース管理方法 | |
US10108669B1 (en) | Partitioning data stores using tenant specific partitioning strategies | |
JP2007133452A (ja) | データ収集プログラムおよびデータ収集装置 | |
JP6262505B2 (ja) | 分散型データ仮想化システム、クエリ処理方法及びクエリ処理プログラム | |
JP6193491B2 (ja) | 計算機システム | |
JP6467826B2 (ja) | 帳票データ管理プログラム、帳票データ管理方法、及び情報処理装置 | |
JP5472885B2 (ja) | プログラム、ストリームデータ処理方法及びストリームデータ処理計算機 | |
JP6568232B2 (ja) | 計算機システム、及び、装置の管理方法 | |
JP2015121924A (ja) | データ管理システム、サーバ装置、サーバ装置の制御方法、及びプログラム | |
JPWO2018061070A1 (ja) | 計算機システム及び分析ソースデータ管理方法 | |
WO2014203397A1 (ja) | 計算機システム、メタデータ管理方法及びプログラム | |
US20200210530A1 (en) | Systems, methods, and storage media for automatically translating content using a hybrid language | |
US20200210436A1 (en) | Systems, methods, storage media, and computing platforms for context-based data retrieval | |
US20200210212A1 (en) | Systems, methods, storage media, and computing platforms for end user pre-inferred context driven applications | |
US20170262512A1 (en) | Search processing method, search processing apparatus, and non-transitory computer-readable recording medium storing search processing program | |
JP2014063336A (ja) | 計算機システム及びジョブネット実行方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14895301 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15303236 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2016528708 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14895301 Country of ref document: EP Kind code of ref document: A1 |