CN107124469B - Cluster node communication method and system - Google Patents
Cluster node communication method and system Download PDFInfo
- Publication number
- CN107124469B CN107124469B CN201710423270.7A CN201710423270A CN107124469B CN 107124469 B CN107124469 B CN 107124469B CN 201710423270 A CN201710423270 A CN 201710423270A CN 107124469 B CN107124469 B CN 107124469B
- Authority
- CN
- China
- Prior art keywords
- node
- cluster
- data
- slave
- master
- 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
- 238000004891 communication Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000004044 response Effects 0.000 abstract description 9
- 230000009467 reduction Effects 0.000 abstract description 4
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 4
- 230000006872 improvement Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- 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
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
Abstract
The application discloses a cluster node communication method, which comprises the steps that a first main node obtains data of each slave node in a first cluster and caches the data; the first master node is located in a first cluster; the first main node receives a calling request sent by a second main node for the data of the slave nodes in the first cluster; the second master node is located in a second cluster; and the first host node acquires the data to be called requested by the second host node from the cache and returns the data to the second host node. According to the method and the device, the master node caches the data of the slave nodes in the cluster, so that the master nodes in other clusters can access the master node to obtain the data of the slave nodes in the cluster, direct communication between the slave nodes and the master nodes of other clusters can be avoided, and the reduction of the response speed of a system request can be avoided when the slave nodes are in failure. The application also discloses a cluster node communication system, which also has the beneficial effects.
Description
Technical Field
The present application relates to the field of cluster technologies, and in particular, to a cluster node communication method and system.
Background
With the rapid development of computer system technology, hardware devices used for high-performance computing have experienced a transition from vector computers to parallel computers to cluster systems. Cluster systems (hereinafter referred to as clusters) are now becoming more and more widely used in high performance computing.
The cluster refers to a group of mutually independent service entities such as computers and the like which are interconnected through a high-speed network and serve as a single system for providing services to the outside. Each service entity in a cluster is a node, and in a cluster, there is typically a master node and the rest are slave nodes. The slave node may store data; the master node may communicate with the various slave nodes and may invoke data stored by the slave nodes.
In the prior art, a master node in one cluster may communicate with not only slave nodes in the cluster, but also slave nodes in other clusters in a local area network. In specific implementation, the slave node is generally provided with an agent module which can call bottom layer services; and the main node is provided with a middleware module which can communicate with the slave nodes in each cluster through the agent module. Because the agent module of each slave node needs to respond to the instruction from the master nodes of different clusters, once one or more slave nodes in the clusters fail, the communication between each master node and the failed node is affected, and each master node needs to request the failed node at regular time; and the communication time between the main node and the fault node is far longer than that between the main node and the normal node, so the request response speed of the whole system is reduced. And, the larger the number of clusters in the local area network, the more serious the situation becomes.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a cluster node communication method in the prior art.
Fig. 1 shows an example of a cluster node communication method in the prior art by taking two clusters as an example, and as shown in fig. 1, each cluster is provided with 1 master node and a plurality of slave nodes. Wherein, the master node 1011 in the cluster 101 may directly communicate with the slave node 1022, the slave node 1023, the slave node 1024, etc. in the cluster 102, besides accessing the slave nodes in the cluster 101; similarly, master node 1021 in cluster 102 may communicate directly with slave node 1012, slave node 1013, slave node 1014, etc. in cluster 101, in addition to having access to slave nodes in cluster 102. When slave node 1012 fails, not only the communication with master node 1011 but also the communication with master node 1021 is affected. Because the communication time between the fault slave node and the master node is long, the request response speed of the whole system is reduced.
Disclosure of Invention
The present application aims to provide a cluster node communication method and system, so as to effectively avoid the decrease of the request response speed of the system when a cluster node fails.
In order to solve the above technical problem, the present application provides a cluster node communication method, including:
the method comprises the steps that a first main node obtains data of each slave node in a first cluster and caches the data; the first master node is located in a first cluster;
the first main node receives a calling request sent by a second main node for the data of the slave nodes in the first cluster; the second master node is located in a second cluster;
and the first host node acquires the data to be called requested by the second host node from the cache and returns the data to the second host node.
Optionally, the obtaining, by the first master node, data of each slave node in the first cluster, and caching the data includes:
a first middleware module of the first master node requests data from agent modules of all slave nodes in the first cluster;
each agent module responds to the request of the first middleware module and returns the data of each slave node to the first middleware module;
the first middleware module caches the data.
Optionally, the obtaining, by the first master node, data of each slave node in the first cluster, and caching the data includes:
the first main node acquires data of each slave node in the first cluster at regular time and caches the data so as to update the data.
Optionally, the method further comprises:
when a slave node in the first cluster fails, the first master node caches failure information of the failed slave node, and after receiving a call request for data of the failed slave node, the call request is sent to the second master node, and the failure information is sent to the second master node.
Optionally, the method further comprises:
when the failure recovers from a node, the first master node clears the failure information.
The application also provides a cluster node communication system, which comprises a plurality of clusters, wherein each cluster comprises a main node and a plurality of slave nodes;
a first master node in a first cluster to:
acquiring and caching data of each slave node in the first cluster; and after receiving a call request for the data of the slave node in the first cluster, which is sent by a second master node in a second cluster, obtaining the data to be called requested by the second master node from a cache, and returning the data to the second master node.
Optionally, the first host node is deployed with a first middleware module, where the first middleware module is specifically configured to:
requesting data from agent modules of respective slave nodes in the first cluster;
each agent module is specifically configured to:
and responding to the request of the first middleware module, and returning the data of each slave node to the first middleware module.
Optionally, the first master node is specifically configured to:
and acquiring data of each slave node in the first cluster at fixed time so as to update the data.
Optionally, wherein the first host node is further configured to:
when a slave node in the first cluster fails, caching fault information of the failed slave node, and when a call request for data of the failed slave node, which is sent by the second master node, is received, sending the fault information to the second master node.
Optionally, the first master node is further configured to:
clearing the fault information when the fault is recovered from a node.
In the cluster node communication method provided by the application, a first main node acquires data of each slave node in a first cluster and caches the data; the first master node is located in a first cluster; the first main node receives a calling request sent by a second main node for the data of the slave nodes in the first cluster; the second master node is located in a second cluster; and the first host node acquires the data to be called requested by the second host node from the cache and returns the data to the second host node.
Therefore, compared with the prior art, in the cluster node communication method provided by the application, the master node caches the data of the slave node in the cluster by using the master node, so that the master nodes in other clusters can access the master node to obtain the data of the slave node in the cluster where the master node is located, thereby avoiding direct communication between the fault slave node and the master nodes of other clusters, improving the access efficiency between the clusters, saving the communication time of the fault slave node responding to the master nodes of other clusters, and avoiding the reduction of the response speed of the system request. The cluster node communication system provided by the application can realize the cluster node communication method and also has the beneficial effects.
Drawings
In order to more clearly illustrate the technical solutions in the prior art and the embodiments of the present application, the drawings that are needed to be used in the description of the prior art and the embodiments of the present application will be briefly described below. Of course, the following description of the drawings related to the embodiments of the present application is only a part of the embodiments of the present application, and it will be obvious to those skilled in the art that other drawings can be obtained from the provided drawings without any creative effort, and the obtained other drawings also belong to the protection scope of the present application.
Fig. 1 is a schematic diagram of a cluster node communication method in the prior art;
fig. 2 is a flowchart of a cluster node communication method provided in an embodiment of the present application;
fig. 3 is a schematic diagram of a cluster node communication system provided in an embodiment of the present application.
Detailed Description
In order to more clearly and completely describe the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. 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 application.
Referring to fig. 2, fig. 2 is a flowchart of a cluster node communication method according to an embodiment of the present application, which mainly includes the following steps:
step 201: the first master node acquires data of each slave node in the first cluster.
A master node in a cluster may make data calls and manage all slave nodes within the cluster. For any cluster in the system, it is not called a first cluster, and the master node, that is, the first master node, needs to call data of each slave node in the first cluster to manage each slave node in the first cluster, so as to provide a service to the outside uniformly as a whole.
Specifically, a middleware module may be deployed on the master node of each cluster, an agent module may be deployed on each slave node in each cluster, and by using the middleware module and the agent module, the master node and each slave node may complete data transmission, that is, data of each slave node is collected into the master node of the cluster.
For a first cluster, a first middleware module is deployed on a first main node, and the first middleware module requests data from agent modules of all slave nodes in the first cluster; and each agent module on each slave node responds to the request of the first middleware module and respectively returns the data of the slave node to which each agent module is positioned to the first middleware module.
Step 202: the first master node caches the data.
Since the different clusters in the system also need the mutual access and data call, the data of the slave node in the first cluster is not only used for the call of the first master node, but also used for the call of the master nodes in other clusters. In order to avoid direct communication between each slave node in the first cluster and the master node in another cluster, so as to prevent the reduction of the response speed of the system when the node fails, the data of each slave node in the first cluster acquired by the first master node in step 201 may be fully utilized, that is, the data acquired in the process is used not only for the invocation of the first master node but also for the invocation of the master nodes in other clusters. In order to provide the data to be called to the master node in the other cluster when the master node makes a data call request, the first master node may cache the data of each slave node in the first cluster acquired in step 201 to be called by the master node in the other cluster.
It should be noted that, in the above steps 201 and 202, the first master node may perform operations of acquiring and caching data of each slave node in the first cluster at regular time, so as to update the data of each slave node in time, and ensure accuracy of the system data.
It should be noted that, if one or more slave nodes in the first cluster fail, the first master node may also cache the failure information of the failed slave node as a flag at this time; and when the failure recovers from the node, the first master node may clear the failure information it previously cached.
Step 203: and the first main node receives a call request for the data of the slave nodes in the first cluster, which is sent by the second main node.
As described above, in this embodiment of the present application, the master node of each cluster does not use a data calling manner for directly communicating with the slave nodes in other clusters, but uses a manner for calling data of the slave nodes cached by the master node in the cluster. Therefore, when the master node of the cluster needs to call the data of the slave nodes in other clusters, it only needs to send a call request to the master node of the cluster where the called slave node is located.
When data of a slave node in a first cluster needs to be called by a master node (not called a second master node) in another cluster (not called a second cluster), the first master node may receive a call request for the data of the slave node in the first cluster, which is sent by the second master node.
Step 204: and the first host node acquires the data to be called requested by the second host node from the cache and returns the data to the second host node.
The first host node responds to a data call request received by the first host node from the second host node, obtains data to be called requested by the second host node from the cache, and returns the data to the second host node, so that the second host node can finish using the data to be called.
Correspondingly, if the invocation request received by the first master node is directed to the data of the failed slave node in the first cluster, the first master node may send the failure information of the failed slave node to the data invoker, that is, the second master node.
As can be seen, in the cluster node communication method provided in the embodiment of the present application, the master node in another cluster may obtain the data of the slave node in the cluster by accessing the cache data of the master node in the cluster, that is, the slave node in one cluster only needs to respond to the data request of the master node in the cluster, and does not need to communicate with the master node in another cluster. Therefore, when one or more slave nodes in the cluster fail, only the communication between the failed node and the master node in the cluster is affected, and the master nodes in other clusters are not affected because the master nodes do not need to directly communicate with the failed node, so that the request response speed of the whole system can be prevented from being reduced. This benefit is even more pronounced, especially when the number of clusters within the system is high.
In addition, in the cluster node communication method provided by the application, the cluster slave nodes do not need to respond to the access of the master nodes in other clusters, and the coupling among the clusters is reduced, so that the load of the slave nodes in the clusters is greatly reduced, and the network overhead of a cluster system is greatly reduced; meanwhile, the stability and reliability of the system are also ensured due to the improvement of the cohesion in the cluster.
The cluster node communication system provided by the embodiment of the present application is introduced below. The cluster node communication system described below and the cluster node communication method described above may be referred to in correspondence with each other.
Referring to fig. 3, fig. 3 shows a schematic diagram of a cluster node communication system provided in the present application, taking two clusters as an example; the cluster 301 and the cluster 302 are included, wherein the cluster 301 includes a master node 3011 and a slave node 3012, and the cluster 302 includes a master node 3021 and a slave node 3022.
Taking the cluster 301 as an example, the master node 3011 is configured to obtain and cache data of each slave node 3012 in the cluster 301; and after receiving a call request for data of the slave node 3012 sent by the master node 3021 in the cluster 302, obtain data to be called requested by the master node 3021 from the cache, and return the data to the master node 3021.
Specifically, a first middleware module may be deployed in the master node 3011, and an agent module may be deployed in the slave node 3012; the master node 3011 requests data from agent modules of the slave nodes 3012 in the cluster 301 through a first middleware module thereof; the agent modules of the slave nodes 3012 respectively return the data of the slave nodes 3012 to the first middleware module in response to the request of the first middleware module.
As described above, the master node 3011 may execute in a timed manner when acquiring and caching data of each slave node 3012 in the cluster 301, so as to update the data and ensure accuracy of the system data.
It should be noted that when one or more slave nodes 3012 in the cluster 301 fail, the master node 3011 may also be configured to cache failure information of the failed slave node, and send the failure information of the failed slave node to the master node 3021 when receiving a call request for data of the failed slave node sent by the master node 3021. The master node 3011 may also be used to clear the failure information of the failed slave node when the failed slave node recovers.
It is easily understood that the above description of the cluster node communication system provided in the embodiment of the present application mainly refers to a general description taking the cluster 301 as an example, and through analogy, a person skilled in the art can obtain the same functional structures and implementation manners of other clusters (including the cluster 302 and the like) and the cluster 301 in the cluster node communication system of the present application, and similar contents are not repeated here.
Therefore, the cluster node communication system provided by the application utilizes the cache of the master node for the data of the slave nodes in the cluster, so that the master nodes in other clusters can access the master node to obtain the data of the slave nodes in the cluster. According to the method and the device, direct communication between the slave node of the cluster and the master nodes of other clusters is avoided, and the access efficiency between the clusters is improved, so that the communication time between the fault slave node and the master nodes in other clusters can be saved when the slave node fails, and the reduction of the response speed of the system request is avoided.
In addition, in the cluster node communication system provided by the application, the load of the cluster slave nodes is greatly reduced, so that the network overhead of the cluster system is also greatly reduced; meanwhile, as the cohesion in the cluster is improved, the cluster node communication system provided by the application can further improve the stability and reliability of the system.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the method steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The technical solutions provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A method for cluster node communication, comprising:
the method comprises the steps that a first main node obtains data of each slave node in a first cluster and caches the data; the first master node is located in the first cluster;
the first main node receives a calling request sent by a second main node for the data of the slave nodes in the first cluster; the second master node is located in a second cluster;
and the first host node acquires the data to be called requested by the second host node from the cache and returns the data to the second host node.
2. The cluster node communication method of claim 1, wherein the first master node obtaining data of each slave node in the first cluster and caching the data comprises:
a first middleware module of the first master node requests data from agent modules of all slave nodes in the first cluster;
each agent module responds to the request of the first middleware module and returns the data of each slave node to the first middleware module;
the first middleware module caches the data.
3. The cluster node communication method of claim 2, wherein the first master node obtaining data of each slave node in the first cluster and caching the data comprises:
the first main node acquires data of each slave node in the first cluster at regular time and caches the data so as to update the data.
4. The cluster node communication method according to any one of claims 1 to 3, further comprising:
when a slave node in the first cluster fails, the first master node caches failure information of the failed slave node, and after receiving a call request for data of the failed slave node, the call request is sent to the second master node, and the failure information is sent to the second master node.
5. The cluster node communication method of claim 4, further comprising:
when the failure recovers from a node, the first master node clears the failure information.
6. A cluster node communication system is characterized by comprising a plurality of clusters, wherein each cluster comprises a main node and a plurality of slave nodes;
a first master node in a first cluster to:
acquiring and caching data of each slave node in the first cluster; and after receiving a call request for the data of the slave node in the first cluster, which is sent by a second master node in a second cluster, obtaining the data to be called requested by the second master node from a cache, and returning the data to the second master node.
7. The cluster node communication system of claim 6, wherein the first master node is deployed with a first middleware module, and the first middleware module is specifically configured to:
requesting data from agent modules of respective slave nodes in the first cluster;
each agent module is specifically configured to:
and responding to the request of the first middleware module, and returning the data of each slave node to the first middleware module.
8. The cluster node communication system of claim 7, wherein the first master node is specifically configured to:
and acquiring data of each slave node in the first cluster at fixed time so as to update the data.
9. The cluster node communication system of any of claims 6 to 8, wherein the first master node is further configured to:
when a slave node in the first cluster fails, caching fault information of the failed slave node, and when a call request for data of the failed slave node, which is sent by the second master node, is received, sending the fault information to the second master node.
10. The cluster node communication system of claim 9, wherein the first master node is further configured to:
clearing the fault information when the fault is recovered from a node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710423270.7A CN107124469B (en) | 2017-06-07 | 2017-06-07 | Cluster node communication method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710423270.7A CN107124469B (en) | 2017-06-07 | 2017-06-07 | Cluster node communication method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107124469A CN107124469A (en) | 2017-09-01 |
| CN107124469B true CN107124469B (en) | 2020-07-24 |
Family
ID=59730129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710423270.7A Active CN107124469B (en) | 2017-06-07 | 2017-06-07 | Cluster node communication method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107124469B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108900643A (en) * | 2018-08-20 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of method and business processing device of business processing |
| CN109189339B (en) * | 2018-08-28 | 2021-08-20 | 郑州云海信息技术有限公司 | Automatic configuration cache acceleration method under storage system |
| CN109151057A (en) * | 2018-09-27 | 2019-01-04 | 郑州云海信息技术有限公司 | A kind of method of intelligent distributed storage cluster management |
| CN111381766B (en) * | 2018-12-28 | 2022-08-02 | 杭州海康威视系统技术有限公司 | Method for dynamically loading disk and cloud storage system |
| CN111010448B (en) * | 2019-12-23 | 2022-06-03 | 北京奇艺世纪科技有限公司 | Distributed message system and data center DC |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978371A (en) * | 2014-04-14 | 2015-10-14 | 阿里巴巴集团控股有限公司 | Data loading method for clustering system, data loading device for clustering system and clustering system |
| CN105187517A (en) * | 2015-08-20 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Metadata clustering method and metadata cluster |
| CN106357723A (en) * | 2016-08-15 | 2017-01-25 | 杭州古北电子科技有限公司 | Synchronous system and method for multi-cluster information caching based on cloud host |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016018262A1 (en) * | 2014-07-29 | 2016-02-04 | Hewlett-Packard Development Company, L.P. | Storage transactions |
| CN104462483A (en) * | 2014-12-18 | 2015-03-25 | 北京奇虎科技有限公司 | Data synchronizing method, device and system |
| CN105635279A (en) * | 2015-12-29 | 2016-06-01 | 长城信息产业股份有限公司 | Distributed monitor system and data acquisition method thereof |
-
2017
- 2017-06-07 CN CN201710423270.7A patent/CN107124469B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978371A (en) * | 2014-04-14 | 2015-10-14 | 阿里巴巴集团控股有限公司 | Data loading method for clustering system, data loading device for clustering system and clustering system |
| CN105187517A (en) * | 2015-08-20 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Metadata clustering method and metadata cluster |
| CN106357723A (en) * | 2016-08-15 | 2017-01-25 | 杭州古北电子科技有限公司 | Synchronous system and method for multi-cluster information caching based on cloud host |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107124469A (en) | 2017-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107124469B (en) | Cluster node communication method and system | |
| CN108234641B (en) | Data reading and writing method and device based on distributed consistency protocol | |
| US9658879B2 (en) | System and method for supporting buffer allocation in a shared memory queue | |
| CN106663033B (en) | System and method for supporting a wraparound domain and proxy model and updating service information for cross-domain messaging in a transactional middleware machine environment | |
| CN110597910A (en) | Remote data synchronization method, device and system | |
| CN104935654A (en) | Caching method, write point client and read client in server cluster system | |
| CN111274310A (en) | Distributed data caching method and system | |
| CN106713378B (en) | Method and system for providing service by multiple application servers | |
| US9390156B2 (en) | Distributed directory environment using clustered LDAP servers | |
| US20220137876A1 (en) | Method and device for distributed data storage | |
| US11347413B2 (en) | Opportunistic storage service | |
| CN111158949A (en) | Configuration method, switching method and device of disaster recovery architecture, equipment and storage medium | |
| CN104598615A (en) | Memory access method and device supporting data persistence | |
| US11461053B2 (en) | Data storage system with separate interfaces for bulk data ingestion and data access | |
| CN102917068A (en) | Self-adaptive large-scale cluster communication system and self-adaptive large-scale cluster communication method | |
| CN107491551B (en) | Method and device for realizing client access of distributed file system | |
| CN107193989B (en) | NAS cluster cache processing method and system | |
| Mahar et al. | Telepathic Datacenters: Efficient and High-Performance RPCs using Shared CXL Memory | |
| US9959238B1 (en) | Message passing among interdependent parallel processes using a shared memory | |
| CN104679688A (en) | Data access method, device and system | |
| US11841793B2 (en) | Switch-based free memory tracking in data center environments | |
| CN110958182B (en) | Communication method and related equipment | |
| CN118277285A (en) | Data access method, system and equipment | |
| CN115086173A (en) | Reliability guarantee method and device in network upgrading process | |
| CN105915644B (en) | Server load balancing method |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200628 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |