CN103051551A - Distributed system and automatic maintaining method for same - Google Patents
Distributed system and automatic maintaining method for same Download PDFInfo
- Publication number
- CN103051551A CN103051551A CN2011103102145A CN201110310214A CN103051551A CN 103051551 A CN103051551 A CN 103051551A CN 2011103102145 A CN2011103102145 A CN 2011103102145A CN 201110310214 A CN201110310214 A CN 201110310214A CN 103051551 A CN103051551 A CN 103051551A
- Authority
- CN
- China
- Prior art keywords
- service
- node
- message
- request
- log
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a distributed system and an automatic maintaining method for the same. The method comprises the following steps that after a node starts a service, a service registration request is sent to a service registry at regular time; and the service registry maintains local information according to the received service registration request and provides an information service for the node or a node related to the node. The scale of the distributed system disclosed by the invention can be dynamically shrunk; after the node starts the service, service registration can be automatically initiated without manual configuration; a network relation can be automatically formed between the nodes by a calling relation and can be dynamically regulated; and the network structure does not need to be planned in advance. Moreover, the system disclosed by the invention is simple to maintain and is low in construction cost.
Description
Technical field
The present invention relates to the distributed computing technology in the cloud computing field, relate in particular to a kind of distributed system and automatic maintenance method thereof.
Background technology
Growing along with the user of the Internet, conventional telecommunications net and application, and both merge the continuous reinforcement of (becoming mobile Internet) trend, the data traffic by server and access request are also in continuous growth.This to the deployment of server and maintenance, operation thereon software performance and the scalability of whole system more and more higher demand has been proposed.For these demands, prior art has proposed the distributed computing system of some replies.When server is too busy, by increasing load-balancing device and the number of servers of system, perhaps promote its disposal ability by the hardware and software performance that promotes individual server.Because server high cost, performance growth potential are limited, it is not the solution of main flow that its performance is promoted.
Fig. 1 is a kind of distributed system that prior art proposes, and as shown in Figure 1, this system supports one group of server by load-balancing device, and load-balancing device is placed on the front end of Servers-all, outwards the unified interface that exposes service.Load-balancing device may be hardware, such as the fourth layer machine; Also may be software, such as some reverse proxy software.This system generally is applied on the website of the Internet, and its design philosophy is by load-balancing device numerous WEB servers to be formed cluster, thereby provides single HTML service to the user.This system is serving (application) when increasing, need to set up new load-balancing device, because each service needs one group of server to support, and each group server all uses a load-balancing device, this will certainly cause the rapid rising of lower deployment cost, and load-balancing device also can can't bear the heavy load because of rolling up of access request.In addition, when the newly-increased one group of service of internal system, server address that client computer can not these newly-increased services of automatic sensing, must a series of manual configuration of process after access request could be sent to smoothly new server.It is very difficult, poor efficiency that such manual configuration is done by the data center that has hundreds and thousands of station servers in the modern times.
Therefore, there are the shortcomings such as lower deployment cost is too high, later maintenance is difficult, system robustness is poor in this distributed system, and the service of can not solving of this system and user increase the problems such as server performance bottleneck of bringing.
Fig. 2 is the another kind of distributed system that prior art proposes, and as shown in Figure 2, this system supports one group of service by ESB (Enterprise Service Bus, ESB) server, and all access request all need to transmit by the ESB server.The ESB server provides load-balancing mechanism based on SOA (Service-Oriented Architecture, Service-Oriented Architecture Based) thought, and newly-increased service also is transparent to client computer.Yet the ESB server itself has been born too many function, has single point failure hidden danger and unit performance bottleneck.On the other hand, when the newly-increased a kind of service of this system or service node, need to be on the ESB server manual registration, have problem difficult in maintenance, that scalability is poor.Another restriction of ESB server is, usually it is the service that directly outwards exposes, can not mutually call between the internal services, thus it generally be applied to enterprise need to be with numerous system combinations in inside and the situation of standards service externally is provided, and be not suitable for the large-scale distributed system that makes up.
Summary of the invention
The object of the invention is to, a kind of distributed system and automatic maintenance method thereof are provided, the problem such as the existing existing lower deployment cost of distributed system is too high, performance bottleneck is serious, later maintenance is difficult to solve, system robustness and retractility are poor.
The present invention solves the problems of the technologies described above by the following technical programs:
A kind of automatic maintenance method of large scale distributed system, said method may further comprise the steps:
After node starts service, regularly send the service registry request to service register center;
Above-mentioned service register center is safeguarded local information, and is provided information service to above-mentioned node or its associated nodes according to the service registry request of receiving.
According to said method, above-mentioned node comprises the node of node that service is provided and transfer service, the log-on message that comprises above-mentioned node in the above-mentioned service registry request, but IP address, port numbers and the above-mentioned node transfer of above-mentioned node or the service name that provides are provided above-mentioned log-on message.
Above-mentioned service register center adopts following methods that local information is safeguarded:
According to the log-on message in the above-mentioned registration service request, judge the whether first registration of above-mentioned node, if, then above-mentioned log-on message is saved in the local node chained list, otherwise the old log-on message of above-mentioned node in above-mentioned log-on message and the above-mentioned node chained list is compared, then upgrade above-mentioned node chained list with above-mentioned log-on message if both are inconsistent.
Above-mentioned service register center is saved in above-mentioned log-on message in the local node chained list or upgrades after the above-mentioned node chained list further comprising the steps of with above-mentioned log-on message:
Judge that whether above-mentioned node is for providing the node of service;
If, then the log-on message of above-mentioned node is sent to the associated nodes of using above-mentioned node service, otherwise, the log-on message of the destination node under its service of wanting transfer is provided to above-mentioned node.
Said method comprises that also following above-mentioned node calls the step of service:
Above-mentioned node at first sends service invocation request to above-mentioned service register center;
After above-mentioned service register center is received above-mentioned call request, but with transfer or provide the log-on message of all destination nodes of above-mentioned node required service to return to above-mentioned node;
Above-mentioned node is preserved the log-on message of destination node, and obtains the loading condition of each destination node, and then the destination node to least-loaded sends service invocation request;
After the destination node of above-mentioned least-loaded was received above-mentioned call request, the service that above-mentioned node is needed returned to above-mentioned node.
According to said method, after above-mentioned service register center is received above-mentioned call request, but with transfer or provide the log-on message of all destination nodes of above-mentioned node required service to return to above-mentioned node step to comprise:
The service that above-mentioned service register center will be called above-mentioned node is saved in the local above-mentioned node chained list;
Judged whether the above-mentioned service of node transfer according to the above-mentioned node chained list in this locality, if, but then the log-on message of all destination nodes of the above-mentioned service of transfer is sent to above-mentioned node, otherwise, judged whether that node provides above-mentioned service;
If, then can provide the log-on message of all destination nodes of above-mentioned service to send to above-mentioned node, otherwise the information of return service request failure.
Above-mentioned node adopts following methods to obtain the loading condition of each above-mentioned destination node:
According to the log-on message of above-mentioned destination node, regularly send the heartbeat message of self to each destination node;
After each destination node is received heartbeat message, self heartbeat message is returned to above-mentioned node;
Above-mentioned node obtains its loading condition according to the heartbeat message of each destination node.
Above-mentioned heartbeat message comprises IP address and the load data of node.
After above-mentioned node has been preserved the log-on message of destination node, if next time is when asking above-mentioned service again, skip step from service invocation request to above-mentioned service register center that send, directly the destination node to least-loaded sends service invocation request, until till asking unsuccessfully.
The automatic maintenance method of above-mentioned distributed system also comprises: when above-mentioned node not during the request of timed sending server registration, above-mentioned service register center is deleted the log-on message that above-mentioned node is preserved in this locality.
The present invention is also by the following technical solutions:
A kind of distributed system comprises node and service register center;
Above-mentioned node is used for regularly sending the service registry request to service register center after starting service;
Above-mentioned service register center is used for local information being safeguarded, and being provided information service to above-mentioned node or its associated nodes according to the service registry request of receiving.
Above-mentioned node comprises information registering module, service request module, optional service providing module, reaches the service reception module;
Above-mentioned information registering module is used for regularly sending the service registry request to above-mentioned service register center;
Above-mentioned service request module is used for sending service invocation request to above-mentioned service register center or other nodes;
Above-mentioned service providing module, after being used for receiving service invocation request, the service that self is provided returns to corresponding node;
Above-mentioned service reception module is used for receiving the service that other nodes provide.
Above-mentioned service register center comprises maintenance of information module, Service Notification module, reaches the service response module;
Above-mentioned maintenance of information module is used for receiving the registration request of above-mentioned node, and safeguards according to the nodal information that above-mentioned registration request is preserved this locality;
Above-mentioned Service Notification module, the nodal information that is used for increasing newly or upgrading sends to other associated nodes, or provides nodal information under its service of wanting transfer to above-mentioned node newly-increased or that upgrade;
Above-mentioned service response module is used for after receiving the service invocation request that above-mentioned node sends, but with transfer or provide the nodal information of respective service to return to above-mentioned node.
Compared with prior art, the present invention has following useful technique effect:
1) Automatic service discovery: need to manually arrange when the new service registry differently from traditional distributed system, can register its COS from the trend service register center after service node of the present invention starts; When other nodes need to be asked this service, just can obtain serving the position by service register center.The benefit that this characteristic is brought is that network configuration is simple, communication link can be set up automatically according to the call relation between the node, (legacy system is wanted advance planning usually not need network configuration between the advance planning node, also can't dynamically adjust), this has made things convenient in data center and has dynamically increased or deletion of node;
2) automatic equalization load: node of the present invention selects the node of least-loaded to set up communication link when the service that the request target node provides automatically, the concurrent affair call request that takes.Thereby in the situation of not introducing conventional load equalizer equipment, the present invention also can realize the load balancing between the node.This not only provides cost savings, and has also eliminated single point failure hidden danger and the single-point performance bottleneck of single load equalizer simultaneously, and system robustness is stronger;
3) scale is flexible convenient: be loosely-coupled between the node of the present invention, and any node failure even service register center fault, the system that can not affect continues operation, and increase or deletion of node only are to impel the service request amount to redistribute between node; Therefore, the scale of system of the present invention is flexible very convenient, is conducive to make up large-scale distributed computing system;
4) service relative is independent: node of the present invention is sending registration request, request call service, is not all relating to the service (software) that node self moves when obtaining loading condition, be that software itself does not participate in these functions, these functions are finished automatically by the communications framework of node bottom, and software only need be paid close attention to the realization of service logic.This has reduced the service development difficulty of distributed computing system.
Description of drawings
Accompanying drawing described herein is used to provide a further understanding of the present invention, consists of a part of the present invention, and illustrative examples of the present invention and explanation thereof are used for explaining the present invention, do not consist of improper restriction of the present invention.In the accompanying drawings:
Fig. 1 is the structural representation of a kind of distributed system of prior art proposition;
Fig. 2 is the structural representation of the another kind of distributed system of prior art proposition;
Fig. 3 is the structural representation of distributed system preferred embodiment of the present invention;
The flow chart of the automatic maintenance method preferred embodiment of Fig. 4 distributed system of the present invention;
Fig. 5 is the module frame chart of distributed system preferred embodiment of the present invention.
Embodiment
In order to make technical problem to be solved by this invention, technical scheme and beneficial effect clearer, clear, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, is not intended to limit the present invention.
Fig. 3 is the structural representation of distributed system preferred embodiment of the present invention.As shown in Figure 3, distributed system in the embodiment of the invention has a plurality of nodes, the node (transit node) that comprises node (service node) that service is provided and transfer service, the hardware of each node can be less expensive computer, but the retractility that the dependence system is powerful, system can provide very powerful computing capability on the whole.Can set up communication link by computer bottom communication framework between node and node, node and the service register center, TCP communication link for example is to realize continuing to the other side the function of transmission information or service.
A node can be set up with it communication link after obtaining the log-on message of other nodes, and sends service invocation request to it.Service register center forms as the core of system, has preserved the log-on message of all nodes, comprise all nodes IP address, port numbers, and node provides or the service of transfer.Each service can be distributed in a plurality of service nodes, and namely one group of service node can provide the same COS.Transit node can the transfer service, but (providing) service itself is not provided, so transit node is optional, but transit node can be simplified the network topology structure of system.For example, when service node 1 will call service B among Fig. 3, because service node 4 and 5 can provide this service, so must obtain the log-on message of service node 4 and 5 to service register center first, then judge their loading condition, ask again the little service node of load to return required service.And if be provided with transit node 1, service node 1 only needs that service invocation request is sent to transit node 1 and gets final product.
It should be noted that, present embodiment service node 1 is behind the log-on message that obtains service node 4 and 5, can regularly send heartbeat message to service node 4 and 5, service node 1 not only can obtain the other side's loading condition thus, can also grasp the information of the other side's fault/withdraw from when not receiving the other side's heartbeat message.For example, when if service node 1 is not received the heartbeat message of service node 5, service node 1 judgement service node 5 faults/withdraw from, this moment, it no longer sent to service invocation request service node 5, until service register center notifies its service node 5 to restart.
Need to prove in addition, the distributed system scale of present embodiment can dynamic retractility, Fig. 3 has just schematically provided two groups of services of A, B, in fact the present invention can support unlimited many services, simultaneously the present invention can increase new service or transit node as required at any time with the elevator system performance, also can be when service request tails off the closed portion service node.The adding of node and to withdraw from all be dynamic, need not manual the setting, this is because the present invention safeguards each node and log-on message thereof automatically by service register center, new node adds fashionable meeting and initiates registration to service register center, other associated nodes can be obtained rapidly the information of new node by service register center, just the part service invocation request are shared on the new node.In addition because node is to want regularly to send log-on message to service register center, therefore when certain node withdraws from, service registry information is rapid this situation of perception just, and this nodal information deleted from this locality, and other associated nodes are broken by stopping of receiving of heartbeat message, also can detect immediately this situation, new service invocation request will not re-send to this node.
Below on the whole the structure of distributed system of the present invention and (operation) mechanism of safeguarding thereof are had been described in detail, be elaborated below in conjunction with the automatic maintenance method of 4 pairs of distributed systems provided by the invention of accompanying drawing.
The flow chart of the automatic maintenance method preferred embodiment of Fig. 4 distributed system of the present invention, as shown in Figure 4, the method for the preferred embodiment of the present invention may further comprise the steps:
Step S1: after node starts service, regularly send the service registry request to service register center;
After a node starts service, it begins regularly to send the service registry request to service register center, but IP address, port numbers and the node transfer of node or the service name that provides are provided above-mentioned registration request, but wherein node transfer or the service that provides can be one or more.By the above-mentioned registration request of timed sending, service register center can in time be understood the ruuning situation of node, and knows the information that node breaks down or logs off when not receiving the registration request that node is regularly sent.
Step S2: the service registry request that the service register center receiving node is sent;
Step S3: service register center is safeguarded local information according to the service registry request of receiving;
Service register center is safeguarded local information by the following method:
According to the log-on message in the above-mentioned registration service request, judge the whether first registration of above-mentioned node, if, then above-mentioned log-on message is saved in the local node chained list, otherwise the old log-on message of above-mentioned node in above-mentioned log-on message and the above-mentioned node chained list is compared, then upgrade above-mentioned node chained list with above-mentioned log-on message if both are inconsistent.
Step S4: service register center provides information service to above-mentioned node or its associated nodes;
Service register center adopts following methods to provide information service to above-mentioned node or its associated nodes:
Judge that whether above-mentioned node is for providing the node of service:
If then the log-on message of above-mentioned node is sent to the associated nodes of using above-mentioned node service, otherwise provide the log-on message of the destination node under its service of wanting transfer to above-mentioned node.
By step S4, when having service node to add or upgrading, need to use other nodes of this node service just can know rapidly this node situation by service register center, and service request is shared on this node.When having transit node to add or to upgrade, transit node also can be known rapidly by service register center nodal information under its service of wanting transfer when it receives the service invocation request of node, just can be transmitted to service node with request thus.
Step S5: above-mentioned node sends service invocation request to service register center;
The service that need to use certain node A to provide when above-mentioned node, and when the log-on message of node A is not recorded in above-mentioned node this locality, can send service invocation request to service register center, the log-on message of this node of acquisition request A, comprise IP address, service port number etc., thereby A sets up communication linkage with this node, and obtains the service that it provides.
Step S6: service register center receives above-mentioned request, but with transfer or provide the log-on message of the destination node of above-mentioned node required service to return to above-mentioned node;
After service register center was received above-mentioned request, the service that at first above-mentioned node need to be called was stored in this locality, in order to have new node to add and when its required service can be provided follow-up, the log-on message of new node was initiatively returned to above-mentioned node;
Then but the node chained list information according to local record judges whether the required service of the above-mentioned node of node transfer, if, whether then but the log-on message with the destination node of the above-mentioned node required service of transfer sends to above-mentioned node, have node can provide above-mentioned node required service otherwise search;
If then can provide the log-on message of all destination nodes of above-mentioned node required service to send to above-mentioned node, if not the information of return service request failure then.
For example, service node 1 among Fig. 3 needs the service B of request call address of service the unknown, then service node 1 sends the service invocation request of service B to service register center by the bottom communication framework, after service register center is received request, at first service node 1 is needed to use the information recording/of service B in the local node chained list, then but whether inquiry has node transfer service B, found that transit node 1 can transfer service B, so the log-on message of transit node 1 is sent to service node 1.Suppose transit node 1 fault or log off, then but the service register center inquiry finds not have node transfer service B, so whether inquiry has node that service B is provided, found that presence service node 4 and service node 5 can provide direct service B, this moment, service register center sent to service node 1 with the log-on message of service node 4 and service node 5.
Step S7: above-mentioned node is preserved the log-on message of destination node, obtains the loading condition of each destination node, and sends service invocation request to the destination node of least-loaded;
But above-mentioned node is after receiving transfer or the log-on message of all destination nodes of self required service is provided, the log-on message of these destination nodes is kept at this locality, so that next time is in the time of will calling the service that these destination nodes provide again, skip the step that sends service invocation request to service register center, directly the destination node to least-loaded sends service invocation request, until certain when ask unsuccessfully just again to service register center transmission service invocation request.
Above-mentioned node adopts following methods to obtain the loading condition of each destination node:
According to the log-on message of each destination node, regularly send the heartbeat message of self to each destination node; After each destination node is received the heartbeat message of above-mentioned node, separately heartbeat message is returned to above-mentioned node; Above-mentioned node receives the heartbeat message of each destination node, and therefrom obtains the loading condition of each destination node.
Because described heartbeat message comprises IP address and the load data of node self, therefore above-mentioned node by with the destination node hop-information of making up one's mind mutually, and can obtain the other side's loading condition.Above-mentioned node not only can obtain the other side's loading condition by regularly sending heartbeat message to each destination node, can also grasp the more information such as whether destination node breaks down or log off.For example, when above-mentioned node is not received the heartbeat message that certain destination node returns, can judge that this destination node breaks down or logs off, this destination node will be no longer issued in after this service registry request.
For example suppose in previous step S6, when the service node 1 among Fig. 3 is served B to the service register center request call, received the log-on message of service node 4 and service node 5, then in step S7, service node 1 at first is stored in this locality with the log-on message of service node 4 and service node 5, then send heartbeat message to service node 4 and service node 5 respectively, to obtain their loading condition, a less node of selection and load is set up communication link at last, and sends service invocation request to it.
Step S8: after the node of least-loaded was received service invocation request, the service that above-mentioned node is required returned to above-mentioned node;
When the node of above-mentioned least-loaded is transit node, after it receives above-mentioned request, above-mentioned request is transmitted to the node that above-mentioned service can directly be provided, and request results is returned to above-mentioned node; When the node of above-mentioned least-loaded was service node, after it received above-mentioned request, directly the service that above-mentioned node is required returned to above-mentioned node.
Step S9: when above-mentioned node not during the request of timed sending server registration, service register center is deleted the log-on message that above-mentioned node is preserved in this locality.
Fig. 5 is the module frame chart of distributed system preferred embodiment of the present invention, and as shown in Figure 5, the distributed system of the preferred embodiment of the present invention comprises: node 51 and service register center 52;
Above-mentioned node 51 is used for after starting service, regularly sends the service registry request to service register center 52;
Above-mentioned service register center 52 is used for local information being safeguarded, and being provided information service to above-mentioned node 51 or its associated nodes according to the service registry request of receiving.
Above-mentioned node 51 comprises information registering module 511, service request module 512, optional service providing module 513, reaches service reception module 514;
Above-mentioned information registering module 511 is used for regularly sending the service registry request to above-mentioned service register center 52;
Above-mentioned service request module 512 is used for sending service invocation request to above-mentioned service register center 52 or other nodes;
Above-mentioned service providing module 513 is used for after receiving service invocation request, and the service that self is provided returns to corresponding node;
Above-mentioned service reception module 514 is used for receiving the service that other nodes provide.
Above-mentioned service register center 52 comprises maintenance of information module 521, Service Notification module 522, reaches service response module 523;
Above-mentioned maintenance of information module 521 is used for receiving the registration request of above-mentioned node 51, and safeguards according to the nodal information that above-mentioned registration request is preserved this locality;
Above-mentioned Service Notification module 522, the nodal information that is used for increasing newly or upgrading sends to other associated nodes, or provides nodal information under its service of wanting transfer to above-mentioned node newly-increased or that upgrade;
Above-mentioned service response module 523 is used for after receiving the service invocation request that above-mentioned node 51 sends, but with transfer or provide the destination node information of respective service to return to above-mentioned node 51.
Above-mentioned explanation illustrates and has described the preferred embodiments of the present invention, but as previously mentioned, be to be understood that the present invention is not limited to the disclosed form of this paper, should not regard the eliminating to other embodiment as, and can be used for various other combinations, modification and environment, and can in invention contemplated scope described herein, change by technology or the knowledge of above-mentioned instruction or association area.And the change that those skilled in the art carry out and variation do not break away from the spirit and scope of the present invention, then all should be in the protection range of claims of the present invention.
Claims (13)
1. the automatic maintenance method of a distributed system is characterized in that, said method comprising the steps of:
After node starts service, regularly send the service registry request to service register center;
Described service register center is safeguarded local information, and is provided information service to described node or its associated nodes according to the service registry request of receiving.
2. method according to claim 1, it is characterized in that: described node comprises the node of node that service is provided and transfer service, the log-on message that comprises described node in the described service registry request, but IP address, port numbers and the described node transfer of described node or the service name that provides are provided described log-on message.
3. method according to claim 2 is characterized in that, described service register center adopts following methods that local information is safeguarded:
According to the log-on message in the described registration service request, judge the whether first registration of described node, if, then described log-on message is saved in the local node chained list, otherwise the old log-on message of node described in described log-on message and the described node chained list is compared, then upgrade described node chained list with described log-on message if both are inconsistent.
4. method according to claim 3 is characterized in that, described service register center is saved in described log-on message in the local node chained list or upgrades after the described node chained list further comprising the steps of with described log-on message:
Judge that whether described node is for providing the node of service;
If, then the log-on message of described node is sent to the associated nodes of using described node service, otherwise, the log-on message of the destination node under its service of wanting transfer is provided to described node.
5. method according to claim 4, it is characterized in that: described method comprises that also node calls the step of service:
Described node at first sends service invocation request to described service register center;
After described service register center is received described call request, but with transfer or provide the log-on message of all destination nodes of described node required service to return to described node;
Described node is preserved the log-on message of destination node, and obtains the loading condition of each destination node, and then the destination node to least-loaded sends service invocation request;
After the destination node of described least-loaded was received described call request, the service that described node is needed returned to described node.
6. method according to claim 5 is characterized in that, after described service register center is received described call request, but with transfer or provide the log-on message of all destination nodes of described node required service to return to described node step to comprise:
The service that described service register center will be called described node is saved in the local described node chained list;
Judged whether the described service of node transfer according to the described node chained list in this locality, if, but then the log-on message of all destination nodes of the described service of transfer is sent to described node, otherwise, judged whether that node provides described service;
If, then can provide the log-on message of all destination nodes of described service to send to described node, otherwise the information of return service request failure.
7. method according to claim 5 is characterized in that, described node adopts following methods to obtain the loading condition of each described destination node:
According to the log-on message of described destination node, regularly send the heartbeat message of self to each destination node;
After described destination node is received heartbeat message, self heartbeat message is returned to described node;
Described node obtains its loading condition according to the heartbeat message of destination node.
8. method according to claim 7, it is characterized in that: described heartbeat message comprises IP address and the load data of node.
9. method according to claim 5, it is characterized in that: after described node has been preserved the log-on message of destination node, if next time is when asking described service again, skip step from service invocation request to described service register center that send, directly the destination node to least-loaded sends service invocation request, until till asking unsuccessfully.
10. method according to claim 1 is characterized in that, described method also comprises: when described node not during the request of timed sending server registration, described service register center is deleted the log-on message that described node is preserved in this locality.
11. a distributed system comprises node, characterized by further comprising: service register center;
Described node is used for regularly sending the service registry request to service register center after starting service;
Described service register center is used for local information being safeguarded, and being provided information service to described node or its associated nodes according to the service registry request of receiving.
12. system according to claim 11 is characterized in that: described node comprises information registering module, service request module, optional service providing module, reaches the service reception module;
Described information registering module is used for regularly sending the service registry request to described service register center;
Described service request module is used for sending service invocation request to described service register center or other nodes;
Described service providing module is used for after receiving service invocation request, and the service that self is provided returns to corresponding node;
Described service reception module is used for receiving the service that other nodes provide.
13. system according to claim 11 is characterized in that: described service register center comprises maintenance of information module, Service Notification module, reaches the service response module;
Described maintenance of information module is used for receiving the registration request of described node, and safeguards according to the nodal information that described registration request is preserved this locality;
Described Service Notification module, the nodal information that is used for increasing newly or upgrading sends to other associated nodes, or provides nodal information under its service of wanting transfer to described node newly-increased or that upgrade;
Described service response module is used for after receiving the service invocation request that described node sends, but with transfer or provide the nodal information of respective service to return to described node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110310214.5A CN103051551B (en) | 2011-10-13 | 2011-10-13 | A kind of distributed system and its automatic maintenance method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110310214.5A CN103051551B (en) | 2011-10-13 | 2011-10-13 | A kind of distributed system and its automatic maintenance method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103051551A true CN103051551A (en) | 2013-04-17 |
| CN103051551B CN103051551B (en) | 2017-12-19 |
Family
ID=48064056
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110310214.5A Active CN103051551B (en) | 2011-10-13 | 2011-10-13 | A kind of distributed system and its automatic maintenance method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103051551B (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103457870A (en) * | 2013-09-25 | 2013-12-18 | 武汉理工大学 | Load-balancing and high-availability sub system used for distribution-type system and method |
| CN103577256A (en) * | 2013-11-21 | 2014-02-12 | 五八同城信息技术有限公司 | Distributed timed task dispatching system |
| CN103780434A (en) * | 2014-02-18 | 2014-05-07 | 成都致云科技有限公司 | Unattended operation automatic networking method of large-type distribution type system |
| CN103986748A (en) * | 2014-04-22 | 2014-08-13 | 世纪禾光科技发展（北京）有限公司 | Method and device for achieving servitization |
| WO2014173341A1 (en) * | 2013-08-22 | 2014-10-30 | 中兴通讯股份有限公司 | Load balancing method and system |
| CN105407161A (en) * | 2015-11-30 | 2016-03-16 | 北京奇艺世纪科技有限公司 | Application service management method and system as well as application service discovery method and system |
| CN105915583A (en) * | 2016-03-28 | 2016-08-31 | 联想(北京)有限公司 | Method for starting service cluster, and service cluster |
| CN106210120A (en) * | 2016-07-29 | 2016-12-07 | 广州仕邦人力资源有限公司 | A kind of recommendation method of server and device thereof |
| CN106453539A (en) * | 2016-09-28 | 2017-02-22 | 广州市百果园网络科技有限公司 | Method and system for processing node registration notice |
| CN106790084A (en) * | 2016-12-22 | 2017-05-31 | 中国科学院电子学研究所苏州研究院 | A kind of heterogeneous resource integrated framework and its integrated approach based on ICE middlewares |
| CN106874155A (en) * | 2015-12-14 | 2017-06-20 | 中国航空工业第六八研究所 | A kind of dynamic monitoring and controlling method of embedded software developing stage for target machine |
| CN107147466A (en) * | 2017-07-20 | 2017-09-08 | 郑州云海信息技术有限公司 | A kind of control method and system of system time uniformity |
| CN109040311A (en) * | 2018-09-17 | 2018-12-18 | 中国联合网络通信集团有限公司 | The push processing method and device of information on services |
| CN109120717A (en) * | 2018-09-26 | 2019-01-01 | 中国平安人寿保险股份有限公司 | Reverse proxy method, apparatus and storage medium, distributed system |
| CN109218355A (en) * | 2017-06-30 | 2019-01-15 | 华为技术有限公司 | Load equalizing engine, client, distributed computing system and load-balancing method |
| CN109829093A (en) * | 2018-12-29 | 2019-05-31 | 深圳云天励飞技术有限公司 | A kind of method and device of search |
| CN110971702A (en) * | 2019-12-10 | 2020-04-07 | 中国建设银行股份有限公司 | Service calling method and device, computer equipment and storage medium |
| CN111262916A (en) * | 2020-01-10 | 2020-06-09 | 深圳市网心科技有限公司 | Data distributed storage method and device, storage node and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1925444A (en) * | 2006-09-14 | 2007-03-07 | 华为技术有限公司 | Method for establishing point-to-point collection in P2P network and nodes in P2P network |
| CN101378327A (en) * | 2007-08-29 | 2009-03-04 | ***通信集团公司 | Communication network system and method for processing communication network business |
| CN101997759A (en) * | 2009-08-10 | 2011-03-30 | 中兴通讯股份有限公司 | Service implementation method and service system |
-
2011
- 2011-10-13 CN CN201110310214.5A patent/CN103051551B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1925444A (en) * | 2006-09-14 | 2007-03-07 | 华为技术有限公司 | Method for establishing point-to-point collection in P2P network and nodes in P2P network |
| CN101378327A (en) * | 2007-08-29 | 2009-03-04 | ***通信集团公司 | Communication network system and method for processing communication network business |
| CN101997759A (en) * | 2009-08-10 | 2011-03-30 | 中兴通讯股份有限公司 | Service implementation method and service system |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014173341A1 (en) * | 2013-08-22 | 2014-10-30 | 中兴通讯股份有限公司 | Load balancing method and system |
| CN104426936A (en) * | 2013-08-22 | 2015-03-18 | 中兴通讯股份有限公司 | Load balancing method and system |
| CN103457870B (en) * | 2013-09-25 | 2016-06-29 | 武汉理工大学 | For the load balancing of distributed system and high availability subsystem and method |
| CN103457870A (en) * | 2013-09-25 | 2013-12-18 | 武汉理工大学 | Load-balancing and high-availability sub system used for distribution-type system and method |
| CN103577256B (en) * | 2013-11-21 | 2017-03-15 | 五八同城信息技术有限公司 | Distributed timing task scheduling system |
| CN103577256A (en) * | 2013-11-21 | 2014-02-12 | 五八同城信息技术有限公司 | Distributed timed task dispatching system |
| CN103780434A (en) * | 2014-02-18 | 2014-05-07 | 成都致云科技有限公司 | Unattended operation automatic networking method of large-type distribution type system |
| CN103986748A (en) * | 2014-04-22 | 2014-08-13 | 世纪禾光科技发展（北京）有限公司 | Method and device for achieving servitization |
| CN103986748B (en) * | 2014-04-22 | 2019-01-25 | 数贸科技（北京）有限公司 | The method and apparatus of the serviceization of realization |
| CN105407161A (en) * | 2015-11-30 | 2016-03-16 | 北京奇艺世纪科技有限公司 | Application service management method and system as well as application service discovery method and system |
| CN106874155A (en) * | 2015-12-14 | 2017-06-20 | 中国航空工业第六八研究所 | A kind of dynamic monitoring and controlling method of embedded software developing stage for target machine |
| CN105915583A (en) * | 2016-03-28 | 2016-08-31 | 联想(北京)有限公司 | Method for starting service cluster, and service cluster |
| CN106210120B (en) * | 2016-07-29 | 2019-07-09 | 广州南方仕通网络科技有限公司 | A kind of recommended method and its device of server |
| CN106210120A (en) * | 2016-07-29 | 2016-12-07 | 广州仕邦人力资源有限公司 | A kind of recommendation method of server and device thereof |
| CN106453539B (en) * | 2016-09-28 | 2019-04-05 | 广州市百果园网络科技有限公司 | A kind of method and system of processing Node registry notice |
| US11343787B2 (en) | 2016-09-28 | 2022-05-24 | Bigo Technology Pte. Ltd. | Method and system for processing node registration notification |
| CN106453539A (en) * | 2016-09-28 | 2017-02-22 | 广州市百果园网络科技有限公司 | Method and system for processing node registration notice |
| WO2018059354A1 (en) * | 2016-09-28 | 2018-04-05 | 广州市百果园网络科技有限公司 | Method and system for processing node registration notification |
| CN106790084A (en) * | 2016-12-22 | 2017-05-31 | 中国科学院电子学研究所苏州研究院 | A kind of heterogeneous resource integrated framework and its integrated approach based on ICE middlewares |
| CN109218355A (en) * | 2017-06-30 | 2019-01-15 | 华为技术有限公司 | Load equalizing engine, client, distributed computing system and load-balancing method |
| CN107147466B (en) * | 2017-07-20 | 2019-03-12 | 郑州云海信息技术有限公司 | A kind of control method and system of system time consistency |
| CN107147466A (en) * | 2017-07-20 | 2017-09-08 | 郑州云海信息技术有限公司 | A kind of control method and system of system time uniformity |
| CN109040311B (en) * | 2018-09-17 | 2021-07-20 | 中国联合网络通信集团有限公司 | Service information push processing method and device |
| CN109040311A (en) * | 2018-09-17 | 2018-12-18 | 中国联合网络通信集团有限公司 | The push processing method and device of information on services |
| CN109120717A (en) * | 2018-09-26 | 2019-01-01 | 中国平安人寿保险股份有限公司 | Reverse proxy method, apparatus and storage medium, distributed system |
| CN109120717B (en) * | 2018-09-26 | 2023-07-25 | 中国平安人寿保险股份有限公司 | Reverse proxy method, device, storage medium and distributed system |
| CN109829093A (en) * | 2018-12-29 | 2019-05-31 | 深圳云天励飞技术有限公司 | A kind of method and device of search |
| CN110971702A (en) * | 2019-12-10 | 2020-04-07 | 中国建设银行股份有限公司 | Service calling method and device, computer equipment and storage medium |
| CN111262916A (en) * | 2020-01-10 | 2020-06-09 | 深圳市网心科技有限公司 | Data distributed storage method and device, storage node and storage medium |
| CN111262916B (en) * | 2020-01-10 | 2022-11-08 | 深圳市网心科技有限公司 | Data distributed storage method and device, storage node and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103051551B (en) | 2017-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103051551A (en) | Distributed system and automatic maintaining method for same | |
| US10491523B2 (en) | Load distribution in data networks | |
| CN105721473B (en) | A kind of method and system of WEB terminal far call optimization | |
| WO2012086919A2 (en) | Distributed storage system including plurality of proxy servers, method for managing object thereof, and storage medium readable by computer | |
| US20090319686A1 (en) | Communication route selecting method and apparatus | |
| CN103401909B (en) | Data interactive method based on BS and system, client and server | |
| CN109660466A (en) | A kind of more live load balance realizing methods towards cloud data center tenant | |
| CN109189856A (en) | Distributed data base service management, device, server and storage medium | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| CN103209223A (en) | Distributed application conversation information sharing method and system and application server | |
| CN111757353B (en) | Network data processing method and device in 5G core network | |
| CN116633775B (en) | Container communication method and system of multi-container network interface | |
| CN106970843B (en) | Remote calling method and device | |
| US20150006622A1 (en) | Web contents transmission method and apparatus | |
| US20110113131A1 (en) | Method of Load Balance Based on BS Architecture | |
| US20110153826A1 (en) | Fault tolerant and scalable load distribution of resources | |
| CN101895550B (en) | Cache accelerating method for compatibility of dynamic and static contents of internet website | |
| CN110336844B (en) | Method for realizing station end system cooperation mechanism based on service architecture | |
| CN104852964A (en) | Multifunctional server scheduling method | |
| CN111600929A (en) | Transmission line detection method, route strategy generation method and proxy server | |
| CN103188323B (en) | The system and method for Web service is provided based on subscriber's main station buffer memory device | |
| CN102546712A (en) | Message transmission method, equipment and system based on distributed service network | |
| CN102404294A (en) | Method and system for achieving content distribution network (CDN) interconnection | |
| CN106357549B (en) | Method, apparatus, system and the load balancer that high concurrent shunts in clustered deploy(ment) | |
| CN114615321A (en) | Traffic processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |