CN110109931B - Method and system for preventing data access conflict between RAC instances - Google Patents
Method and system for preventing data access conflict between RAC instances Download PDFInfo
- Publication number
- CN110109931B CN110109931B CN201711450602.7A CN201711450602A CN110109931B CN 110109931 B CN110109931 B CN 110109931B CN 201711450602 A CN201711450602 A CN 201711450602A CN 110109931 B CN110109931 B CN 110109931B
- Authority
- CN
- China
- Prior art keywords
- client
- partition
- organization
- access
- request
- 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.)
- Active
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/22—Indexing; Data structures therefor; Storage structures
-
- 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
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
-
- 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/24564—Applying rules; Deductive queries
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method for preventing data access conflict between RAC examples of a database, which comprises the following steps: creating a list partition of the service table based on the organization ID, and taking the organization ID of the client as an index field of the service table; associating the organization ID with the client IP through a routing rule; acquiring a client IP which provides an access request, and determining the same list partition corresponding to an organization ID associated with the client IP according to a routing rule; and acquiring access requests of the client aiming at the same list partition, and sending the access requests of the same list partition to the same database instance of the corresponding application server through the reverse proxy server. Any partition data of the same table is cached in the cache of one example only, the service tables among the examples do not need to be transmitted mutually, and the lock contention phenomenon does not exist among different partitions, so that the access conflict among the examples is avoided, the performance and the processing capacity of the system are improved, and the problem of utilizing an Oracle architecture is solved.
Description
Technical Field
The invention relates to the technical field of database application, in particular to a method and a system for preventing data access conflict between RAC instances.
Background
The Oracle RAC is a technical framework for improving the high availability of the system, and is also a cluster technology, and the number of nodes in the cluster is 2 or more. The background databases of many computer systems employ Oracle RAC, especially for large enterprise or corporate level systems. However, the main problem which plagues database design and operation and maintenance personnel is the problem of data access conflict between RAC instances. The Oracle database provides a method for collision detection and a mechanism for data sharing among instances, but the design of the database architecture is still crucial, because the database design determines the number of collisions occurring and thus the performance of the system. The industry widely uses service separation or read-write separation, however, on one hand, read-write separation is difficult to develop and has a long development period, and on the other hand, if a single node does not provide the processing capability required by the service, only a higher-grade server can be selected.
The Oracle partitioning technology is a divide-and-conquer technology for converting a large table into a plurality of small tables, and supported partitioning modes comprise range partitioning, Hash partitioning, list partitioning and the like. After the large table is divided into the small tables, the large table is still logically one table, is transparent to developers, and can improve the performance of the system.
In the prior art (CN201610258541.3 "a method and apparatus for reducing GC requests between RAC nodes", a method for reducing GC requests between RAC nodes is disclosed, which includes: and receiving a business operation request sent by a client, wherein the business operation request comprises an SQL statement. And analyzing the table name corresponding to the SQL statement according to the SQL statement, and judging whether the table name corresponding to the SQL statement exists in the service table in the table information memory area. If so, switching on a sub-connection pool corresponding to the SQL statement and an access path corresponding to the sub-connection pool according to the access rule of the business table; if not, allocating an access path for the SQL statement, and then connecting a sub-connection pool corresponding to the SQL statement and an access corresponding to the sub-connection pool
<171964I-BJ > Path. The technology for reducing GC requests among RAC nodes disclosed by the prior art improves the execution efficiency of SQL statements. However, the prior art does not solve the problem of mutual transmission of data between instances and data access conflict between instances.
Therefore, a technique is required to implement a technique for preventing data access collision between RAC instances.
Disclosure of Invention
The invention provides a method and a system for preventing data access conflict between RAC instances, which are used for solving the problem of data access conflict between RAC instances.
In order to solve the above problem, the present invention provides a method for preventing data access conflict between RAC instances of a database, the method comprising:
creating a list partition of the service table based on the organization ID, and taking the organization ID of the client as an index field of the service table;
associating the organization ID with the client IP through the routing rule;
acquiring a client IP of a client which provides an access request, and determining the same list partition corresponding to an organization ID associated with the client IP according to the routing rule;
and acquiring the access request of the client aiming at the same list partition, and sending the access request of the same list partition to the same database instance of the corresponding application server through a reverse proxy server.
Preferably, in each list partition of the service table, data of at least one organization ID is stored.
Preferably, the data of each list partition is cached in only one database instance.
Preferably, the method further comprises the following steps:
and for the client sending the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server through the reverse proxy server according to a polling algorithm.
Preferably, the method further comprises the following steps:
and for the client which does not send the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server.
Preferably, the method further comprises the following steps:
different database instances cache data of the different list partitions in the service table.
Preferably, the method further comprises the following steps:
each application server corresponds to an available database instance.
According to another aspect of the present invention, there is provided a system for preventing data access conflict between database RAC instances, the system comprising:
the partition unit is used for creating a list partition of the service table based on the organization ID and taking the organization ID of the client as an index field of the service table;
a rule unit, configured to associate an organization ID with a client IP via the routing rule;
a determining unit, configured to obtain a client IP of a client that makes an access request, and determine, according to the routing rule, the same list partition corresponding to an organization ID associated with the client IP;
and the execution unit is used for acquiring the access requests of the client aiming at the same list partition, and sending the access requests of the same list partition to the same database instance of the corresponding application server through the reverse proxy server.
Preferably, the partition unit is further configured to: in each list partition of the service table, data of at least one organization ID is stored.
Preferably, the partition unit is further configured to: the data of each list partition is cached in only one database instance.
Preferably, the execution unit is further configured to:
and for the client sending the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server through the reverse proxy server according to a polling algorithm.
Preferably, the execution unit is further configured to:
and for the client which does not send the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server.
Preferably, in the execution unit, different database instances cache data of the different list partitions in the service table.
Preferably, in the execution unit, each application server corresponds to one available database instance.
The technical scheme of the invention adopts an Oracle partition table to store a service table exceeding 4GB, partitions the related data table according to the organization ID, and routes the related request to the corresponding database instance instead of the partition of the table through a front-end reverse proxy server Nginx and an application server. The technical scheme of the invention only routes the access requests of different tables to different database instances. According to the technical scheme, after the service table is partitioned, the large table is disassembled into the small tables, the requirement for reading other example data does not exist during table correlation query, mutual transmission of data blocks among database examples is avoided, further, data access conflict of an Oracle RAC example is effectively avoided, and the response speed and the processing capacity of a system are improved.
Drawings
A more complete understanding of exemplary embodiments of the present invention may be had by reference to the following drawings in which:
fig. 1 is a flowchart of a method for preventing data access collision between RAC instances according to an embodiment of the present invention;
figure 2 is a diagram of a system architecture for preventing data access conflicts between RAC instances according to an embodiment of the present invention;
FIG. 3 is a flow diagram of a business table access according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an example structure of an Oracle database according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of an example Oracle cluster data cache according to an embodiment of the present invention; and
fig. 6 is a diagram illustrating a system structure for preventing data access collision between RAC instances according to an embodiment of the present invention.
Detailed Description
The exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, however, the present invention may be embodied in many different forms and is not limited to the embodiments described herein, which are provided for complete and complete disclosure of the present invention and to fully convey the scope of the present invention to those skilled in the art. The terminology used in the exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting of the invention. In the drawings, the same units/elements are denoted by the same reference numerals.
Unless otherwise defined, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Further, it will be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense.
Fig. 1 is a flowchart of a method for preventing data access collision between RAC instances according to an embodiment of the present invention. The embodiment of the invention discloses a method for effectively avoiding data access conflict between Oracle RAC instances, which utilizes an Oracle partition technology, also utilizes a self-defined routing rule of a Nginx reverse proxy server and a corresponding relation between an organization ID and a client IP address in a service system, creates a list partition on a large table which is likely to generate excessive RAC instance access conflict according to the organization ID, and only accesses one instance of a background Oracle database and related organizations access the same instance through the Nginx route of the reverse proxy server, and only accesses an independent partition storing the organization data when accessing the large table, and the data of one partition only exists in the cache of one instance, so that data blocks do not need to be mutually transmitted between the Oracle RAC instances, thereby effectively avoiding data transmission and access conflict between RAC nodes. As shown in fig. 1, a method 100 for preventing data access collision between RAC instances comprises:
preferably, in step 101: and creating a list partition of the service table based on the organization ID, and taking the organization ID of the client as an index field of the service table.
Preferably, in each list partition of the service table, data of at least one organization ID is stored.
Preferably, the data for each list partition is cached in only one database instance.
Preferably, at step 102: the organization ID is associated with the client IP by routing rules.
Preferably, in step 103: and acquiring the client IP of the client which provides the access request, and determining the same list partition corresponding to the organization ID associated with the client IP according to the routing rule.
Preferably, at step 104: and acquiring access requests of the client aiming at the same list partition, and sending the access requests of the same list partition to the same database instance of the corresponding application server through the reverse proxy server.
Preferably, the method 100 further comprises:
and for the client sending the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server through the reverse proxy server according to the polling algorithm.
Preferably, the method 100 further comprises:
and for the client which does not send the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server.
Preferably, the method 100 further comprises:
different database instances cache data for different list partitions in the service table.
Preferably, the method 100 further comprises:
each application server corresponds to an available database instance.
Because large enterprises generally have own internal networks or various private networks, the IP addresses of branch organizations are fixed, and the routing of client requests to corresponding application server clusters according to the client IP is realized through the self-defined routing rule of Nginx. In the application, an Oracle client is installed on an application server, and one of N instances of a rear-end Oracle database is accessed through a failure over mode. An access request from any organization (branch office) accesses a database instance in the background through a front-end reverse proxy server Nginx and an application server cluster. The list partition is created by organizing IDs (i.e., clorgids) by key fields for large tables exceeding 4GB and their indices. According to the data volume, each partition stores 1-N data of cOrgnID, a data access request of a related organization (branch mechanism) is sent to the same database instance through a front-end reverse proxy server Nginx, the data of one partition is cached in only one instance, and the data of different cOrgnID are isolated by utilizing a partitioning technology, so that the access conflict of a database shared data block among a plurality of instances of an Oracle RAC database is avoided, and the performance and the processing capacity of the whole system are improved.
And creating list partitions by using service tables of more than 4GB in the database according to the organization ID fields, wherein each partition contains 1-N organized data according to the predicted data volume, and the index creates a local partition index based on the organization ID. The method for effectively avoiding data access contention among Oracle RAC instances comprises the steps of creating a list partition table and a list partition index according to the commonalities of organization ID fields of main service tables, wherein each partition contains one to N organized data. Database access requests of different organizations send access requests needing to access the same partition to the same database instance through the corresponding application server through the proxy server of Nginx, therefore, any partition data of the same table can be cached in the cache of one instance, the business tables among the instances do not need data transmission, and lock contention does not exist among different partitions, thereby avoiding access conflict among the instances, greatly improving the performance and the processing capacity of the system, and solving the problem that technical personnel are troubled when an Oracle RAC architecture is utilized.
Because large enterprise servers such as groups are deployed in a centralized manner, the network IP address is fixed. In the application, a reverse proxy server is used for setting a routing rule according to the IP of a client, associating an organization with an IP address and identifying whether the access requests of the same partition exist or not. The access requests of the same partition are routed to the same application server cluster after passing through the front-end reverse proxy server. In the application, any application server cluster only accesses one database instance normally, therefore, an access request from any organization accesses one database instance in a background through a front-end reverse proxy server Nginx and the application server cluster, and related organizations only need to access the same partition of the same instance when accessing a large table, so that the conflict of operations of sharing data blocks among database instances is avoided, the excessive cache fusion generated by access data is reduced, and the key problem existing when an Oracle RAC is utilized is solved.
Fig. 2 is a system architecture diagram for preventing data access collision between RAC instances according to an embodiment of the present invention. As shown in fig. 2, first, the client sends a request to the reverse proxy server nginnx, and the reverse proxy server nginnx determines an application server cluster to be accessed according to a custom routing rule. When a request is sent to the reverse proxy server Nginx for the first time, the server randomly sends the request to the nodes in the application server cluster according to a polling algorithm. When the client sends a request to the reverse proxy server Nginx for the second time, the reverse proxy server Nginx receives the request and processes the request, the client request is guided to the original application node, and the reverse proxy server Nginx realizes the functions of routing and load balancing at the same time.
As shown in fig. 2, the application server cluster a can only access the database cluster instance a, and only when the database cluster instance a hangs up, the application server cluster a can only access the database cluster instance B, and similarly, the application server cluster B. Thus, each application server cluster corresponds to an available Oracle database server cluster instance, and related organizations or branches only need to access the same partition of the same instance, so that operation conflicts between the database server clusters and database shared data are avoided, and the performance of accessing the database by users is improved.
Fig. 3 is a flow chart of service table access according to an embodiment of the present invention. The service table access flow diagram shown in fig. 3 illustrates the process of routing data access requests of a client to different application servers, database instances and tables. If the table is a partition table, the database optimizer will access the corresponding partition. In the embodiment of the invention, a client proposes an access request for accessing an SQL statement, acquires a client IP of the client which proposes the access request, and determines the same list partition corresponding to an organization ID associated with the client IP according to a routing rule. And sending the access requests of the client aiming at the same list partition to the same database instance of the corresponding application server through the reverse proxy server. The method and the device analyze the SQL statement through the optimizer, and if the SQL statement does not contain the index key words, all partitions of the table are accessed. When the SQL statement contains the index key words, further analyzing the SQL statement, and if the SQL statement does not contain the partition key words, accessing all index partitions of the table; if the SQL statement contains partition keywords, accessing the index partition cut by the table; and accessing the partition table data according to the ROWID. And ending the business table access flow.
FIG. 4 is a diagram illustrating an example structure of an Oracle database according to an embodiment of the present invention. The memory structure of each instance of OracleRAC is shown in fig. 4, the access conflict between the instances mainly occurs in the cache region of the SGA database, and if the data cached and stored in the part of each instance is different, the anti-counterfeiting conflict between the instances cannot occur.
FIG. 5 is a schematic diagram of an example structure of an Oracle cluster data cache according to an embodiment of the present invention. After table partitioning and access requests are routed, different database instance data caches cache different partition data of the same table, and data between instances does not have data transmission requirements across instances, so that access conflicts do not exist.
Fig. 6 is a diagram illustrating a system structure for preventing data access collision between RAC instances according to an embodiment of the present invention. As shown in fig. 6, a system 600 for preventing data access collision between RAC instances comprises:
and a partition unit 601, configured to create a list partition of the service table based on the organization ID, and use the organization ID of the client as an index field of the service table.
Preferably, the partition unit is further configured to: in each list partition of the service table, data of at least one organization ID is stored.
Preferably, the partition unit is further configured to: the data of each list partition is cached in only one database instance.
The rule unit 602 associates the organization ID with the client IP by a routing rule.
The determining unit 603 is configured to obtain a client IP of the client that makes the access request, and determine, according to the routing rule, the same list partition corresponding to the organization ID associated with the client IP.
The executing unit 604 is configured to obtain access requests of the client for the same list partition, and send the access requests of the same list partition to the same database instance of the corresponding application server through the reverse proxy server.
Preferably, the execution unit is further configured to:
and for the client sending the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server through the reverse proxy server according to the polling algorithm.
Preferably, the execution unit is further configured to:
and for the client which does not send the request for the first time, sending the access request of the client aiming at the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server.
Preferably, in the execution unit, different database instances cache data of different list partitions in the service table.
Preferably, in the execution unit, each application server corresponds to one available database instance.
The embodiment of the invention provides a system for effectively avoiding data access contention among Oracle RAC instances of a database. The method and the device adopt an Oracle partition table to store the service table exceeding 4GB, partition the related data table according to the organization ID, and route the related request to the corresponding database instance instead of the partition of the table through the front-end reverse proxy server Nginx and the application server. According to the method, a list partition table and a list partition index are created according to the common organization ID field of the main service table, and each partition contains data of one to N organizations. Database access requests of different organizations send access requests needing to access the same partition to the same database instance through the corresponding application server through the reverse proxy server of the Nginx, therefore, any partition data of the same table can be cached in the cache of one instance, service tables among the instances do not need data transmission, and lock contention phenomenon does not exist among different partitions, so that access conflict among the instances is avoided, the performance and the processing capacity of the system are greatly improved, and the problem that technical personnel are troubled when an Oracle RAC framework is utilized is solved.
The invention has been described with reference to a few embodiments. However, other embodiments of the invention than the one disclosed above are equally possible within the scope of the invention, as would be apparent to a person skilled in the art from the appended patent claims.
Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the [ device, component, etc ]" are to be interpreted openly as referring to at least one instance of said device, component, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.
Claims (10)
1. A method for preventing data access conflicts between database RAC instances, said method comprising:
creating a list partition of the service table based on the organization ID, and taking the organization ID of the client as an index field of the service table;
associating the organization ID with the client IP through a routing rule;
acquiring a client IP of a client which provides an access request, and determining the same list partition corresponding to an organization ID associated with the client IP according to the routing rule;
obtaining the access request of the client aiming at the same list partition, and sending the access request of the same list partition to the same database instance of the corresponding application server through a reverse proxy server;
for a client sending a request for the first time, sending an access request of the client aiming at the same list partition to a node of a corresponding application server through the reverse proxy server according to a polling algorithm;
and for the client which does not send the request for the first time, sending the access request of the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server aiming at the access request of the same list partition.
2. The method of claim 1, wherein each list partition of the service table stores data for at least one organization ID.
3. The method of claim 1, wherein the data for each list partition is cached in only one database instance.
4. The method of claim 1, further comprising:
different database instances cache data of the different list partitions in the service table.
5. The method of claim 1, further comprising:
each application server corresponds to an available database instance.
6. A system for preventing data access conflicts between database RAC instances, said system comprising:
the partition unit is used for creating a list partition of the service table based on the organization ID and taking the organization ID of the client as an index field of the service table;
the rule unit is used for associating the organization ID with the client IP through a routing rule;
a determining unit, configured to obtain a client IP of a client that makes an access request, and determine, according to the routing rule, the same list partition corresponding to an organization ID associated with the client IP;
the execution unit is used for acquiring the access requests of the client aiming at the same list partition, and sending the access requests of the same list partition to the same database instance of the corresponding application server through the reverse proxy server;
for a client sending a request for the first time, sending an access request of the client aiming at the same list partition to a node of a corresponding application server through the reverse proxy server according to a polling algorithm;
and for the client which does not send the request for the first time, sending the access request of the same list partition to the node of the corresponding application server when the client sends the request for the first time through the reverse proxy server aiming at the access request of the same list partition.
7. The system of claim 6, the partition unit further to: in each list partition of the service table, data of at least one organization ID is stored.
8. The system of claim 6, the partition unit further to: the data of each list partition is cached in only one database instance.
9. The system of claim 6, wherein in the execution unit, different database instances cache data of the different list partitions in the service table.
10. The system of claim 6, wherein each of the application servers corresponds to one of the available database instances in the execution unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711450602.7A CN110109931B (en) | 2017-12-27 | 2017-12-27 | Method and system for preventing data access conflict between RAC instances |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711450602.7A CN110109931B (en) | 2017-12-27 | 2017-12-27 | Method and system for preventing data access conflict between RAC instances |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110109931A CN110109931A (en) | 2019-08-09 |
| CN110109931B true CN110109931B (en) | 2021-08-24 |
Family
ID=67483489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711450602.7A Active CN110109931B (en) | 2017-12-27 | 2017-12-27 | Method and system for preventing data access conflict between RAC instances |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110109931B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112491940B (en) * | 2019-09-12 | 2024-05-24 | 北京京东振世信息技术有限公司 | Request forwarding method and device of proxy server, storage medium and electronic equipment |
| CN111209296A (en) * | 2019-12-31 | 2020-05-29 | 航天信息股份有限公司企业服务分公司 | Database access method and device, electronic equipment and storage medium |
| CN111581234B (en) * | 2020-05-09 | 2023-04-28 | 中国银行股份有限公司 | RAC multi-node database query method, device and system |
| CN114389998A (en) * | 2021-12-21 | 2022-04-22 | 深圳奥哲网络科技有限公司 | Flow distribution method, system, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101083597A (en) * | 2006-05-31 | 2007-12-05 | 朗迅科技公司 | SIP based instant message of mobile self-organizing network |
| CN102047611A (en) * | 2008-03-31 | 2011-05-04 | 三星电子株式会社 | Upnp device for preventing network address conflict in consideration of remote access and method thereof |
| CN104980468A (en) * | 2014-04-09 | 2015-10-14 | 深圳市腾讯计算机***有限公司 | Method, device and system for processing service request |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7308411B2 (en) * | 2004-04-01 | 2007-12-11 | Leo Software, Inc. | Method of presenting leasing arrangements |
| CN103107976A (en) * | 2011-11-10 | 2013-05-15 | 中国电信股份有限公司 | Content provider/service provider (CP/SP) user identification authentication method and system and authentication support device |
| US9135269B2 (en) * | 2011-12-07 | 2015-09-15 | Egnyte, Inc. | System and method of implementing an object storage infrastructure for cloud-based services |
| CN102799628B (en) * | 2012-06-21 | 2015-10-07 | 新浪网技术(中国)有限公司 | The method and apparatus of data partition is carried out in key-value database |
| CN104238999B (en) * | 2013-06-09 | 2017-11-17 | 阿里巴巴集团控股有限公司 | A kind of method for scheduling task and device based on horizontal partitioning distributed data base |
| CN106576074B (en) * | 2015-07-31 | 2020-04-21 | 华为技术有限公司 | Method, equipment and system for acquiring routing rule |
| CN107197000B (en) * | 2017-05-04 | 2020-07-31 | 微梦创科网络科技（中国）有限公司 | Static and dynamic hybrid caching method, device and system |
-
2017
- 2017-12-27 CN CN201711450602.7A patent/CN110109931B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101083597A (en) * | 2006-05-31 | 2007-12-05 | 朗迅科技公司 | SIP based instant message of mobile self-organizing network |
| CN102047611A (en) * | 2008-03-31 | 2011-05-04 | 三星电子株式会社 | Upnp device for preventing network address conflict in consideration of remote access and method thereof |
| CN104980468A (en) * | 2014-04-09 | 2015-10-14 | 深圳市腾讯计算机***有限公司 | Method, device and system for processing service request |
Non-Patent Citations (2)
| Title |
|---|
| Optimizing adaptive multi-route query processing via time-partitioned indices - ScienceDirect;Karen Works 等;《 Journal of Computer and System Sciences》;20130531;330-348 * |
| Oracle RAC数据库缓存优化方法研究;姜召凤;《中国优秀硕士学位论文全文数据库 信息科技辑》;20090915(第9期);I138-457 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110109931A (en) | 2019-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3418877B1 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| CN110109931B (en) | Method and system for preventing data access conflict between RAC instances | |
| US7809769B2 (en) | Database partitioning by virtual partitions | |
| US10002148B2 (en) | Memory-aware joins based in a database cluster | |
| US10275184B2 (en) | Framework for volatile memory query execution in a multi node cluster | |
| JP3269849B2 (en) | Parallel database processing system and its retrieval method | |
| CN102053982B (en) | A kind of database information management method and equipment | |
| US9384072B2 (en) | Distributed queue pair state on a host channel adapter | |
| US7853570B2 (en) | Method and system for data processing with parallel database systems | |
| US11561930B2 (en) | Independent evictions from datastore accelerator fleet nodes | |
| CN103067433B (en) | A kind of data migration method of distributed memory system, equipment and system | |
| CN103544261B (en) | A kind of magnanimity structuring daily record data global index's management method and device | |
| CN101594309B (en) | Method and device for managing memory resources in cluster system, and network system | |
| WO2012121316A1 (en) | Distributed storage system and method therefor | |
| KR101435789B1 (en) | System and Method for Big Data Processing of DLP System | |
| US20090037427A1 (en) | Redistributing a distributed database | |
| CN102314506B (en) | Based on the distributed buffering district management method of dynamic index | |
| US20050004898A1 (en) | Distributed search methods, architectures, systems, and software | |
| US11263270B1 (en) | Heat balancing in a distributed time-series database | |
| CN111984696A (en) | Novel database and method | |
| CN111309805B (en) | Data reading and writing method and device for database | |
| US11409771B1 (en) | Splitting partitions across clusters in a time-series database | |
| US11947534B2 (en) | Connection pools for parallel processing applications accessing distributed databases | |
| US11366598B1 (en) | Dynamic lease assignments in a time-series database | |
| CN116541427A (en) | Data query method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |