CN112800104A - Method and device for optimizing ES query request link - Google Patents
Method and device for optimizing ES query request link Download PDFInfo
- Publication number
- CN112800104A CN112800104A CN202011444261.4A CN202011444261A CN112800104A CN 112800104 A CN112800104 A CN 112800104A CN 202011444261 A CN202011444261 A CN 202011444261A CN 112800104 A CN112800104 A CN 112800104A
- Authority
- CN
- China
- Prior art keywords
- request
- server
- address
- data storage
- node address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- 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/2471—Distributed 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
Abstract
The invention discloses a method and a device for optimizing ES query request links, relates to the technical field of big data, and can disperse the pressure of coordinated nodes, reduce query links and improve the efficiency of ES query. The method comprises the following steps: periodically requesting a server index list query interface, and updating data storage node addresses corresponding to all index fragments in a client cache; matching coordination node addresses located in the same node area with each data storage node one by one on the basis of the data storage node addresses; and initiating an ES query request, querying a data storage node address corresponding to the ES query request in the cache, and taking the matched coordination node address as a target address request server. The device is applied with the method provided by the scheme.
Description
Technical Field
The invention relates to the technical field of big data, in particular to a method and a device for optimizing an ES query request link.
Background
For ES query requests, the index data is typically randomly scattered across the cluster data nodes according to a certain rule. Referring to fig. 2, when an open-source native client initiates an ES query request, a coordinating node configured by the client is requested first, and then an actual data storage node is requested through the coordinating node, that is, most of the conventional ES query request schemes need to be performed across node areas, which has the following problems in 2 respects:
1. all query requests are forwarded through a plurality of fixedly configured coordination nodes, so that the pressure of the coordination nodes is high, and data isolation is not achieved.
2. Because the coordinating node and the data storage node requesting access are mostly not in the same node area, mostly need to be forwarded by the cross-area coordinating node once, resulting in a longer link.
Disclosure of Invention
The invention aims to provide a method and a device for optimizing an ES query request link, which can disperse the pressure of a coordinating node, reduce query links and improve the efficiency of ES query.
In order to achieve the above object, a first aspect of the present invention provides an ES query request link optimization method, including:
periodically requesting a server index list query interface, and updating data storage node addresses corresponding to all index fragments in a client cache;
matching coordination node addresses located in the same node area with each data storage node one by one on the basis of the data storage node addresses;
and initiating an ES query request, querying the data storage node address corresponding to the ES query request in a cache, and taking the matched coordination node address as a target address request server.
Preferably, before periodically requesting the server index list query interface and updating the data storage node addresses corresponding to all index segments in the client cache, the method further includes:
and appointing at least one coordination node address in advance in a client by adopting a fixed configuration means, and taking the coordination node address in the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in a cache.
Preferably, the method of initiating an ES query request, querying the data storage node address corresponding to the ES query request in the cache, and requesting the server with the matched coordination node address as the target address includes:
judging whether the initiated ES query request is a single index request;
if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server when the inquiry result is searched, or taking a coordination node address fixedly configured in the client as the target address request server;
if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
Further, after requesting a server with the matched coordinating node address as a target address, the method further includes:
and if the server side responds abnormally, the coordination node address fixedly configured in the client side is reused as a target address to request the server side.
Optionally, after the server responds to the exception and requests the server by reusing the coordination node address fixedly configured in the client as the target address, the method further includes:
and the client asynchronously requests the index list query interface of the server to actively request to update the data storage node addresses corresponding to all the index fragments in the cache of the client.
Compared with the prior art, the ES request link optimization method provided by the invention has the following beneficial effects:
in the ES request link optimization method provided by the invention, data storage node addresses corresponding to all index fragments are periodically updated in a client cache, coordination node addresses which correspond to all the data storage node addresses one to one and are located in the same node area are matched, then the client is used for initiating an ES query request, and the coordination node addresses matched with the ES query request in the cache are used as target addresses to request a server.
Therefore, the invention can preferentially use the coordination nodes located in the same node area with the target data storage node to forward the access server according to the initiated ES query request, and compared with the prior art that all ES query requests use a plurality of coordination nodes with fixed configuration to coordinate the access server, the scheme of the invention disperses the distribution of the coordination nodes and greatly reduces the forwarding pressure of the coordination nodes. In addition, because the coordination node and the target data storage node are located in the same node area, the forwarding times of the coordination node can be reduced, the request link is shortened, and data isolation can be achieved well.
A second aspect of the present invention provides an ES query request link optimization apparatus, which is applied to the ES request link optimization method in the above technical solution, and the apparatus includes:
the cache updating unit is used for periodically requesting the index list query interface of the server and updating the data storage node addresses corresponding to all the index fragments in the cache of the client;
the association matching unit is used for matching the coordination node address which is positioned in the same node area with each data storage node on the basis of the data storage node address in a one-to-one correspondence manner;
and the request query unit is used for initiating an ES query request, querying the data storage node address corresponding to the ES query request in the cache, and taking the matched coordination node address as a target address request server.
Preferably, the method further comprises the following steps:
and the fixed configuration unit is used for appointing at least one coordination node address in advance by adopting a fixed configuration means in the client, and is used for taking the coordination node address of the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in the cache.
Preferably, the method further comprises the following steps:
a judging unit, configured to judge whether the initiated ES query request is a single index request; if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server when the inquiry result is searched, or taking a coordination node address fixedly configured in the client as the target address request server; if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
Preferably, the method further comprises the following steps:
and the exception handling unit is used for reusing the coordination node address fixedly configured in the client as a target address request server if the server responds to the exception.
Compared with the prior art, the beneficial effects of the ES query request link optimization device provided by the present invention are the same as those of the ES query request link optimization method provided by the above technical solution, and are not described herein again.
A third aspect of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the ES query request link optimization method described above.
Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the invention are the same as those of the ES query request link optimization method provided by the technical scheme, and are not repeated herein.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a flowchart illustrating a method for optimizing an ES query request link according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a conventional ES query request link according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart illustrating a method for optimizing an ES query request link according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an optimized ES query request link according to an embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, fig. 3 and fig. 4, the present embodiment provides a method for optimizing an ES query request link, including:
periodically requesting a server index list query interface, and updating data storage node addresses corresponding to all index fragments in a client cache; matching coordination node addresses located in the same node area with each data storage node one by one on the basis of the data storage node addresses; and initiating an ES query request, querying the data storage node address corresponding to the ES query request in a cache, and taking the matched coordination node address as a target address request server.
In the method for optimizing ES request links provided in this embodiment, data storage node addresses corresponding to all index fragments are periodically updated in a cache of a client, coordination node addresses corresponding to each data storage node address one to one and located in the same node area are simultaneously matched, then the client is used to initiate an ES query request, and the coordination node addresses matched with the ES query request in the cache are used as target addresses to request a server.
It can be seen that, according to the initiated ES query request, the embodiment can preferentially use the coordinating node located in the same node area as the target data storage node to forward the access server, and compared with the prior art in which all ES query requests use several coordinating nodes in fixed configuration to coordinate the access server, the embodiment disperses the distribution of coordinating nodes, and greatly reduces the forwarding pressure of the coordinating nodes. In addition, because the coordination node and the target data storage node are located in the same node area, the forwarding times of the coordination node can be reduced, the request link is shortened, and data isolation can be achieved well.
In the above embodiment, before periodically requesting the query interface of the server index list and updating the addresses of the data storage nodes corresponding to all the index segments in the client cache, the method further includes:
and appointing at least one coordination node address in advance in a client by adopting a fixed configuration means, and taking the coordination node address in the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in a cache.
In specific implementation, at least one Coordinating Node address, that is, an address of a Coordinating Node, is fixedly configured in a client, and when the Coordinating Node of the fixed configuration is used in a cache and cannot query a data storage Node address corresponding to an ES query request, that is, cannot match a Coordinating Node condition in the same Node area, in order to ensure a normal response of a server, a conventional ES request policy is continuously used, that is, the Coordinating Node address of the fixed configuration is used as a target address request server.
In addition, after the coordination node address is fixedly configured in the client, the client thread starts to run, a periodic timing task is started to request the index list query interface of the server, and the data storage node addresses corresponding to all index fragments in the client cache are updated regularly. The purpose of periodically updating the client cache is to keep the address of the coordinating node in the latest state all the time, and avoid the problem of link extension caused by the fact that the traditional scheme has to be used because the address is not updated in time, namely, the coordinating node with fixed configuration is used for accessing the server.
In the above embodiment, the method for querying the data storage node address corresponding to the ES query request in the cache and using the matched coordination node address as the target address request server includes:
judging whether the initiated ES query request is a single index request; if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server when the inquiry result is searched, or taking the coordination node address fixedly configured in the client as the target address request server; if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
In specific implementation, referring to fig. 3, in a flow of an ES query request initiated by a client, it is necessary to determine whether a current request is a single index request, if the current request is the single index request, the optimized link scheme in this embodiment is used to access a server, and if the current request is not the single index request, a traditional scheme is used to access the server. Of course, even if the request is a single-index request, there may be a case where the address of the data storage node corresponding to the ES query request cannot be found in the client cache, and at this time, in order to ensure normal response of the request, the server may still be accessed by using a conventional scheme. It should be noted that, there are various situations that the address of the data storage node corresponding to the ES query request cannot be found in the client cache, for example, the address of the data storage node in the client cache is not the latest.
Generally, a single index request refers to a query result only involving a single data table, data in the single data table may be distributed among a plurality of data storage nodes, and a non-single index request refers to a query result involving a plurality of data tables.
In the foregoing embodiment, after the step of requesting the server with the matched coordinating node address as the target address, the method further includes:
and if the server side responds abnormally, the coordination node address fixedly configured in the client side is reused as a target address to request the server side.
In specific implementation, when the server responds to an exception, the client jumps to a flow execution request and an exception handling retry action in the conventional scheme, that is, the configured Coordinating Node address is used as a target address to request the server, and waits for the server to respond.
In the above embodiment, after the server responds to the exception and requests the server by reusing the coordination node address fixedly configured in the client as the target address, the method further includes:
and the client asynchronously requests the index list query interface of the server to actively request to update the data storage node addresses corresponding to all the index fragments in the cache of the client.
In specific implementation, a client asynchronously initiates a request to request a server index list query interface, obtains data storage node addresses corresponding to all index fragments, and updates the result to the cache of the client.
In summary, the above embodiment scheme has the following effects:
1. request pressure of fixed configuration coordination nodes in the traditional scheme is dispersed, and the request pressure is dispersed to all coordination nodes in a cluster;
2. the query of the single index only affects the node where the index is located, and the mutual influence of the query among the indexes is reduced;
3. the accessed coordination node and the data storage node are in the same node area, and the forwarding of the request link is reduced.
Example two
The present embodiment provides an ES query request link optimization apparatus, including:
the cache updating unit is used for periodically requesting the index list query interface of the server and updating the data storage node addresses corresponding to all the index fragments in the cache of the client;
the association matching unit is used for matching the coordination node address which is positioned in the same node area with each data storage node on the basis of the data storage node address in a one-to-one correspondence manner;
and the request query unit is used for initiating an ES query request, querying the data storage node address corresponding to the ES query request in the cache, and taking the matched coordination node address as a target address request server.
Preferably, the method further comprises the following steps:
and the fixed configuration unit is used for appointing at least one coordination node address in advance by adopting a fixed configuration means in the client, and is used for taking the coordination node address of the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in the cache.
Preferably, the method further comprises the following steps:
a judging unit, configured to judge whether the initiated ES query request is a single index request; if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server when the inquiry result is searched, or taking a coordination node address fixedly configured in the client as the target address request server; if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
Preferably, the method further comprises the following steps:
and the exception handling unit is used for reusing the coordination node address fixedly configured in the client as a target address request server if the server responds to the exception.
Compared with the prior art, the beneficial effects of the ES query request link optimization device provided by the embodiment of the present invention are the same as those of the ES query request link optimization method provided by the first embodiment, and are not described herein again.
EXAMPLE III
The present embodiment provides a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to perform the steps of the ES query request link optimization method.
Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by this embodiment are the same as those of the ES query request link optimization method provided by the above technical solution, and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the invention may be implemented by hardware instructions related to a program, the program may be stored in a computer-readable storage medium, and when executed, the program includes the steps of the method of the embodiment, and the storage medium may be: ROM/RAM, magnetic disks, optical disks, memory cards, and the like.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. An ES query request link optimization method, comprising:
periodically requesting a server index list query interface, and updating data storage node addresses corresponding to all index fragments in a client cache;
matching coordination node addresses located in the same node area with each data storage node in a one-to-one correspondence mode based on the data storage node addresses;
and initiating an ES query request, querying the data storage node address corresponding to the ES query request in a cache, and taking the matched coordination node address as a target address request server.
2. The method of claim 1, wherein before periodically requesting the server-side index list query interface to update the addresses of the data storage nodes corresponding to all the index shards in the client-side cache, the method further comprises:
and pre-designating at least one coordination node address in a client in a fixed configuration mode, wherein the coordination node address is used for taking the coordination node address in the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in a cache.
3. The method of claim 2, wherein initiating an ES query request, querying the data storage node address in the cache corresponding to the ES query request, and requesting a server with the matched coordinating node address as a target address comprises:
judging whether the initiated ES query request is a single index request;
if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server after the inquiry result is searched, otherwise, taking the coordination node address fixedly configured in the client as the target address request server;
if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
4. The method according to any of claims 1-3, further comprising, after requesting a server with the matched coordinating node address as a target address:
and if the server side responds abnormally, the coordination node address fixedly configured in the client side is reused as a target address to request the server side.
5. The method of claim 4, wherein after the server requests the server by reusing the coordination node address fixedly configured in the client as the target address in response to the exception, the method further comprises:
and the client asynchronously requests the index list query interface of the server to actively request to update the data storage node addresses corresponding to all the index fragments in the cache of the client.
6. An ES query request link optimization apparatus, comprising:
the cache updating unit is used for periodically requesting the index list query interface of the server and updating the data storage node addresses corresponding to all the index fragments in the cache of the client;
the association matching unit is used for matching the coordination node address which is positioned in the same node area with each data storage node on the basis of the data storage node address in a one-to-one correspondence manner;
and the request query unit is used for initiating an ES query request, querying the data storage node address corresponding to the ES query request in the cache, and taking the matched coordination node address as a target address request server.
7. The apparatus of claim 6, further comprising:
and the fixed configuration unit is used for appointing at least one coordination node address in advance by adopting a fixed configuration means in the client, and is used for taking the coordination node address of the fixed configuration as a target address when the data storage node address corresponding to the ES query request cannot be queried in the cache.
8. The apparatus of claim 7, further comprising:
a judging unit, configured to judge whether the initiated ES query request is a single index request; if the judgment result is yes, continuing to inquire the data storage node address corresponding to the ES inquiry request in the cache, and taking the matched coordination node address as a target address request server when the inquiry result is searched, or taking a coordination node address fixedly configured in the client as the target address request server; if the judgment result is negative, the coordination node address fixedly configured in the client is directly used as the target address request server.
9. The apparatus of claim 8, further comprising:
and the exception handling unit is used for reusing the coordination node address fixedly configured in the client as a target address request server if the server responds to the exception.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of the claims 1 to 5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011444261.4A CN112800104A (en) | 2020-12-08 | 2020-12-08 | Method and device for optimizing ES query request link |
| CA3141328A CA3141328A1 (en) | 2020-12-08 | 2021-12-08 | Method and device for es query request link optimization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011444261.4A CN112800104A (en) | 2020-12-08 | 2020-12-08 | Method and device for optimizing ES query request link |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112800104A true CN112800104A (en) | 2021-05-14 |
Family
ID=75806580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011444261.4A Pending CN112800104A (en) | 2020-12-08 | 2020-12-08 | Method and device for optimizing ES query request link |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112800104A (en) |
| CA (1) | CA3141328A1 (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741731A (en) * | 2009-12-03 | 2010-06-16 | 中兴通讯股份有限公司 | Content metadata storing, inquiring method and managing system in content delivery network (CDN) |
| CN107959695A (en) * | 2016-10-14 | 2018-04-24 | 北京国双科技有限公司 | A kind of data transmission method and device |
| CN108959549A (en) * | 2018-06-29 | 2018-12-07 | 北京奇虎科技有限公司 | Method for writing data, calculates equipment and computer storage medium at device |
| CN109739882A (en) * | 2019-01-04 | 2019-05-10 | 南威软件股份有限公司 | A kind of big data enquiring and optimizing method based on Presto and Elasticsearch |
| CN110334094A (en) * | 2019-06-20 | 2019-10-15 | 阿里巴巴集团控股有限公司 | A kind of data query method, system, device and equipment based on inverted index |
| CN110569302A (en) * | 2019-08-16 | 2019-12-13 | 苏宁云计算有限公司 | method and device for physical isolation of distributed cluster based on lucene |
| CN111338766A (en) * | 2020-03-12 | 2020-06-26 | 腾讯科技（深圳）有限公司 | Transaction processing method and device, computer equipment and storage medium |
| CN111460023A (en) * | 2020-04-29 | 2020-07-28 | 上海东普信息科技有限公司 | Service data processing method, device, equipment and storage medium based on elastic search |
| CN111752986A (en) * | 2019-03-27 | 2020-10-09 | 杭州海康威视数字技术股份有限公司 | Data query method and device, equipment and storage medium |
| CN111797096A (en) * | 2020-06-29 | 2020-10-20 | 中国平安财产保险股份有限公司 | Data indexing method and device based on ElasticSearch, computer equipment and storage medium |
-
2020
- 2020-12-08 CN CN202011444261.4A patent/CN112800104A/en active Pending
-
2021
- 2021-12-08 CA CA3141328A patent/CA3141328A1/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741731A (en) * | 2009-12-03 | 2010-06-16 | 中兴通讯股份有限公司 | Content metadata storing, inquiring method and managing system in content delivery network (CDN) |
| CN107959695A (en) * | 2016-10-14 | 2018-04-24 | 北京国双科技有限公司 | A kind of data transmission method and device |
| CN108959549A (en) * | 2018-06-29 | 2018-12-07 | 北京奇虎科技有限公司 | Method for writing data, calculates equipment and computer storage medium at device |
| CN109739882A (en) * | 2019-01-04 | 2019-05-10 | 南威软件股份有限公司 | A kind of big data enquiring and optimizing method based on Presto and Elasticsearch |
| CN111752986A (en) * | 2019-03-27 | 2020-10-09 | 杭州海康威视数字技术股份有限公司 | Data query method and device, equipment and storage medium |
| CN110334094A (en) * | 2019-06-20 | 2019-10-15 | 阿里巴巴集团控股有限公司 | A kind of data query method, system, device and equipment based on inverted index |
| CN110569302A (en) * | 2019-08-16 | 2019-12-13 | 苏宁云计算有限公司 | method and device for physical isolation of distributed cluster based on lucene |
| CN111338766A (en) * | 2020-03-12 | 2020-06-26 | 腾讯科技（深圳）有限公司 | Transaction processing method and device, computer equipment and storage medium |
| CN111460023A (en) * | 2020-04-29 | 2020-07-28 | 上海东普信息科技有限公司 | Service data processing method, device, equipment and storage medium based on elastic search |
| CN111797096A (en) * | 2020-06-29 | 2020-10-20 | 中国平安财产保险股份有限公司 | Data indexing method and device based on ElasticSearch, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 多喝水JS: "es源码笔记-如何选择协调节点", pages 146 - 148, Retrieved from the Internet <URL:https://www.jianshu.com/p/ae4f0e53795c> * |
Also Published As
| Publication number | Publication date |
|---|---|
| CA3141328A1 (en) | 2022-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10534776B2 (en) | Proximity grids for an in-memory data grid | |
| TWI665569B (en) | Method and device for data caching | |
| US10462250B2 (en) | Distributed caching cluster client configuration | |
| CN109213699B (en) | Metadata management method, system, equipment and computer readable storage medium | |
| US10275347B2 (en) | System, method and computer program product for managing caches | |
| CN110147407B (en) | Data processing method and device and database management server | |
| US20140149537A1 (en) | Distributed caching cluster management | |
| JP2018502373A (en) | System and method for performing a distributed tree scan using hardware-based processing | |
| US20130018919A1 (en) | Speculative Switch Database | |
| CN102937980A (en) | Method for inquiring data of cluster database | |
| WO2017016336A1 (en) | Method and apparatus for data processing and query | |
| US20150142845A1 (en) | Smart database caching | |
| JP2019518271A (en) | Identification and adjustment of network resource information | |
| CN107870954B (en) | Method and device for expanding distributed database | |
| US9529772B1 (en) | Distributed caching cluster configuration | |
| US9710532B2 (en) | Method for avoiding conflicts in database cluster | |
| US20200089678A1 (en) | Autonomic caching for in memory data grid query processing | |
| US20190228009A1 (en) | Information processing system and information processing method | |
| US11360975B2 (en) | Data providing apparatus and data providing method | |
| JP2013156765A (en) | Information processing apparatus, distributed processing system, cache management program, and distributed processing method | |
| US9979783B2 (en) | Distributed coordinated snapshots | |
| US20150178328A1 (en) | Client-Side Directed Commands to a Loosely Coupled Database | |
| CA3057038C (en) | Data filtering method, apparatus, electronic apparatus and storage medium | |
| CN112800104A (en) | Method and device for optimizing ES query request link | |
| US11188538B2 (en) | Dynamic generated query plan caching |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |