JP6696927B2 - Cluster system, update management device for cluster system, update distribution device, update management method, update distribution method and program - Google Patents

Description

  The present invention relates to a software update technique.

  2. Description of the Related Art In the field of Web server hosting and the like, a form called IaaS (Infrastructure as a Service) in which a server management company such as a data center collectively manages a plurality of servers and hosts a service provider has been known. (See, for example, Non-Patent Document 1). On the other hand, in lifeline services such as telephones, high availability was realized by duplication. In order to realize a telephone service on IaaS, a technique of increasing availability and facility utilization efficiency by an N-Active configuration in which N servers are clustered is used. (See, for example, Non-Patent Document 2, Patent Document 1 and Patent Document 2).

JP, 2012-230638, A JP, 2011-096161, A

"Amazon EC2", [online], [Search on February 21, 2017], Internet <URL: http://aws.amazon.com/ec2/> "Infinispan", [online], [February 21, 2017 search], Internet <URL: http://infinispan.org/>

  However, when software is updated without stopping the service, it is usually necessary to carry out data transfer processing to the update destination. In order to perform the data transfer processing, it is necessary to convert the data format before the update to the data format after the update in addition to synchronizing the data to the update destination.

  In view of the above circumstances, it is an object of the present invention to provide a technique capable of reducing the development cost required when updating software in a cluster system.

  An aspect of the present invention is a cluster system including an update management device that updates software of a server having an N-Active configuration, and an update distribution device that distributes a processing request to the server to any of the servers. The update management device updates the software used by the server according to the end of the service provided by the server that is the target of the software update when an instruction to update the software is issued. The update distribution device transmits a processing request to the server that is updating the software to a new server for which the software is updated based on the processing request, or an old server for which the software is not updated. This is a cluster system that includes a distribution unit that determines which of the servers should be processed and distributes it to any of the servers.

  According to an aspect of the present invention, when an instruction to update software of a server having an N-Active configuration is given, the server is used in response to the end of the service provided by the server that is the target of the software update. A server management unit for updating the software, the server management unit monitors the load of the server, stops the service provision of the server in which the load of the server becomes equal to or less than a predetermined threshold, and stops the server. Is an update management device for updating software used by.

  One aspect of the present invention is an update distribution device in a cluster system including an update management device that updates software of a server having an N-Active configuration, and an update distribution device that distributes a processing request to the server to one of the servers. However, whether the processing request to the server during the software update should be processed by the new server where the software is updated or the old server where the software is not updated based on the processing request. A distribution unit that determines and distributes to one of the servers, the distribution unit, when the processing request is the first request in a series of processing that requires consistency, The update distribution device determines that processing should be performed by the new server and distributes it to the new server.

  One aspect of the present invention is the update distribution device described above, wherein when the processing request is not a processing request that does not require session maintenance and is a request that may be discarded, It is determined that the processing request should be processed by the new server, and the processing request is distributed to the new server.

  One aspect of the present invention is an update method performed by a cluster system including an update management device that updates software of a server having an N-Active configuration, and an update distribution device that distributes a processing request to the server to any of the servers. Therefore, when the update management device is instructed to update the software, the software used by the server is updated according to the end of the service provided by the server that is the target of the software update. A server management step of updating, the update distribution device issues a processing request to the server that is updating the software, based on the processing request, a new server for which the software has been updated, or the software has not been updated. This is an update management method having a distribution step of determining which of the old servers should be processed and distributing it to any of the servers.

  According to an aspect of the present invention, when an instruction to update software of a server having an N-Active configuration is given, the server is used in response to the end of the service provided by the server that is the target of the software update. A server management step of updating the software, which monitors the load of the server in the server management step, and stops and stops the service provision of the server when the load of the server becomes a predetermined threshold value or less. This is an update management method for updating the software used by the server.

  One aspect of the present invention is an update distribution device in a cluster system including an update management device that updates software of a server having an N-Active configuration, and an update distribution device that distributes a processing request to the server to one of the servers. In the update distribution method performed by, the processing request to the server during the software update, based on the processing request, the new server for which the software has been updated, or the old server for which the software has not been updated. A distribution step of determining which is to be processed and distributing to one of the servers, and in the distribution step, the processing request is the first request in a series of processing requiring consistency. In this case, the update distribution method determines that the processing request should be processed by the new server and distributes it to the new server.

  One embodiment of the present invention is a program for causing a computer to function as the above device.

  According to the present invention, it is possible to reduce the development cost required for updating software in a cluster system.

It is a block diagram showing the system configuration of the cluster system 100 in the present invention. 3 is a schematic block diagram showing a functional configuration of an update distribution device 20. FIG. 3 is a schematic block diagram showing a functional configuration of an update management device 40. FIG. It is a figure which shows the specific example of a server information file. It is a figure for demonstrating the method of the software update in this embodiment. It is a flow chart which shows a flow of distribution processing of update distribution device 20 in this embodiment. It is a flow chart which shows a flow of distribution processing of update distribution device 20 in this embodiment. It is a flow chart which shows a flow of distribution processing of update distribution device 20 in this embodiment. It is a flow chart which shows a flow of distribution processing of update distribution device 20 in this embodiment. It is a figure for demonstrating the method of the update method when N servers are additionally prepared.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a configuration diagram showing a system configuration of a cluster system 100 according to the present invention. The client device 10 is connected to the cluster system 100 via the external network 1. The external network 1 may be configured using the Internet, for example. The client device 10 is configured using an information processing device such as a personal computer. The client device 10 is a communication device owned by a user who uses a service provided by the cluster system 100. The client device 10 sends a processing request for a service to the cluster system 100.

  The cluster system 100 includes a plurality of update distribution devices 20-1 to 20-M (M is an integer of 2 or more), a plurality of servers 30-1 to 30-N (N is an integer of 2 or more), and an update management device 40. Equipped with. The cluster system 100 is a server having a so-called N-Active configuration. In the following description, the update distribution devices 20-1 to 20-M are referred to as the update distribution device 20 when they are not distinguished. In the following description, the servers 30-1 to 30-N will be referred to as the server 30 if they are not distinguished. The update distribution device 20 and the server 30 are communicably connected via the internal network 50.

  The update distribution device 20, the server 30, and the update management device 40 are communicably connected via the network 60. The internal network 50 and the network 60 may be configured using any network. For example, the internal network 50 and the network 60 may be configured using a LAN (Local Area Network).

  The update distribution device 20 distributes the processing request from the client device 10 to the corresponding server 30. For example, the update distribution device 20 distributes the processing request to the server 30 before software update (hereinafter referred to as “old server”) or the server 30 after software update (hereinafter referred to as “new server”). A specific method for distribution processing of processing requests by the update distribution device 20 will be described later.

  The server 30 is configured using an information processing device such as a personal computer. The server 30 provides a service to the client device 10. The service is, for example, a lifeline service such as a telephone. In the present embodiment, a case will be described as an example where all the servers 30 provide the same service (for example, lifeline service), but the servers 30 may provide different services for each cluster. In addition, in a server having an N-Active configuration, data necessary for maintaining a session is shared between the servers.

  The update management device 40 is configured using an information processing device such as a personal computer. The update management device 40 manages the update distribution device 20 and the server 30. For example, when the update management device 40 receives an instruction to update the software used by the server 30, the update management device 40 updates the software. At this time, the update management device 40 updates the software used by the server 30 when the service being processed by the server 30 to be updated ends. The specific method of updating will be described later.

FIG. 2 is a schematic block diagram showing the functional configuration of the update distribution device 20.
The update distribution device 20 includes a CPU (Central Processing Unit), a memory, and an auxiliary storage device that are connected by a bus, and executes a load distribution processing program. By executing the load distribution processing program, the update distribution device 20 functions as a device including the distribution information storage unit 201, the update unit 202, and the distribution unit 203. Note that all or some of the functions of the update distribution device 20 may be realized using hardware such as an ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and FPGA (Field Programmable Gate Array). Good. The load distribution processing program may be recorded in a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, the load distribution processing program may be transmitted / received via an electric communication line.

  The distribution information storage unit 201 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The distribution information storage unit 201 stores a distribution information file. The distribution information file is a file used when distributing a processing request from the client device 10. The distribution information file is associated with the server name and the file old / new display. The server name is information for identifying the server 30. In the file new / old display, information indicating whether the server 30 is a new server or an old server when software update is necessary is registered. In the distribution information file, if the server 30 is the new server, "new" is registered in the file new / old display item, and if the server 30 is the old server, "old" is registered in the file new / old display item. To be done. If software update is not necessary, "-" is registered in the item of file old / new display.

The update unit 202 updates the distribution information file according to the instruction from the update management device 40. For example, the updating unit 202 registers or deletes the server 30 in the distribution information file and changes the items of the file old / new display.
When a processing request is received from the client device 10, the distribution unit 203 refers to the distribution information file and distributes the processing request to the corresponding server 30.

FIG. 3 is a schematic block diagram showing the functional configuration of the update management device 40.
The update management device 40 includes a CPU, a memory, an auxiliary storage device, and the like connected by a bus, and executes a management program. By executing the management program, the update management device 40 functions as a device including the command processing unit 401, the server information storage unit 402, and the server management unit 403. Note that all or part of each function of the update management device 40 may be realized using hardware such as ASIC, PLD, and FPGA. Further, the management program may be recorded in a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, the management program may be transmitted / received via an electric communication line.

The command processing unit 401 receives a command for adding or deleting a server to the cluster system 100, a command for updating software, and a command for starting or ending a service of the server 30, and performs processing according to the received command.
The server information storage unit 402 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The server information storage unit 402 stores a server information file. The server information file is a file in which information about the server 30 included in the cluster system 100 is registered.

FIG. 4 is a diagram showing a specific example of the server information file.
The server information file has a plurality of records. The record has the values of server name, service, and server load. The value of the server name is information for identifying the server 30. The service value represents the service name provided by the server 30. The value of the server load represents the load status of the server 30.

  In the example shown in FIG. 4, four server names are registered in the server information file. These server names are "Server A", "Server B", "Server C", and "Server D". In FIG. 4, in the record recorded at the top of the server information file, the value of the server name is "Server A", the value of the service is "Lifeline Service", and the value of the server load is "○○". That is, it is indicated that the server name "Server A" provides "lifeline service" and the current load of the server is "XX". The configuration of the server information file is not limited to the configuration shown in FIG. 4, and necessary information may be added as appropriate.

Returning to FIG. 3, the description of the update management device 40 will be continued.
The server management unit 403 manages the server 30. For example, the server management unit 403 performs addition or deletion of the server 30, start or end of service of the server 30, change of service provided by the server 30, and the like according to a command input to the command processing unit 401. In addition, the server management unit 403 monitors the operating state of the server 30 and acquires the load of the server 30 at a predetermined timing. The server management unit 403 registers the acquired load in the server information file. The predetermined timing may be a preset timing, a timing when a command is input, or another timing.

  Next, a method of updating software according to this embodiment will be described with reference to FIG. FIG. 5 is a diagram for explaining the software update method according to the present embodiment. Note that, in FIG. 5, a method of updating software will be described using a distribution information file. In FIG. 5, information indicating four servers 30 (server names: “A” server, “B” server, “C” server, and “D” server) is registered in the distribution information file.

  FIG. 5A shows a state before updating the software of the distribution information file. For example, the state of FIG. 5A is set as the initial state. In the example shown in FIG. 5A, since the software update is not required, “-” is registered in the file new / old display item for all four servers 30.

When the software update is required, that is, when the software update command is input to the update management device 40, the command processing unit 401 notifies that the software update is required (hereinafter referred to as “update request”). .) To the update distribution device 20. Further, the command processing unit 401 transmits a notification indicating that software update is to be executed (hereinafter referred to as “update execution request”) to the server management unit 403. The update request includes the server name of the server 30 that uses the software to be updated. In FIG. 5, it is assumed that the update request includes the server names of the four servers 30 (server names: “A” server, “B” server, “C” server, and “D” server). The update execution request includes the server name of the server 30 that uses the software to be updated and the software for updating.
Upon receiving the update request from the update management device 40, the update unit 202 refers to the distribution information file and updates the file old / new display item of the server 30 corresponding to the server name included in the update request to “old”. An example of the distribution information file after this processing is shown in FIG.

Next, the server management unit 403 monitors the load of the server 30 corresponding to the server name included in the update execution request, and stops the server 30 having the load equal to or less than the predetermined threshold. Here, it is assumed that the "D" server is below the threshold. In this case, the server management unit 403 stops the "D" server. After that, the server management unit 403 transmits, via the command processing unit 401, a notification indicating that the server 30 has been stopped (hereinafter referred to as “stop request”) to the update distribution device 20. The stop request includes the server name of the stopped server 30. In FIG. 5, the stop request includes information indicating the “D” server.
Upon receiving the stop request from the update management device 40, the update unit 202 refers to the distribution information file and deletes the server 30 corresponding to the server name included in the stop request from the distribution information file. For example, the update unit 202 deletes the record including the information about the “D” server from the distribution information file. An example of the distribution information file after this processing is shown in FIG.

  Next, the server management unit 403 updates the software used by the stopped server using the software included in the update execution request. For example, the server management unit 403 updates the software used by the “D” server. After the update is completed, the server management unit 403 issues a notification (hereinafter referred to as “completion notification”) indicating that the update of the software used by the server 30 is completed via the command processing unit 401. Send to 20. The completion notification includes the server name of the server 30 that has completed the update. In FIG. 5, it is assumed that the completion notification includes information indicating the “D” server.

  Upon receiving the completion notice from the update management device 40, the update unit 202 newly registers the server name included in the completion notice in the distribution information file. At this time, the updating unit 202 registers “new” in the file new / old display item of the newly registered server 30. In this process, the update unit 202 registers "D" server in the server name of the distribution information file and "new" in the item of file old / new display. An example of the distribution information file after this processing is shown in FIG. A processing request from the client received by the update distribution device 20 after this time is distributed to the server 30 according to a distribution method described later.

As described above, the server management unit 403 sequentially stops the servers 30 as the load on the servers 30 decreases, and then updates the software. By repeating this process, the file old / new display item of at least one server 30 finally becomes the "old" state. In the example of FIG. 5E, only the “A” server has the item “old” in the file old / new display. Server management when processing on the server whose file old / new display item is "old" is completed, or when processing is forcibly ended manually on the server whose file old / new display item is "old" The unit 403 stops the last remaining "A" server. After that, the server management unit 403 transmits a stop request to the update distribution device 20 via the command processing unit 401. The stop request in this process includes information indicating the "A" server.
Upon receiving the stop request from the update management device 40, the update unit 202 refers to the distribution information file and deletes the server 30 corresponding to the server name included in the stop request from the distribution information file. For example, the update unit 202 deletes the record including the information about the “A” server from the distribution information file. An example of the distribution information file after this processing is shown in FIG.

Next, the server management unit 403 updates the software used by the stopped server using the software included in the update execution request. For example, the server management unit 403 updates the software used by the “A” server. After the update is completed, the server management unit 403 transmits a completion notification to the update distribution device 20 via the command processing unit 401. It is assumed that the completion notification in this processing includes information indicating the "A" server.
Upon receiving the completion notice from the update management device 40, the update unit 202 newly registers the server name included in the completion notice in the distribution information file. At this time, the updating unit 202 registers “new” in the file new / old display item of the newly registered server 30. In this process, the updating unit 202 registers "A" server in the server name of the distribution information file and "new" in the item of file old / new display. An example of the distribution information file after this processing is shown in FIG.
By the above processing, all the items of the file old and new display of the distribution information file become "new". This completes the upload. After that, the distribution information storage unit 201 updates the distribution information file to the initial state. An example of the distribution information file after this processing is shown in FIG.

6 to 9 are flowcharts showing the flow of the distribution process of the update distribution device 20 in this embodiment.
When the processing request is received from the client device 10, the distribution unit 203 refers to the distribution information file and determines whether the file new / old display item is "-" or all "old" (step S101). ). When the file new / old display item is "-" or all "old" (step S101-YES), the distribution unit 203 performs a normal load balancing process (round robin or the like) (step S102). After that, the update distribution device 20 ends the processing of FIG.

  On the other hand, when the file new / old display item is "-", or some of them are "old" or all of them are "new" (step S101-NO), the distribution unit 203 determines that the processing requests are consistent. It is determined whether or not the request is the first request (for example, an invitation of the SIP (Session Initiation Protocol) protocol) of the required series of processing (for example, a processing request that requires session maintenance) (step S103). When the processing request is the first request (step S103-YES), the distribution unit 203 performs normal load balancing processing on the server 30 (new server) whose file new / old display item is "new" (step S104). ).

On the other hand, if the processing request is not the first request (step S103-NO), the distribution unit 203 determines whether the processing request is a request for processing that does not require session maintenance (step S105). If the request is for a process that does not require session maintenance (step S105-YES), the distribution unit 203 performs the process of step S104.
On the other hand, when the session maintenance is not an unnecessary processing request, that is, when the session maintenance is required (step S105-NO), the distribution unit 203 determines whether or not the processing request may be discarded. When it is determined (step S106) that the processing request may be discarded (step S106-YES), the distribution unit 203 performs load distribution processing on the processing request to the new server (step S107). Here, a request for processing that requires session maintenance, but the processing request may be discarded is, for example, a processing request before ACK when Confirmed Dialog of the SIP protocol is used as call relief.

Further, in the processing of step S106, when the processing request should not be discarded (step S106-NO), the distribution unit 203 receives information about the server 30 processed at the time of the previous processing request (for example, the Record-Route header of the SIP protocol). It is determined whether or not there is a server 30 that matches () (step S108). When there is the server 30 processed at the time of the previous processing request (step S108-YES), the distribution unit 203 distributes the processing request to the server 30 processed last time (step S109). Then, the distribution unit 203 determines whether the previously processed server 30 has the previously processed information (step S110). If the previously processed server 30 has the previously processed information (step S110-YES), the update distribution device 20 ends the distribution process. For example, when the distribution unit 203 does not receive the notification that the processing request cannot be processed from the previously processed server 30, the distribution unit 203 determines that the previously processed server 30 has the previously processed information.
On the other hand, when there is no previously processed information in the previously processed server 30 (step S110-NO), the distribution unit 203 performs load distribution processing on the servers 30 having different file old and new file display items (step S111). For example, the distribution unit 203 determines that there is no previously processed information in the previously processed server 30 when a notification that the processing request cannot be processed is acquired from the previously processed server 30.

Next, the distribution unit 203 determines whether or not there is previously processed information in the server 30 having different file new / old display items (step S112). If the server 30 having different file old / new display items has the previously processed information (step S112-YES), the update distribution device 20 ends the distribution process.
On the other hand, when there is no previously processed information in the server 30 having different file old / new display items (step S112-NO), the distribution unit 203 discards the processing request (step S113). After that, the update distribution device 20 ends the distribution process.

Further, in the process of step S108, when there is no server 30 processed at the time of the previous process request (step S108-NO), the distribution unit 203 performs the load distribution process on the old server (step S114). After that, the distribution unit 203 determines whether or not there is information processed last time in the server 30 whose file new / old display item is "old" (step S115). When the server 30 whose file new / old display item is “old” has the previously processed information (step S115-YES), the update distribution device 20 ends the distribution process.
On the other hand, when there is no previously processed information in the server 30 whose file new / old display item is "old" (step S115-NO), the distribution unit 203 performs load distribution processing on the new server 30 (step S116).

After that, the distribution unit 203 determines whether or not there is the previously processed information in the server 30 whose file new / old display item is "new" (step S117). When the server 30 whose file new / old display item is “new” has the previously processed information (step S117-YES), the update distribution device 20 ends the distribution process.
On the other hand, when there is no previously processed information in the server 30 whose file new / old display item is "new" (step S117-NO), the distribution unit 203 discards the processing request (step S118). After that, the update distribution device 20 ends the distribution process.

  In the cluster system 100 configured as described above, the update management device 40 updates the server 30 when the service being processed by the server 30 before the update ends. As a result, the data transfer process can be reduced. Further, the update distribution device 20 determines whether the processing request for the server 30 being updated should be processed by the new server or the old server, and distributes it to the corresponding server 30. Therefore, the cost required for the data transfer processing can be reduced. Therefore, in the cluster system, it is possible to reduce the development cost required when updating the software.

  If the processing request is not a request that the processing request may be abandoned and there is the server 30 that processed the processing request, the distribution unit 203 may distribute the processing request to the server 30 that processed the processing request and discard the processing request. If there is no server 30 that processed the request, not the request, the process request is distributed to the old server.

<Modification>
In the cluster system 100 according to the present embodiment, if the server pool has sufficient resources for IaaS or the like, another server resource may be used when updating the software. In that case, if the number of operating servers is N, 1 to N additional servers 30 are required for updating. An updating method when N servers are additionally prepared for updating will be described with reference to FIG. Note that, in FIG. 10, a method of updating software will be described using a distribution information file. In FIG. 10, at the start of processing, information indicating four servers 30 (server names: “A” server, “B” server, “C” server, and “D” server) is registered in the distribution information file. .

  FIG. 10A shows a state before updating the software of the distribution information file. For example, the state of FIG. 10A is set as the initial state. In the example shown in FIG. 10A, since the software update is not required, "-" is registered in the file new / old display item for all four servers 30.

When software update is required, that is, when a software update command is input to the update management device 40, the command processing unit 401 sends an update request to the update distribution device 20. The command processing unit 401 also sends an update execution request to the server management unit 403. The update request includes the server name of the server 30 that uses the software to be updated. In FIG. 10, it is assumed that the update request includes the server names of the four servers 30 (server names: “A” server, “B” server, “C” server, and “D” server). The update execution request includes the server name of the server 30 that uses the software to be updated and the software for updating.
Upon receiving the update request from the update management device 40, the update unit 202 refers to the distribution information file and updates the file old / new display item of the server 30 corresponding to the server name included in the update request to “old”. An example of the distribution information file after this processing is shown in FIG.

  Next, the server management unit 403 prepares a new server (for example, “E” server) from the server pool, and installs new software on the new server (for example, “E” server). The server management unit 403 transmits a notification indicating that the software is installed in the new server 30 (hereinafter, referred to as “addition request”) to the update distribution device 20 via the command processing unit 401. The addition request includes the server name (for example, "E" server) of the server 30 in which the software is newly installed.

  Upon receiving the addition request from the update management device 40, the update unit 202 refers to the distribution information file and newly registers the server name included in the addition request in the distribution information file. At this time, the updating unit 202 registers “new” in the file new / old display item of the newly registered server 30. In this process, the updating unit 202 registers "E" server in the server name of the distribution information file and "new" in the item of file old / new display. An example of the distribution information file after this processing is shown in FIG. The update distribution device 20 and the update management device 40 perform the above processing for the number of operating old softwares (four in FIG. 10). An example of the distribution information file after this processing is shown in FIG. A processing request from the client received by the update distribution device 20 after this time is distributed to the server 30 according to a distribution method described later.

Next, the server management unit 403 monitors the load of the server 30 corresponding to the server name included in the update execution request, and stops the server 30 having the load equal to or less than the predetermined threshold. Here, it is assumed that the "D" server is below the threshold. In this case, the server management unit 403 stops the "D" server. After that, the server management unit 403 transmits a stop request to the update distribution device 20 via the command processing unit 401. The stop request includes the server name of the stopped server 30. In this process, it is assumed that the stop request includes information indicating the "D" server.
Upon receiving the stop request from the update management device 40, the update unit 202 refers to the distribution information file and deletes the server 30 corresponding to the server name included in the stop request from the distribution information file. For example, the update unit 202 deletes the record including the information about the “D” server from the distribution information file. An example of the distribution information file after this processing is shown in FIG.

As described above, the server management unit 403 sequentially stops the servers 30 as the load on the servers 30 decreases, and then updates the software. By repeating this process, the file old / new display item of at least one server 30 finally becomes the "old" state. In the example of FIG. 10 (F), only the “A” server has the item “old” in the file new / old display. Server management when processing on the server whose file old / new display item is "old" is completed, or when processing is forcibly ended manually on the server whose file old / new display item is "old" The unit 403 stops the last remaining "A" server. After that, the server management unit 403 transmits a stop request to the update distribution device 20 via the command processing unit 401. The stop request in this process includes information indicating the "A" server.
Upon receiving the stop request from the update management device 40, the update unit 202 refers to the distribution information file and deletes the server 30 corresponding to the server name included in the stop request from the distribution information file. For example, the update unit 202 deletes the record including the information about the “A” server from the distribution information file. An example of the distribution information file after this processing is shown in FIG.
By the above processing, the file old and new display items of the distribution information file become the newly added server 30, and all become "new". This completes the upload. After that, the distribution information storage unit 201 updates the distribution information file to the initial state. An example of the distribution information file after this processing is shown in FIG.

  Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and includes a design and the like within a range not departing from the gist of the present invention.

10 ... Client device, 20, 20-1 to 20-M ... Update distribution device, 30, 30-1 to 30-N ... Server, 40 ... Update management device, 50 ... Internal network, 60 ... Network, 201 ... Distribution Minute information storage unit, 202 ... update unit, 203 ... distribution unit, 401 ... command processing unit, 402 ... server information storage unit, 403 ... server management unit

Claims (3)

An update management device that updates the software of the server of the N-Active configuration that shares data required for maintaining a session between the servers, and an update distribution device that distributes the processing request to the server to any of the servers A cluster system,
The update management device,
When an instruction to update the software is given, a server management unit that updates the software used by the server according to the end of the service provided by the server that is the target of the software update,
Equipped with
The update distribution device,
Based on the processing request, the processing request to the server during the software update is determined by which of the new server for which the software has been updated or the old server for which the software has not been updated. Distribution unit that distributes to that server,
Equipped with
The distribution unit is a request that the processing request must not be discarded, and when there is a server that processed the processing request, the processing request is distributed to the server that processed the processing request, and the processing request is discarded and a request not, if there is no server that processes the processing request, distributing Ru cluster system the processing request to the old server. An update management device that updates the software of the server of the N-Active configuration that shares data required for maintaining a session between the servers, and an update distribution device that distributes the processing request to the server to any of the servers The update method performed by the cluster system,
A server that updates the software used by the server when the update management device issues an instruction to update the software, according to the end of the service provided by the server that is the target of the software update. Management steps,
Based on the processing request, the update distribution device processes a processing request for the server that is updating the software, by a new server where the software is updated or an old server where the software is not updated. It has a sorting step that determines whether it should be done and assigns it to one of the servers,
In the distribution step, if the processing request is a request that must not be discarded and there is a server that processed the processing request, the processing request is distributed to the server that processed the processing request, and the processing request is discarded and a request not, if there is no server that processes the processing request, distributing Ru update management method the processing request to the old server. A program for causing a computer to function as the device according to claim 1 .

Images