CN107391156A - Method, management node and service node for distributed system transmission services - Google Patents

Method, management node and service node for distributed system transmission services Download PDF

Info

Publication number
CN107391156A
CN107391156A CN201710642637.4A CN201710642637A CN107391156A CN 107391156 A CN107391156 A CN 107391156A CN 201710642637 A CN201710642637 A CN 201710642637A CN 107391156 A CN107391156 A CN 107391156A
Authority
CN
China
Prior art keywords
node
service node
software
message
service
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
Application number
CN201710642637.4A
Other languages
Chinese (zh)
Other versions
CN107391156B (en
Inventor
任永强
谢晓芹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chengdu Huawei Technology Co Ltd
Original Assignee
Chengdu Huawei Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chengdu Huawei Technology Co Ltd filed Critical Chengdu Huawei Technology Co Ltd
Priority to CN201710642637.4A priority Critical patent/CN107391156B/en
Publication of CN107391156A publication Critical patent/CN107391156A/en
Application granted granted Critical
Publication of CN107391156B publication Critical patent/CN107391156B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/465—Distributed object oriented systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Stored Programmes (AREA)

Abstract

This application provides a kind of method, management node and service node for distributed system transmission services.The distributed system, which includes management node and at least one service node, this method, to be included：First service node at least one service node sends first message, and the first message is used to notify the first service node updates software；The second message that the first service node is sent is received, second message is used to indicate that the first service node has been successfully updated the software, and the version identifier of the software is carried in second message；The version identifier of the software is obtained, and is determined according to the version identifier of the software to be successfully updated the number of the service node of the software at least one service node；In the case where the number of the service node for being successfully updated the software meets preset value, it is determined that carrying out service switching, the software upgrading problem in service node is can solve the problem that, business will not interrupt at no point in the update process.

Description

Method, management node and service node for distributed system transmission services
Technical field
The application is related to field of computer technology, and more particularly, to the side for distributed system transmission services Method, management node and service node.
Background technology
Distributed system (Distributed System) is made up of multiple nodes, as one entirely through front network (Front-end Network, FN) externally provides service.Each node of internal system passes through back-end network (Back-end Network, BN) connection.Following functions node is generally included in system：Load balancing node (Load Balance Node, LBN), service node (Service Node, SN), cluster management node (Cluster Management Node, CMN).It is each Functional node is logical node.Service node is responsible for processing business.When the service node in system needs to carry out software upgrading When, it will usually using two ways：Upgraded in offline and online upgrading.
For upgraded in offline, all service nodes are required to restart, and each service node is upgraded, so as to cause Service disconnection.For online upgrading, there can be the problem of new early version coexists in escalation process, due to redaction and early version Compliance is high, and actual is difficult fully to realize compatibility, can not carry out online upgrading.Based on this, it is necessary to propose one kind side Method solves the upgrade problem of service node.
The content of the invention
The application provides a kind of equal for the method for distributed system transmission services, management node, service node and load Weigh node, can solve the problem that the software upgrading problem in service node, business will not interrupt at no point in the update process.
A kind of first aspect, there is provided method for distributed system transmission services, it is characterised in that the distribution System includes management node and at least one service node, and methods described is performed by the management node, and methods described includes：
First service node at least one service node sends first message, and the first message is used to lead to Know the first service node updates software；
The second message that the first service node is sent is received, second message is used to indicate the first service section Point has been successfully updated the software, and the version identifier of the software is carried in second message；
The version identifier of the software is obtained, and determines that at least one service saves according to the version identifier of the software The number of the service node of the software has been successfully updated in point；
In the case where the number of the service node for being successfully updated the software meets preset value, it is determined that entering industry Business switching.
In the embodiment of the present application, the second message that management node is sent by receiving first service node, described second Message is used to indicate that the first service node has been successfully updated software, and the version mark of the software is carried in second message Know, then determined to be successfully updated the clothes of the software at least one service node according to the version identifier of the software The number of business node；And in the case where the number of the service node for being successfully updated the software meets preset value, really Surely service switching is carried out, it is relatively low to the compliance of service node before and after renewal, and business will not interrupt at no point in the update process.
In the embodiment of the present application, renewal software can include：Software upgrading or upgrading rollback.Wherein, software upgrading is Refer to upgrading of the software from lowest version to highest version；Software rollback refers to that software rolls back to lowest version from highest version.
In some possible implementations, according to the version identifier of the software, at least one service section is determined The number of the service node of the software has been successfully updated in point, including：
Each version identifier of the software corresponding to service node at least one service node is detected, To obtain the service node that the software has been successfully updated at least one service node；
The number of the service node of the software has been successfully updated described in statistics.
In some possible implementations, when the determination carries out service switching, methods described also includes：
Enable it is described be successfully updated the service node of the software, and stop at least one service node not into Work(updates the service node of the software.
In the embodiment of the present application, management node is described soft by judging to be successfully updated at least one service node Whether the number of the service node of part meets preset value, to determine whether to carry out service switching.It so can not only ensure to service The online updating of node, it can also be ensured that business is only transmitted on the service node of identical version number so that has been successfully updated institute Business on the service node for stating software and the service node for updating the software not successfully will not interact, i.e., business only concentrates on It has been successfully updated on the service node of the software, or has been focusing only on the service node for updating the software not successfully.
In some possible implementations, the distributed system also includes load balancing node, wherein, it is described to enable It is described to be successfully updated the service node of the software, and stop updating not successfully at least one service node described soft The service node of part, including：
Handover request is sent to the load balancing node, the handover request is used to indicate that the load balancing node opens The service node of the software has been successfully updated with described, and has been stopped at least one service node described in failed renewal The service node of software, in order to the load balancing node to the first service node send the 3rd message, the described 3rd Message enables the first service node for instruction；
Methods described also includes：
The switching response message that the load balancing node is sent is received, the switching response message is used to notify business to cut Change work(into；
According to the switching response message to updating the service of the software at least one service node not successfully Node is updated.
That is, when it is determined that carrying out service switching, management node can directly enable and be successfully updated the software Service node, and stop updating the service node of the software not successfully.Or the management node can indicate that load is equal Node weigh to carry out service switching, this is not construed as limiting.
In some possible implementations, the is sent in the first service node at least one service node Before one message, methods described also includes：
Request message is sent to the load balancing node, the request message is used to notify the load balancing node to stop The only first service node；
The request response that the load node is sent is received, the request response represents the load balancing section Point has successfully stopped the first service node.
Alternatively, before being updated to the software of first service node, management node can also directly stop institute State first service node.
In some possible implementations, meet in the number of the service node for being successfully updated the software pre- If in the case of value, it is determined that service switching is carried out, including：
It is more than in the number of the service node for being successfully updated the software at least one service node not When being successfully updated the number of the service node of the software, it is determined that carrying out service switching.
Alternatively, the preset value can be set as needed.
In some possible implementations, the is sent in the first service node at least one service node After one message, methods described also includes：
The renewal bag of the software is uploaded in the first service node, the renewal bag is used for the first service section Point updates the software using the renewal bag.
Second aspect, there is provided a kind of method for distributed system transmission services, the distributed system include pipe Node and at least one service node are managed, methods described is performed by the first service node at least one service node, Methods described includes：
The first message that the management node is sent is received, the first message is used to notify the first service node more New software；
The software is updated according to the first message, and the is sent to the management node after being successfully updated Two message, second message is used to indicate that the first service node has been successfully updated the software, in second message The version identifier of the software is carried, in order to which the management node is at least one according to determining the version identifier of the software The number of the service node of the software has been successfully updated in individual service node.
In the embodiment of the present application, first service node to management node by sending the second message, second message For indicating that the first service node has been successfully updated software, the version identifier of the software is carried in second message, So that management node determine to be successfully updated at least one service node according to the version identifier of the software it is described soft The number of the service node of part, and meet the situation of preset value in the number of the service node for being successfully updated the software Under, it is determined that service switching is carried out, it is relatively low to the compliance of service node before and after renewal, and business will not at no point in the update process Interrupt.
In the embodiment of the present application, renewal software can include：Software upgrading or upgrading rollback.Wherein, software upgrading is Refer to upgrading of the software from lowest version to highest version；Software rollback refers to that software rolls back to lowest version from highest version.
Alternatively, before the first message that the management node is sent is received, the business on the first service node is It is deactivated.Wherein, the management node can directly disable the business on the first service node, or, it can also indicate that Load balancing node disables the first service node.
In some possible implementations, the clothes of the software have been successfully updated at least one service node In the case that the number of business node meets preset value, the distributed system also includes load balancing node, and methods described is also wrapped Include：
The 3rd message that the load balancing node is sent is received, the 3rd message enables first clothes for instruction Business node；
Business transmission is carried out according to the 3rd message.
In some possible implementations, methods described also includes：
Obtain the renewal bag of the software；
Wherein, it is described that the software is updated according to the first message, including：
According to the first message, the renewal bag renewal software is used.
The third aspect, there is provided a kind of method for distributed system transmission services, the distributed system include pipe Reason node, at least one service node and load balancing node, methods described are performed by the load balancing node, methods described Including：
The handover request that the management node is sent is received, the handover request is used to indicate that the load balancing node opens The service node of software has been successfully updated with least one service node, and has been stopped at least one service node The service node of the software is updated not successfully；
The service section that the software has been successfully updated at least one service node is enabled according to the handover request Point, and stop updating the service node of the software not successfully at least one service node；
Switching response message is sent to the management node, the switching response message is used to notify service switching success, So that the management node is described soft to being updated not successfully at least one service node according to the switching response message The service node of part is updated.
In the embodiment of the present application, load balancing node is at least one according to enabling the handover request that management node is sent The service node of the software has been successfully updated in individual service node, and stop at least one service node it is failed more The service node of the new software, it is ensured that business is only transmitted on the service node of identical version number so that succeeded more The service node of the new software and the business updated not successfully on the service node of the software will not interact, i.e., business only collects In on the service node of the software has been successfully updated, or be focusing only on the service node for updating the software not successfully On.
In some possible implementations, before the handover request that the management node is sent is received, methods described is also Including：
The request message that the management node is sent is received, the request message is used to notify the load balancing node to stop The only first service node at least one service node；
The first service node is stopped according to the request message, and sends request response to the management node and disappears Breath, the request response represent that the load balancing node has successfully stopped the first service node.
That is, being if desired updated to the software of first service node, load balancing node can receive management The request message of node, stop the business on the first service node.
In some possible implementations, after the handover request that the management node is sent is received, methods described Also include：
The 3rd message is sent to the first service node, the 3rd message enables the first service section for instruction Point.
Fourth aspect, there is provided the management node in a kind of distributed system, for performing above-mentioned first aspect or first Method in any possible implementation of aspect.Specifically, the management node include be used for perform above-mentioned first aspect or The module of method in any possible implementation of first aspect.
5th aspect, there is provided the service node in a kind of distributed system, for performing above-mentioned second aspect or second Method in any possible implementation of aspect.Specifically, the service node include be used for perform above-mentioned second aspect or The module of method in any possible implementation of second aspect.
6th aspect, there is provided the load balancing node in a kind of distributed system, for perform the above-mentioned third aspect or Method in any possible implementation of the third aspect.Specifically, the load balancing node includes being used to perform above-mentioned the The module of method in any possible implementation of three aspects or the third aspect.
A kind of 7th aspect, there is provided the management node in distributed system.The management node includes processor, memory And communication interface.Processor is connected with memory and communication interface.Memory is used for store instruction, and processor refers to for performing this Order, communication interface are used to be communicated with other network elements under the control of a processor.The computing device memory storage During instruction, the execution causes the method in any possible implementation of the computing device first aspect or first aspect.
A kind of eighth aspect, there is provided the service node in distributed system.The service node includes processor, memory And communication interface.Processor is connected with memory and communication interface.Memory is used for store instruction, and processor refers to for performing this Order, communication interface are used to be communicated with other network elements under the control of a processor.The computing device memory storage During instruction, the execution causes the method in any possible implementation of the computing device second aspect or second aspect.
A kind of 9th aspect, there is provided the load balancing node in distributed system.The load balancing node includes processing Device, memory and communication interface.Processor is connected with memory and communication interface.Memory is used for store instruction, and processor is used In performing the instruction, communication interface is used to be communicated with other network elements under the control of a processor.The computing device this deposit During the instruction of reservoir storage, the execution causes any possible implementation of the computing device third aspect or the third aspect In method.
Tenth aspect, there is provided a kind of computer-readable recording medium, the computer-readable recording medium storage have program, The program cause management node perform it is above-mentioned in a first aspect, and its any of various implementations be used in distributed system The method of transmission services.
Tenth on the one hand, there is provided a kind of computer-readable recording medium, the computer-readable recording medium storage have journey Sequence, the program cause service node to perform above-mentioned second aspect, and its any of various implementations are used for distributed system The method of transmission services in system.
12nd aspect, there is provided a kind of computer-readable recording medium, the computer-readable recording medium storage have journey Sequence, the program cause load balancing node to perform the above-mentioned third aspect, and its any of various implementations are used to be distributed The method of transmission services in formula system.
13rd aspect, this application provides a kind of computer program product for including instruction, when the computer program produces When product are run on computers so that computer performs any possible implementation of above-mentioned first aspect or first aspect Described method.
Fourteenth aspect, this application provides a kind of computer program product for including instruction, when the computer program produces When product are run on computers so that computer performs any possible implementation of above-mentioned second aspect or second aspect Described method.
15th aspect, this application provides a kind of computer program product for including instruction, when the computer program produces When product are run on computers so that computer performs any possible implementation of the above-mentioned third aspect or the third aspect Described method.
Brief description of the drawings
Fig. 1 is the schematic diagram using a distributed system of the embodiment of the present application.
Fig. 2 is the schematic interaction figure according to the method for distributed system transmission services of the embodiment of the present application.
Fig. 3 is the schematic interaction according to the method for distributed system transmission services of another embodiment of the application Figure.
Fig. 4 is the schematic diagram according to an example of the embodiment of the present application.
Fig. 5 is the schematic diagram according to another example of the embodiment of the present application.
Fig. 6 is the schematic interaction figure according to the further example of the embodiment of the present application.
Fig. 7 is the schematic interaction figure according to another example of the embodiment of the present application.
Fig. 8 is the schematic block diagram of the management node in the distributed system according to the embodiment of the present application.
Fig. 9 is the schematic block diagram of the service node in the distributed system according to the embodiment of the present application.
Figure 10 is the schematic block diagram of the load balancing node in the distributed system according to the embodiment of the present application.
Figure 11 is the structured flowchart of management node in the distributed system according to the embodiment of the present application.
Figure 12 is the structured flowchart according to the Services in Distributed System node of the embodiment of the present application.
Figure 13 is the structured flowchart of load balancing node in the distributed system according to the embodiment of the present application.
Embodiment
Below in conjunction with accompanying drawing, the technical scheme in the application is described.
The technical scheme of the embodiment of the present application can apply to distributed system (Distributed System) or cluster In system.Fig. 1 shows the schematic diagram of a distributed system using the embodiment of the present application.As shown in figure 1, distributed system Including following functions node：Load balancing node (Load Balance Node, LBN) 10, service node (Service Node, SN) 11 and cluster management node (Cluster Management Node, CMN) 12.Wherein, load balancing node 10 is responsible will The traffic assignments of client 13 are to the purpose on each service node 11, reaching load balancing.Each service node 11 is responsible for place Reason business.Cluster management node 12 is responsible for the functions such as the registration, management, upgrading of each node.
Alternatively, distributed system can not have load balancing node 10 in specific implementation, but be carried out by algorithm Load balancing, such as distributed hashtable (Distributed Hash Table, DHT) algorithm.
It can be located at it should be understood that above-mentioned each node is logical node, during actual deployment on same physical machine, also may be used With separated deployment, this is not construed as limiting.
It should also be understood that it is to be schematically illustrated by taking 4 service nodes 11 as an example in Fig. 1, not to service node 11 Number is construed as limiting.
It should also be understood that Fig. 1 simply exemplarily gives the schematic diagram of a scenario that can apply the embodiment of the present application, and The embodiment of the present application is not formed and limited.
Fig. 2 shows the signal sexual intercourse of the method 200 for distributed system transmission services according to the embodiment of the present application Mutually figure.The distributed system includes management node and at least one service node.For example, the management node can be Fig. 1 In cluster management node 12, at least one service node can be the service node 11 in Fig. 1.It is as shown in Fig. 2 described Method 200 includes：
S201, first service node of the management node at least one service node sends first message, described First message is used to notify the first service node updates software；
In the embodiment of the present application, renewal software can include：Software upgrading or upgrading rollback.Wherein, software upgrading is Refer to upgrading of the software from lowest version (Version) to highest version；Software rollback refers to that software rolls back to lowest version from highest version.
It should be understood that " the renewal software " of the embodiment of the present application is not limited to the software upgrading to service node or pin Renewal to some software module, this is not construed as limiting.
Alternatively, management node can be uploaded in the first service node renewal bag (such as AKU), it is described more New wrap updates the software for the first service node using the renewal bag, wherein, the renewal bag can be understood as Service node enters software kit required during line program renewal.
Accordingly, first service node performs more newer command after the first message is received, and is wrapped using the renewal It is updated.
Alternatively, the first message can be instruction or program, and those skilled in the art can be realized using programming language.Example Such as, the first message is upgrade command.
Alternatively, the first service node can represent the service section to be updated at least one service node Point.The first service node can represent one or more service nodes.That is, the management node can be to described Multiple service nodes for updating the software not successfully send more new command at least one service node, and upload renewal Bag.
Alternatively, before S201, methods described 200 also includes：
The management node is sent to the first service node stops message, and the stopping message being used to stop described the One service node.
Or alternatively, the distributed system also includes load balancing node (for example, the load balancing node can To be the load balancing node 10 in Fig. 1), before S201, methods described 200 also includes：
Management node sends request message to the load balancing node, and the request message is used to notify that the load is equal The node that weighs stops the first service node and carries out business transmission；
The load balancing node sends request response to the management node, and the request response represents institute The business that load balancing node has successfully stopped on the first service node is stated to transmit.
That is, when first service node carries out software upgrading, it is necessary to stop the industry on the first service node Business.Wherein, management node can directly stop first service node, or, management node instruction load balancing node stops the One service node.
S202, the first service node are updated according to the first message to the software；
Here, first service node can obtain the renewal bag pair after the first message of management node transmission is received The software is updated.
S203, the first service node after being successfully updated to the management node send the second message, described second Message is used to indicate that the first service node has been successfully updated the software, and the version of the software is carried in second message This mark, in order to the management node according to the version identifier of the software determine at least one service node into Work(updates the number of the service node of the software；
Alternatively, the version identifier of the software can be understood as software version number or other revision identification informations.Wherein, Software version number illustrates the software version of the software on service node.
Alternatively, software version number can with the issue or upgrading of software version monotonic increase.For example, service node On a certain software version number be 1.0, referred to as V1.0, with the development of software version, the version after the software version update This numbering is V2.0.
Here, first service node can send the second message after completing to update to management node, with to management node Software upgrading success is informed, and the version identifier of software is carried in the second message, such as, carry the start context after renewal V2.0.So, management node can obtain or know the software version number in all service nodes, so as to learn described at least one The number of the service node of the software has been successfully updated in individual service node.
Alternatively, second message can be registration request or heartbeat request, you can be asked in registration request or heartbeat Ask and carry the software version number after updating.
Accordingly, management node can update cache information after second message is received, in order to count it is described extremely Software version number corresponding to each service node in a few service node.
S204, the management node obtains the version identifier of the software, and is determined according to the version identifier of the software The number of the service node of the software has been successfully updated at least one service node；
Alternatively, S204 includes：
Version of the management node to each software corresponding to service node at least one service node Mark is detected, to obtain the service node that the software has been successfully updated at least one service node；
The number of the service node of the software has been successfully updated described in the management node statistics.
Specifically, management node can check or identify that each service node is corresponding at least one service node The software version identifier, and to being successfully updated the service node of the software at least one service node Number is counted.
S205, it is described in the case where the number of the service node for being successfully updated the software meets preset value Management node determines to carry out service switching.
Alternatively, the preset value can be that management node determines according to the actual requirements.
Alternatively, S205 includes：
It is more than in the number of the service node for being successfully updated the software at least one service node not When being successfully updated the number of the service node of the software, it is determined that carrying out service switching.
For example, when the number of the service node for being successfully updated the software reaches at least one service node Total number half, management node can determine carry out service switching.
Wherein, service switching refers to：Stop updating the industry on the service node of the software not successfully in distributed system Business, enables the business being successfully updated in the distributed system on the service node of the software.In other words, it is by distribution The service node that business in system never updates institute's software is switched to and has been successfully updated on the service node of the software.Wherein, The time of service switching is ofer short duration, can be ignored, and business can't be transmitted and cause big influence.
It should be understood that in the embodiment of the present application, numbering " first " is introduced, " second " ... is intended merely to distinguish different pairs As, for example different message is distinguished, or different " service node " is distinguished, the protection domain of the embodiment of the present application is not formed Limit.
It should also be understood that in the various embodiments of the application, the size of the sequence number of above-mentioned each process is not meant to perform The priority of order, the execution sequence of each process should be determined with its function and internal logic, without the reality of reply the embodiment of the present application Apply process and form any restriction.
In the embodiment of the present application, the second message that management node is sent by receiving first service node, described second Message is used to indicate that the first service node has been successfully updated software, and the version mark of the software is carried in second message Know, then determined to be successfully updated the clothes of the software at least one service node according to the version identifier of the software The number of business node；And in the case where the number of the service node for being successfully updated the software meets preset value, really Surely service switching is carried out, it is relatively low to the compliance of service node before and after renewal, and business will not interrupt at no point in the update process.
In the embodiment of the present application, management node is described soft by judging to be successfully updated at least one service node Whether the number of the service node of part meets preset value, to determine whether to carry out service switching.It so can not only ensure to service The online updating of node, it can also be ensured that business is only transmitted on the service node of identical version number so that has been successfully updated institute Business on the service node for stating software and the service node for updating the software not successfully will not interact, i.e., business only concentrates on It has been successfully updated on the service node of the software, or has been focusing only on the service node for updating the software not successfully.
Alternatively, in the case where the number of the service node for being successfully updated the software is unsatisfactory for preset value, The management node continues to select other service nodes to be updated at least one service node to be updated, with weight Multiple above-mentioned renewal step.
Alternatively, when it is determined that carrying out service switching, methods described 200 also includes：
Management node has been successfully updated the service node of the software described in enabling, and stops at least one service section The service node of the software is updated in point not successfully.
That is, when it is determined that carrying out service switching, management node can directly enable and be successfully updated the software Service node, and stop updating the service node of the software not successfully.Or the management node can indicate that load is equal Node weigh to carry out service switching, this is not construed as limiting.
Alternatively, as shown in figure 3, methods described 200 can also include：
S206, management node send handover request to the load balancing node, and the handover request is described for indicating Load balancing node has been successfully updated the service node of the software described in enabling, and stops at least one service node The service node of the software is updated not successfully, in order to which the load balancing node sends the 3rd to the first service node Message, the 3rd message enable the first service node for instruction；
Alternatively, the load balancing node according to the handover request enable at least one service node into Work(updates the service node of the software, and stops updating the service of the software not successfully at least one service node Node；
S207, after the handover request that the management node is sent is received, the load balancing node is to described first Service node sends the 3rd message, and the 3rd message enables the first service node for instruction.
Accordingly, the first service node enables business transmission according to the 3rd message.
Alternatively, the load balancing node can also be included in the 3rd message to the first service node to distribute Business, in order to the first service node open business transmission.
It should be noted that first service node has been stopped for business transmission when carrying out software upgrading.But in the first clothes After software success described in node updates of being engaged in, management node can't enable the first service node, or instruction load immediately Balanced node gives the first service node distribution service, but in the service node that the software has been successfully updated described in judgement Number meet preset value in the case of, can just enable the first service node, or instruction load balancing node is to described First service node distribution service.It can so ensure that business is only distributed or passed in the service node of same software version identifier It is defeated so that the business on the service node for being successfully updated the software and the service node for updating the software not successfully will not Interaction.
S208, the load balancing node send switching response message, the switching response message to the management node For notifying service switching success.
Alternatively, the management node according to the switching response message to failed at least one service node The service node for updating the software is updated.
Alternatively, management node can be to the service of the software to be updated of other at least one service node Node updates (i.e. parallel renewal) together, or updates one by one.Alternatively, management node often updates a service node, Ke Yikai Open the business of the service node.
Specifically, management node can learn that business has switched successfully when receiving switching response message, i.e., business has been Never the service node for being successfully updated the software is switched to and has been successfully updated on the service node of the software.Now, manage Node can be updated to the service node for updating the software at least one service node not successfully.
Therefore, management node determines to have succeeded more at least one service node by the version identifier of the software The number of the service node of the new software, meets preset value in the number of the service node for being successfully updated the software In the case of, it is determined that service switching is carried out, it is relatively low to the compliance of service node before and after renewal, and industry at no point in the update process Business will not be interrupted.
For the ease of skilled artisan understands that the technical scheme of the embodiment of the present application, is retouched below in conjunction with Fig. 4 State.Fig. 4 shows the schematic diagram of an example according to the embodiment of the present application.As shown in figure 4, distributed system includes 4 clothes Business node (including service node 1, service node 2, service node 3 and service node 4).On Fig. 4 left side, in load balancing section Point stopped to after service node 2 and the distribution service of service node 4, software and services node 4 of the management node to service node 2 The software updated respectively, and the version number for obtaining the software on service node 2 and service node 4 is The version number of the software is v1 on v2, and service node 1 and service node 3；On Fig. 4 the right, management node is obtaining Know be successfully updated to software version number be v2 service node number meet reach sum half when, load balancing section can be indicated Put by distribution of services into service node 2 and service node 4, and stop to service node 1 and the distribution service of service node 3.Can Selection of land, according to the update status of each service node, renewal is buffered in described soft on local each service node management node The version number of part, in order to subsequently use.Alternatively, management node, can be to the kimonos of service node 1 after the completion of service switching The software on business node 3 is updated.Fig. 5 is the schematic diagram according to another example of the embodiment of the present application.For example, such as Shown in Fig. 5, management node can upgrade to the software on service node 1, by the software version on service node 1 by V1 is upgraded to v2, and recovers the transmission of the business on service node 1.Certainly, management node can continue to rise service node 3 Level (not shown in Fig. 5).
It should be understood that merely just illustrated by taking the example in Fig. 4 and Fig. 5 as an example, not to the guarantor of the embodiment of the present application Protect scope and form restriction.
Software upgrading is illustrated below in conjunction with the example in Fig. 6 and Fig. 7.It should be understood that software rollback is equally applicable In the technical scheme of the embodiment of the present application.Fig. 6 shows the schematic interaction figure of the further example according to the embodiment of the present application. As shown in fig. 6, the example may comprise steps of：
Step 1, management node (or cluster management node) is sent to load balancing node stops request, and stopping request being used Stop the business of service node 1 in notification payload equilibrium node；Wherein, the software version of service node 1 is V1.
Step 2, after load balancing node stops the business of service node 1, replied to management node and stop response, the stopping rings It should represent successfully to stop the business on service node 1；
Step 3, management node sends upgrade request to service node 1, to notify it to start to upgrade, and uploads AKU；
Step 4, service node 1 receives AKU, and is replied to management node and be properly received AKU；
Step 5, management node is sent to service node 1 starts upgrade request, to notify service node 1 to start to upgrade；
Step 6, service node 1 performs upgrade command, is upgraded using AKU；
Step 7, service node 1 is replied to management node after upgrading successfully and upgrades successfully response, while register new version This number V2；
Step 8, after management node receives registration request, more new node version number (or cache information), i.e., by service node 1 Software version number V2 is updated to by V1；
Step 9, management node checks the version number of all service nodes, (can also claim in the service node for the upgrading that succeeds Make new node) half for being not up to total service node number is counted, other service nodes to be upgraded can be selected, circulate above-mentioned steps 1-8。
Therefore, management node can judge to meet the service section upgraded that succeeds according to the software version number of service node Whether point meets condition, continues the service node for selecting other to be upgraded in the case of ungratified.
Alternatively, Fig. 7 be according to the schematic interaction figure of another example of the embodiment of the present application, as shown in fig. 7, for Step 9, if management node checks new node number more than old node (service node not upgraded) number, business can be started and cut Change, and service switching request is sent to load balancing node；
Step 10, load balancing node performs service switching, that is, stops old node traffic, starts new node business；
Step 11, the successful response message of load balancing node reverts back service switching；
Step 12, after management node receives the successful response message of service switching, the remaining clothes not upgraded can be selected Business node is upgraded, such as, service node 2, wherein, the software version of service node 2 is V1.
Therefore, management node is it is determined that the number of the service node for successfully installing the AKU meets preset value In the case of, it is determined that service switching is carried out, it is relatively low to the compliance of service node before and after upgrading, and the industry in escalation process Business will not be interrupted.
It should be understood that the example being introduced into above-mentioned Fig. 6 or Fig. 7 is simply facilitated it will be understood by those skilled in the art that present application example Technical scheme, the protection domain of the embodiment of the present application is not formed and limited.
It should also be understood that in the various embodiments of the application, the size of the sequence number of above-mentioned each process is not meant to perform The priority of order, the execution sequence of each process should be determined with its function and internal logic, without the reality of reply the embodiment of the present application Apply process and form any restriction.
The method for distributed system transmission services according to the embodiment of the present application has been described in detail above.Below will Management node, service node and load balancing node in distributed system according to the embodiment of the present application is described.
Fig. 8 shows the schematic block diagram of the management node 800 in the distributed system according to the embodiment of the present application.Its In, the distributed system includes at least one service node.As shown in figure 8, the management node 800 includes：
Sending module 810, first message, institute are sent for the first service node at least one service node First message is stated to be used to notify the first service node updates software；
Receiving module 820, the second message sent for receiving the first service node, second message are used to refer to Show that the first service node has been successfully updated the software, the version identifier of the software is carried in second message；
Determining module 830, institute is determined for obtaining the version identifier of the software, and according to the version identifier of the software State the number for the service node that the software has been successfully updated at least one service node；
The determining module 830 is additionally operable to, and is met in the number of the service node for being successfully updated the software pre- If in the case of value, it is determined that carrying out service switching.
Alternatively, the determining module 830 is specifically used for：
Each version identifier of the software corresponding to service node at least one service node is detected, To obtain the service node that the software has been successfully updated at least one service node；
The number of the service node of the software has been successfully updated described in statistics.
Alternatively, the management node also includes：
Processing module, for when the determination carries out service switching, enabling the clothes for being successfully updated the software Business node, and stop updating the service node of the software not successfully at least one service node.
Alternatively, the distributed system also includes load balancing node, wherein, the sending module 810 is additionally operable to：
Handover request is sent to the load balancing node, the handover request is used to indicate that the load balancing node opens The service node of the software has been successfully updated with described, and has been stopped at least one service node described in failed renewal The service node of software, in order to the load balancing node to the first service node send the 3rd message, the described 3rd Message enables the first service node for instruction；
Wherein, the receiving module 820 is additionally operable to：
The switching response message that the load balancing node is sent is received, the switching response message is used to notify business to cut Change work(into；
The management node 800 also includes：
Update module, for updating institute to failed at least one service node according to the switching response message The service node for stating software is updated.
Alternatively, the sending module 810 is additionally operable to：
Request message is sent to the load balancing node, the request message is used to notify the load balancing node to stop Only the first service node carries out business transmission；
Wherein, the receiving module 820 is additionally operable to：
The request response that the load node is sent is received, the request response represents the load balancing section Point has successfully stopped the first service node.
Alternatively, the determining module 830 is specifically used for：
It is more than in the number of the service node for being successfully updated the software at least one service node not When being successfully updated the number of the service node of the software, it is determined that carrying out service switching.
Alternatively, the management node 800 also includes：
Uploading module, for uploading the renewal bag of the software in the first service node, the renewal bag is used for The first service node updates the software using the renewal bag.
The executable use according to the embodiment of the present application of management node 800 in the distributed system of the embodiment of the present application The method of management node side in the method for distributed system transmission services, and the management node in the distributed system Above and other operation and/or function of modules in 800 respectively in order to realize the corresponding flow of foregoing each method, because This can also be in implementation method beneficial effect, for sake of simplicity, being not added with repeating herein.
Fig. 9 shows the schematic block diagram of the service node 900 in the distributed system according to the embodiment of the present application.Its In, the distributed system includes management node.As shown in figure 9, the service node 900 includes：
Receiving module 910, the first message sent for receiving the management node, the first message are used to notify institute State service node renewal software；
Update module 920, the software is updated according to the first message；
Sending module 930, for sending the second message to the management node after the software is successfully updated, described the Two message are used to indicate that the service node has been successfully updated the software, and the version of the software is carried in second message Mark, in order to which the management node determines to be successfully updated at least one service node according to the version identifier of the software The number of the service node of the software.
Alternatively, the distributed system also includes load balancing node, and the receiving module 910 is additionally operable to：
The 3rd message that the load balancing node is sent is received, the 3rd message enables the service section for instruction Point；
Wherein, the service node 900 also includes：
Transport module, business transmission is carried out according to the 3rd message.
Alternatively, the service node 900 also includes：
Acquisition module, for obtaining the renewal bag of the software；
Wherein, the update module 920 is specifically used for：
According to the first message, the software is updated using the renewal bag.
The executable use according to the embodiment of the present application of service node 900 in the distributed system of the embodiment of the present application The method of management node side in the method for distributed system transmission services, and the service node in the distributed system Above and other operation and/or function of modules in 900 respectively in order to realize the corresponding flow of foregoing each method, because This can also be in implementation method beneficial effect, for sake of simplicity, being not added with repeating herein.
Figure 10 shows the schematic frame of the load balancing node 1000 in the distributed system according to the embodiment of the present application Figure.Wherein, the distributed system includes management node and at least one service node.As shown in Figure 10, the load balancing Node 1000 includes：
Receiving module 1010, the handover request sent for receiving the management node, the handover request are used to indicate The load balancing node enables the service node that software has been successfully updated at least one service node, and described in stopping The service node of the software is updated at least one service node not successfully；
Processing module 1020, it has been successfully updated for being enabled according to the handover request at least one service node The service node of the software, and stop updating the service node of the software not successfully at least one service node；
Sending module 1030, for sending switching response message to the management node, the switching response message is used for Notify service switching success so that the management node according to the switching response message at least one service node The service node for updating the software not successfully is updated.
Alternatively, the receiving module 1010 is additionally operable to：
The request message that the management node is sent is received, the request message is used to notify the load balancing node to stop The only first service node at least one service node；
The processing module 1020 is additionally operable to, and stops the first service node according to the request message；
The sending module 1030 is additionally operable to, and sends request response to the management node, the request response disappears Breath represents that the load balancing node has successfully stopped the first service node.
Alternatively, the sending module 1030 is additionally operable to：
The 3rd message is sent to the first service node, the 3rd message enables the first service section for instruction Point.
Load balancing node 1000 in the distributed system of the embodiment of the present application can perform to be implemented according to the application The method of management node side in the method for distributed system transmission services of example, and the load in the distributed system Above and other operation and/or function of modules in balanced node 1000 is respectively in order to realize the phase of foregoing each method Answer flow, thus can also be in implementation method beneficial effect, for sake of simplicity, being not added with repeating herein.
Figure 11 shows the structure of management node in the distributed system that the application one embodiment provides, including at least one Individual processor 1102 (such as CPU), at least one network interface 1103 or other communication interfaces, memory 1104.Alternatively, Can be with receiver 1105 and transmitter 1106.Processor 1102 is used to perform the executable module stored in memory 1104, Such as computer program.Memory 1104 may include high-speed random access memory RAM, it is also possible to also including non-labile Memory (non-volatile memory), for example, at least a magnetic disk storage.Pass through at least one network interface 1103 (can be wired or wireless) realizes the communication connection between at least one other network element.Receiver 1105 and transmitter 1106 are used to transmit various signals, message or information.
In some embodiments, memory 1104 stores program 11041, and program 11041 can be by processor 1102 Perform, the side of management node side in the method for distributed system transmission services for performing foregoing the embodiment of the present application Method.
Figure 12 shows the structure for the Services in Distributed System node that the application one embodiment provides, including at least one Individual processor 1202 (such as CPU), at least one network interface 1203 or other communication interfaces, memory 1204.Alternatively, Can be with receiver 1205 and transmitter 1206.Processor 1202 is used to perform the executable module stored in memory 1204, Such as computer program.Memory 1204 may include high-speed random access memory RAM, it is also possible to also including non-labile Memory (non-volatile memory), for example, at least a magnetic disk storage.Pass through at least one network interface 1203 (can be wired or wireless) realizes the communication connection between at least one other network element.Receiver 1205 and transmitter 1206 are used to transmit various signals, message or information.
In some embodiments, memory 1204 stores program 12041, and program 12041 can be by processor 1202 Perform, the side of service node side in the method for distributed system transmission services for performing foregoing the embodiment of the present application Method.
Figure 13 shows the structure of the load balancing node in the distributed system that the application one embodiment provides, including At least one processor 1302 (such as CPU), at least one network interface 1303 or other communication interfaces, memory 1304. Alternatively, can be with receiver 1305 and transmitter 1306.Processor 1302 is used to perform holding of storing in memory 1304 Row module, such as computer program.Memory 1304 may include high-speed random access memory RAM, it is also possible to also including non- Unstable memory (non-volatile memory), for example, at least a magnetic disk storage.Connect by least one network 1303 (can be wired or wireless) of mouth realize the communication connection between at least one other network element.Receiver 1305 and hair Device 1306 is sent to be used to transmit various signals, message or information.
In some embodiments, memory 1304 stores program 13041, and program 13041 can be by processor 1302 Perform, load balancing node side in the method for distributed system transmission services for performing foregoing the embodiment of the present application Method.
Those of ordinary skill in the art are it is to be appreciated that the list of each example described with reference to the embodiments described herein Member and algorithm steps, it can be realized with the combination of electronic hardware or computer software and electronic hardware.These functions are actually Performed with hardware or software mode, application-specific and design constraint depending on technical scheme.Professional and technical personnel Described function can be realized using distinct methods to each specific application, but this realization is it is not considered that exceed The scope of the embodiment of the present application.
It is apparent to those skilled in the art that for convenience and simplicity of description, the system of foregoing description, The specific work process of device and unit, the corresponding process in preceding method embodiment is may be referred to, will not be repeated here.
In several embodiments that the embodiment of the present application is provided, it should be understood that disclosed system, device and side Method, it can realize by another way.For example, device embodiment described above is only schematical, for example, described The division of unit, only a kind of division of logic function, can there are other dividing mode, such as multiple units when actually realizing Or component can combine or be desirably integrated into another system, or some features can be ignored, or not perform.It is another, institute Display or the mutual coupling discussed or direct-coupling or communication connection can be by some interfaces, device or unit INDIRECT COUPLING or communication connection, can be electrical, mechanical or other forms.
The unit illustrated as separating component can be or may not be physically separate, show as unit The part shown can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple On NE.Some or all of unit therein can be selected to realize the mesh of this embodiment scheme according to the actual needs 's.
In addition, each functional unit in each embodiment of inventive embodiments can be integrated in a processing unit, Can be that unit is individually physically present, can also two or more units it is integrated in a unit.
If the function is realized in the form of SFU software functional unit and is used as independent production marketing or in use, can be with It is stored in a computer read/write memory medium.Based on such understanding, the technical scheme of the embodiment of the present application is substantially The part to be contributed in other words to prior art or the part of the technical scheme can be embodied in the form of software product Come, the computer software product is stored in a storage medium, including some instructions are make it that a computer equipment (can To be personal computer, server, or network equipment etc.) perform the whole of each embodiment methods described of the embodiment of the present application Or part steps.And foregoing storage medium includes：USB flash disk, mobile hard disk, read-only storage (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disc or CD etc. are various can be with storage program The medium of code.
It is described above, the only embodiment of the embodiment of the present application, but the protection domain of the embodiment of the present application is not This is confined to, any one skilled in the art can think easily in the technical scope that the embodiment of the present application discloses To change or replacement, should all cover within the protection domain of the embodiment of the present application.Therefore, the protection domain of the embodiment of the present application It should be based on the protection scope of the described claims.

Claims (26)

  1. A kind of 1. method for distributed system transmission services, it is characterised in that the distributed system includes management node With at least one service node, methods described is performed by the management node, and methods described includes：
    First service node at least one service node sends first message, and the first message is used to notify institute State first service node updates software；
    The second message that the first service node is sent is received, second message is used to indicate the first service node The software is successfully updated, the version identifier of the software is carried in second message；
    The version identifier of the software is obtained, and is determined according to the version identifier of the software at least one service node It has been successfully updated the number of the service node of the software；
    In the case where the number of the service node for being successfully updated the software meets preset value, it is determined that the business of progress is cut Change.
  2. 2. according to the method for claim 1, it is characterised in that the version identifier according to the software, it is determined that described The number of the service node of the software has been successfully updated at least one service node, including：
    Each version identifier of the software corresponding to service node at least one service node is detected, to obtain Take the service node that the software has been successfully updated at least one service node；
    The number of the service node of the software has been successfully updated described in statistics.
  3. 3. method according to claim 1 or 2, it is characterised in that when the determination carries out service switching, methods described Also include：
    Enable it is described be successfully updated the service node of the software, and stop at least one service node it is failed more The service node of the new software.
  4. 4. according to the method for claim 3, it is characterised in that the distributed system also includes load balancing node, its In, it is described enable it is described be successfully updated the service node of the software, and stop at least one service node not into Work(updates the service node of the software, including：
    Handover request is sent to the load balancing node, the handover request is used to indicate that the load balancing node enables institute The service node for being successfully updated the software is stated, and stops updating the software not successfully at least one service node Service node, in order to the load balancing node to the first service node send the 3rd message, the 3rd message For indicating to enable the first service node；
    Methods described also includes：
    Receive the switching response message that the load balancing node is sent, the switching response message be used to notifying service switching into Work(；
    According to the switching response message to updating the service node of the software at least one service node not successfully It is updated.
  5. 5. according to the method for claim 4, it is characterised in that wherein, described at least one service node First service node send first message before, methods described also includes：
    Request message is sent to the load balancing node, the request message is used to notify the load balancing node to stop institute State first service node；
    The request response that the load node is sent is received, the request response has represented the load balancing node Success stops the first service node.
  6. 6. method according to any one of claim 1 to 5, it is characterised in that be successfully updated the software described Service node number meet preset value in the case of, it is determined that carry out service switching, including：
    It is more than in the number of the service node for being successfully updated the software failed at least one service node When updating the number of the service node of the software, it is determined that carrying out service switching.
  7. 7. method according to any one of claim 1 to 6, it is characterised in that at least one service node In first service node send first message after, methods described also includes：
    The renewal bag of the software is uploaded in the first service node, the renewal bag, which is used for the first service node, to be made The software is updated with the renewal bag.
  8. A kind of 8. method for distributed system transmission services, it is characterised in that the distributed system includes management node With at least one service node, methods described is performed by the first service node at least one service node, the side Method includes：
    The first message that the management node is sent is received, the first message is used to notify that the first service node updates are soft Part；
    The software is updated according to the first message, and sends second to the management node after being successfully updated and disappears Breath, second message are used to indicate that the first service node has been successfully updated the software, carried in second message The version identifier of the software, in order to which the management node determines at least one clothes according to the version identifier of the software The number of the service node of the software has been successfully updated in business node.
  9. 9. according to the method for claim 8, it is characterised in that the distributed system also includes load balancing node, institute Stating method also includes：
    The 3rd message that the load balancing node is sent is received, the 3rd message enables the first service section for instruction Point；
    Business transmission is carried out according to the 3rd message.
  10. 10. method according to claim 8 or claim 9, it is characterised in that methods described also includes：
    Obtain the renewal bag of the software；
    Wherein, it is described that the software is updated according to the first message, including：
    According to the first message, the software is updated using the renewal bag.
  11. A kind of 11. method for distributed system transmission services, it is characterised in that the distributed system includes management and saved Point, at least one service node and load balancing node, methods described are performed by the load balancing node, methods described bag Include：
    The handover request that the management node is sent is received, the handover request is used to indicate that the load balancing node enables institute State the service node that software has been successfully updated at least one service node, and stop at least one service node not into Work(updates the service node of the software；
    The service node that the software has been successfully updated at least one service node is enabled according to the handover request, and Stop updating the service node of the software not successfully at least one service node；
    Switching response message is sent to the management node, the switching response message is used to notify service switching success, so that The management node is according to the switching response message to updating the software not successfully at least one service node Service node is updated.
  12. 12. according to the method for claim 11, it is characterised in that please in the switching for receiving the management node transmission Before asking, methods described also includes：
    The request message that the management node is sent is received, the request message is used to notify the load balancing node to stop institute State the first service node at least one service node；
    The first service node is stopped according to the request message, and request response, institute are sent to the management node State request response and represent that the load balancing node has successfully stopped the first service node.
  13. 13. the method according to claim 11 or 12, it is characterised in that receiving the switching of the management node transmission After request, methods described also includes：
    The 3rd message is sent to the first service node, the 3rd message enables the first service node for instruction.
  14. 14. the management node in a kind of distributed system, it is characterised in that the distributed system includes at least one service and saved Point, the management node include：
    Sending module, at least one service node first service node send first message, described first Message is used to notify the first service node updates software；
    Receiving module, the second message sent for receiving the first service node, second message are described for indicating First service node has been successfully updated the software, and the version identifier of the software is carried in second message；
    Determining module, for obtaining the version identifier of the software, and according to determining the version identifier of the software at least The number of the service node of the software has been successfully updated in one service node；
    The determining module is additionally operable to, and meets the feelings of preset value in the number of the service node for being successfully updated the software Under condition, it is determined that carrying out service switching.
  15. 15. management node according to claim 14, it is characterised in that the determining module is specifically used for：
    Each version identifier of the software corresponding to service node at least one service node is detected, to obtain Take the service node that the software has been successfully updated at least one service node；
    The number of the service node of the software has been successfully updated described in statistics.
  16. 16. the management node according to claims 14 or 15, it is characterised in that the management node also includes：
    Processing module, for when the determination carries out service switching, enabling the service section for being successfully updated the software Point, and stop updating the service node of the software not successfully at least one service node.
  17. 17. management node according to claim 16, it is characterised in that the distributed system also includes load balancing section Point, wherein, the sending module is additionally operable to：
    Handover request is sent to the load balancing node, the handover request is used to indicate that the load balancing node enables institute The service node for being successfully updated the software is stated, and stops updating the software not successfully at least one service node Service node, in order to the load balancing node to the first service node send the 3rd message, the 3rd message For indicating to enable the first service node；
    Wherein, the receiving module is additionally operable to：
    Receive the switching response message that the load balancing node is sent, the switching response message be used to notifying service switching into Work(；
    The management node also includes：
    Update module, for described soft to being updated not successfully at least one service node according to the switching response message The service node of part is updated.
  18. 18. management node according to claim 17, it is characterised in that wherein, the sending module is additionally operable to：
    Request message is sent to the load balancing node, the request message is used to notify the load balancing node to stop institute State first service node；
    Wherein, the receiving module is additionally operable to：
    The request response that the load node is sent is received, the request response has represented the load balancing node Success stops the first service node.
  19. 19. the management node according to any one of claim 14 to 18, it is characterised in that the determining module is specifically used In：
    It is more than in the number of the service node for being successfully updated the software failed at least one service node When updating the number of the service node of the software, it is determined that carrying out service switching.
  20. 20. the management node according to any one of claim 14 to 19, it is characterised in that the management node is also wrapped Include：
    Uploading module, for uploading the renewal bag of the software in the first service node, the renewal bag is used for described First service node updates the software using the renewal bag.
  21. 21. the service node in a kind of distributed system, it is characterised in that the distributed system includes management node, described Service node includes：
    Receiving module, the first message sent for receiving the management node, the first message are used to notify the service Node updates software；
    Update module, the software is updated according to the first message；
    Sending module, for sending the second message, second message to the management node after the software is successfully updated For indicating that the service node has been successfully updated the software, the version identifier of the software is carried in second message, In order to which the management node is according to the version identifier of the software determines to be successfully updated at least one service node The number of the service node of software.
  22. 22. service node according to claim 21, it is characterised in that the distributed system also includes load balancing section Point, the receiving module are additionally operable to：
    The 3rd message that the load balancing node is sent is received, the 3rd message enables the service node for instruction；
    Business transmission is carried out according to the 3rd message.
  23. 23. the service node according to claim 21 or 22, it is characterised in that the service node also includes：
    Acquisition module, for obtaining the renewal bag of the software；
    Wherein, the update module is specifically used for：
    According to the first message, the software is updated using the renewal bag.
  24. A kind of 24. load balancing node in distributed system, it is characterised in that the distributed system include management node and At least one service node, the load balancing node include：
    Receiving module, the handover request sent for receiving the management node, the handover request are used to indicate the load Balanced node enables at least one service node and has been successfully updated the service node of software, and stops described at least one The service node of the software is updated in service node not successfully；
    Processing module, the software is successfully updated for being enabled according to the handover request at least one service node Service node, and stop updating the service node of the software not successfully at least one service node；
    Sending module, for sending switching response message to the management node, the switching response message is used to notify business Switch successfully so that the management node according to the switching response message at least one service node it is failed more The service node of the new software is updated.
  25. 25. load balancing node according to claim 24, it is characterised in that the receiving module is additionally operable to：
    The request message that the management node is sent is received, the request message is used to notify the load balancing node to stop institute State the first service node at least one service node；
    The processing module is additionally operable to, and stops the first service node according to the request message；
    The sending module is additionally operable to, and sends request response to the management node, the request response represents institute State load balancing node and successfully stop the first service node.
  26. 26. the load balancing node according to claim 24 or 25, it is characterised in that the sending module is additionally operable to：
    The 3rd message is sent to the first service node, the 3rd message enables the first service node for instruction.
CN201710642637.4A 2017-07-31 2017-07-31 Method, management node and service node for distributed system transmission service Active CN107391156B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710642637.4A CN107391156B (en) 2017-07-31 2017-07-31 Method, management node and service node for distributed system transmission service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710642637.4A CN107391156B (en) 2017-07-31 2017-07-31 Method, management node and service node for distributed system transmission service

Publications (2)

Publication Number Publication Date
CN107391156A true CN107391156A (en) 2017-11-24
CN107391156B CN107391156B (en) 2021-01-08

Family

ID=60344299

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710642637.4A Active CN107391156B (en) 2017-07-31 2017-07-31 Method, management node and service node for distributed system transmission service

Country Status (1)

Country Link
CN (1) CN107391156B (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108365984A (en) * 2018-02-06 2018-08-03 上海华为技术有限公司 A kind of information processing method and device
CN109032643A (en) * 2018-07-26 2018-12-18 北京百度网讯科技有限公司 The method and apparatus of software upgrading
CN110633096A (en) * 2018-06-21 2019-12-31 阿里巴巴集团控股有限公司 Node control method and device, version control method and device and distributed system
CN110874238A (en) * 2018-09-03 2020-03-10 阿里巴巴集团控股有限公司 Online service updating method and device
CN111338682A (en) * 2020-02-27 2020-06-26 上海百秋电子商务有限公司 Continuous upgrading system service method based on load
CN111382046A (en) * 2018-12-28 2020-07-07 中国电信股份有限公司 Test system, method and device for distributed software system
CN112181915A (en) * 2019-07-03 2021-01-05 成都华为技术有限公司 Method, device, terminal and storage medium for executing service
WO2021135412A1 (en) * 2019-12-31 2021-07-08 华为技术有限公司 Instance deployment method, instance management node, computing node, and computing device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101741894A (en) * 2008-11-26 2010-06-16 中国移动通信集团公司 Upgrade method for distributed system and upgrade scheduling node and system
CN103294675A (en) * 2012-02-23 2013-09-11 上海盛霄云计算技术有限公司 Method and device for updating data in distributed storage system
CN104094248A (en) * 2012-02-02 2014-10-08 微软公司 Self-updating functionality in a distributed system
US20150355932A1 (en) * 2014-06-09 2015-12-10 International Business Machines Corporation Adaptive virtual machine request approver
US20170199922A1 (en) * 2016-01-13 2017-07-13 American Express Travel Related Services Co., Inc. System and method for managing data and updates to a database structure

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101741894A (en) * 2008-11-26 2010-06-16 中国移动通信集团公司 Upgrade method for distributed system and upgrade scheduling node and system
CN104094248A (en) * 2012-02-02 2014-10-08 微软公司 Self-updating functionality in a distributed system
CN103294675A (en) * 2012-02-23 2013-09-11 上海盛霄云计算技术有限公司 Method and device for updating data in distributed storage system
US20150355932A1 (en) * 2014-06-09 2015-12-10 International Business Machines Corporation Adaptive virtual machine request approver
US20170199922A1 (en) * 2016-01-13 2017-07-13 American Express Travel Related Services Co., Inc. System and method for managing data and updates to a database structure

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
张敏狄: "分布式网络设备的业务不中断软件升级系统设计_", 《计算机系统应用》 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108365984A (en) * 2018-02-06 2018-08-03 上海华为技术有限公司 A kind of information processing method and device
CN110633096A (en) * 2018-06-21 2019-12-31 阿里巴巴集团控股有限公司 Node control method and device, version control method and device and distributed system
CN109032643A (en) * 2018-07-26 2018-12-18 北京百度网讯科技有限公司 The method and apparatus of software upgrading
CN110874238A (en) * 2018-09-03 2020-03-10 阿里巴巴集团控股有限公司 Online service updating method and device
CN110874238B (en) * 2018-09-03 2023-04-28 阿里巴巴集团控股有限公司 Online service updating method and device
CN111382046A (en) * 2018-12-28 2020-07-07 中国电信股份有限公司 Test system, method and device for distributed software system
CN111382046B (en) * 2018-12-28 2023-03-28 中国电信股份有限公司 Test system, method and device for distributed software system
CN112181915A (en) * 2019-07-03 2021-01-05 成都华为技术有限公司 Method, device, terminal and storage medium for executing service
CN112181915B (en) * 2019-07-03 2023-12-08 成都华为技术有限公司 Method, device, terminal and storage medium for executing service
WO2021135412A1 (en) * 2019-12-31 2021-07-08 华为技术有限公司 Instance deployment method, instance management node, computing node, and computing device
CN111338682A (en) * 2020-02-27 2020-06-26 上海百秋电子商务有限公司 Continuous upgrading system service method based on load

Also Published As

Publication number Publication date
CN107391156B (en) 2021-01-08

Similar Documents

Publication Publication Date Title
CN107391156A (en) Method, management node and service node for distributed system transmission services
CN105204965B (en) Method and apparatus for the dynamic node reparation in multi-node environment
CN102834806B (en) System architecture management equipment, system architecture management method and program
CN106130972B (en) resource access control method and device
EP2994828B1 (en) Apps store with integrated test support
CN105915650B (en) Load-balancing method and device
US10944655B2 (en) Data verification based upgrades in time series system
CN101984632A (en) Load distributing method, device and server in distributed cache system
CN110784530A (en) Gray scale publishing method and server
CN113472700B (en) Message processing method, device, storage medium and network card
CN109120680A (en) A kind of control system, method and relevant device
JP6015750B2 (en) Log collection server, log collection system, and log collection method
CN110019481A (en) Memory database access method, device, equipment and medium
CN107210971A (en) Network load balancer
CN109729008B (en) Routing method and device and computer equipment
CN108351773B (en) Cloud platform OS management
JP6091333B2 (en) Network management apparatus and network management method
JP2018013994A (en) Program, computer and information processing method
US20160125330A1 (en) Rolling upgrade of metric collection and aggregation system
US20220360494A1 (en) Assisted and context-driven network changes
CN111698266B (en) Service node calling method, device, equipment and readable storage medium
CN105094947B (en) The quota management method and system of a kind of virtual computing resource
CN107046503A (en) A kind of message transmitting method, system and its apparatus
CN113504981A (en) Task scheduling method and device, storage medium and electronic equipment
CN107743615A (en) Content test during image generation

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