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

Abstract

PROBLEM TO BE SOLVED: To reduce development cost required for software update in a cluster system.SOLUTION: A cluster system comprises: an update management device that performs software update for an N-Active configuration server; and an update distribution device that distributes a processing request to one of servers. The update management device comprises a server management section that, in a case where a software update instruction is given, updates software according to the termination of a service provided by a server to be updated. The update distribution device comprises a distribution section that, on the basis of the processing request, determines which one, a new server subjected to update or a former server not subjected to update, should be used to process the processing request for a server being updated, and distributes it to one of the servers.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a software update technique.

  Conventionally, in the field of web server hosting and the like, a form called IaaS (Infrastructure as a Service) or the like in which a server management company such as a data center collectively manages a plurality of servers and hosts a service provider (See, for example, Non-Patent Document 1). On the other hand, lifeline services such as telephones have achieved high availability through duplication. In order to realize a telephone service on IaaS, a technology for increasing availability and facility utilization efficiency by using an N-Active configuration in which N servers are clustered is used. (For example, refer nonpatent literature 2, patent literature 1, and patent literature 2).

JP 2012-230638 A JP 2011-096161 A

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

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

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

  One aspect of the present invention is a cluster system including an update management apparatus that updates software of a server having an N-Active configuration, and an update distribution apparatus that distributes a processing request to the server to any one of the servers, The update management device is a server management for updating software used by the server in response to termination of a service provided by the server that is a target of the software update when an instruction to update the software is given. The update distribution device includes a new server in which software has been updated based on the processing request, or an old in which no software has been updated based on the processing request. Determines whether to be processed by any of over server, a cluster system comprising a distribution unit, which distributes to any of the servers.

  According to one aspect of the present invention, when an instruction to update software of a server having an N-Active configuration is given, the server uses the server in response to termination of a service provided by the server to be updated by the software. A server management unit that updates the software that is running, the server management unit monitors the load on the server, stops service provision of the server whose load is below a predetermined threshold, and stops the server It is an update management device that updates the software used by.

  One aspect of the present invention is an update distribution apparatus in a cluster system including an update management apparatus that updates software of a server having an N-Active configuration, and an update distribution apparatus that distributes processing requests to the server to any one of the servers. Whether the processing request to the server during the software update should be processed by the new server that has been updated by the software or the old server that has not been updated by the software based on the processing request. Determining and allocating to any one of the servers, wherein the allocating unit determines the processing request when the processing request is a first request in a series of processes requiring consistency. The server determines that the new server should be processed and allocates to the new server. It is a date sorting equipment.

  One aspect of the present invention is the update distribution device described above, wherein the distribution unit is configured such that 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 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 apparatus that updates software of a server having an N-Active configuration and an update distribution apparatus that distributes processing requests to the server. When the update management device is instructed to update the software, the software used by the server is updated in response to termination of the service provided by the server that is the target of the software update. A server management step for updating, wherein the update distribution apparatus sends a processing request to the server during the software update to a new server updated with software or a software update based on the processing request. Determines that should be processed in any that is not the old server made, an update management method having a sorting step of sorting to any of the servers.

  According to one aspect of the present invention, when an instruction to update software of a server having an N-Active configuration is given, the server uses the server in response to termination of a service provided by the server to be updated by the software. A server management step for updating the software, and in the server management step, the load on the server is monitored, and the service provision of the server whose load on the server falls below a predetermined threshold is stopped and stopped. This is an update management method for updating software used by a server.

  One aspect of the present invention is an update distribution apparatus in a cluster system including an update management apparatus that updates software of a server having an N-Active configuration, and an update distribution apparatus that distributes processing requests to the server to any one of the servers. An update distribution method performed by the server, wherein a processing request to the server that is updating the software is sent to a new server that has been updated based on the processing request or an old server that has not been updated. A distribution step for deciding which should be processed and allocating to any server, wherein in the distribution step, the processing request is the first request in a series of processing that needs consistency In this case, the processing request is processed by the new server. It determines that to be an update distribution method of distributing the new server.

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

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

It is a block diagram showing the system configuration | structure of the cluster system 100 in this invention. 3 is a schematic block diagram illustrating 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 flowchart which shows the flow of the distribution process of the update distribution apparatus 20 in this embodiment. It is a flowchart which shows the flow of the distribution process of the update distribution apparatus 20 in this embodiment. It is a flowchart which shows the flow of the distribution process of the update distribution apparatus 20 in this embodiment. It is a flowchart which shows the flow of the distribution process of the update distribution apparatus 20 in this embodiment. It is a figure for demonstrating the method of the update method when N servers are prepared additionally.

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. A client apparatus 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 transmits a processing request for a service to the cluster system 100.

  The cluster system 100 includes a plurality of update distribution apparatuses 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 apparatus 40. Is provided. 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 described as update distribution devices 20 when they are not distinguished. In the following description, the servers 30-1 to 30-N are referred to as servers 30 when they are not distinguished. The update distribution device 20 and the server 30 are connected to be communicable via the internal network 50.

  The update distribution device 20 and the server 30 and the update management device 40 are connected via a network 60 so that they can communicate with each other. 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 the distribution processing of processing requests by the update distribution device 20 will be described later.

  The server 30 is configured using an information processing apparatus 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 this embodiment, a case where all the servers 30 are servers that provide the same service (for example, lifeline service) will be described as an example. However, the servers 30 that provide different services for each cluster may be used. Note that, in a server with 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 an update instruction for software used in the server 30 is input, the update management apparatus 40 updates the software. At this time, the update management device 40 updates the software used in the server 30 when the service being processed in the server 30 to be updated is terminated. A specific method of updating will be described later.

FIG. 2 is a schematic block diagram showing a functional configuration of the update distribution device 20.
The update distribution device 20 includes a CPU (Central Processing Unit), a memory, an auxiliary storage device, and the like 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 a distribution information storage unit 201, an update unit 202, and a distribution unit 203. All or some of the functions of the update distribution device 20 may be realized using hardware such as an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA). Good. Further, the load distribution processing program may be recorded on 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 the computer system. The load distribution processing program may be transmitted / received via a telecommunication 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 processing requests from the client device 10. In the distribution information file, the server name is associated with the file old / new display. The server name is information for specifying 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 required is registered. In the distribution information file, when the server 30 is a new server, “new” is registered in the item of the file old / old display, and when the server 30 is the old server, “old” is registered in the item of the file old / old display. Is done. If no software update is required, “-” is registered in the file old / old display item.

The update unit 202 updates the distribution information file in accordance with instructions from the update management device 40. For example, the update unit 202 performs registration and deletion of the server 30 in the distribution information file and changes in the items of 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 illustrating a functional configuration of the update management apparatus 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 a command processing unit 401, a server information storage unit 402, and a server management unit 403. All or some of the functions of the update management apparatus 40 may be realized using hardware such as an ASIC, PLD, or FPGA. The management program may be recorded on 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 the computer system. Further, the management program may be transmitted / received via a telecommunication line.

The command processing unit 401 receives a server addition or deletion command for the cluster system 100, a software update command, and a service start or service end command for 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 related to the server 30 provided 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 values of server name, service, and server load. The value of the server name is information for specifying the server 30. The service value represents the name of a service 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, the record recorded at the top of the server information file has a server name value “server A”, a service value “lifeline service”, and a server load value “OO”. That is, it is indicated that the server name “Server A” provides “Lifeline Service” and the current server load is “XXX”. 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 adds or deletes the server 30, starts or ends the service of the server 30, changes the service provided by the server 30, etc. according to the command input to the command processing unit 401. In addition, the server management unit 403 monitors the operating state of the server 30 at a predetermined timing and acquires the load of the server 30. 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 software update method according to this embodiment will be described with reference to FIG. FIG. 5 is a diagram for explaining a software update method according to this embodiment. In FIG. 5, a software update method 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 the software of the distribution information file is updated. For example, the state of FIG. In the example shown in FIG. 5A, since no software update is required, “-” is registered in the item of file new / old display for all four servers 30.

When a software update is required, that is, when a software update command is input to the update management apparatus 40, the command processing unit 401 sends a notification indicating that a software update is necessary (hereinafter referred to as "update request"). .) Is transmitted to the update distribution device 20. In addition, the command processing unit 401 transmits a notification (hereinafter referred to as “update execution request”) indicating that the software update is to be executed 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 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 using the software to be updated and the software for updating.
When receiving the update request from the update management apparatus 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 whose load is equal to or less than a predetermined threshold. Here, it is assumed that the “D” server is equal to or less than the threshold value. In this case, the server management unit 403 stops the “D” server. Thereafter, the server management unit 403 transmits a notification (hereinafter referred to as “stop request”) indicating that the server 30 has been stopped 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 FIG. 5, it is assumed that the stop request includes information indicating the “D” server.
When receiving the stop request from the update management apparatus 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 a record including information related to 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 uses the software included in the update execution request to update the software used by the stopped server. 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 sends 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 to the update distribution device. 20 to send. The completion notification includes the server name of the server 30 that has been updated. In FIG. 5, it is assumed that the completion notification includes information indicating the “D” server.

  When receiving the completion notification from the update management device 40, the update unit 202 newly registers the server name included in the completion notification in the distribution information file. At this time, the update 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 new / old display. An example of the distribution information file after this processing is shown in FIG. Processing requests from the client received by the update distribution device 20 after this time are distributed to the server 30 according to a distribution method described later.

As described above, the server management unit 403 sequentially updates the software after stopping the servers 30 as the load on the server 30 decreases. By repeating this process, the file new / old display item of at least one server 30 is finally set to the “old” state. In the example of FIG. 5E, only the “A” server has the file old / old display item “old”. Server management at the time when processing on the server with the "old / old" display item is completed, or when processing on the server with the "old / old" display item is forcibly terminated manually, etc. The unit 403 stops the last remaining “A” server. Thereafter, the server management unit 403 transmits a stop request to the update distribution apparatus 20 via the command processing unit 401. The stop request in this process includes information indicating the “A” server.
When receiving the stop request from the update management apparatus 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 a record including information on 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 uses the software included in the update execution request to update the software used by the stopped server. 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 apparatus 20 via the command processing unit 401. It is assumed that the completion notification in this process includes information indicating the “A” server.
When receiving the completion notification from the update management device 40, the update unit 202 newly registers the server name included in the completion notification in the distribution information file. At this time, the update 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 “A” server as the server name of the distribution information file and “new” as the item of file new / old display. An example of the distribution information file after this processing is shown in FIG.
As a result of the above processing, all the items of the file old / new display in the distribution information file become “new”. This completes the upload. Thereafter, 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 the present embodiment.
When a processing request is received from the client device 10, the distribution unit 203 refers to the distribution information file and determines whether the items of the file new / old display are “-” or all “old” (step S101). ). If the file new / old display items are “-” or all “old” (step S101—YES), the distribution unit 203 performs normal load distribution processing (round robin or the like) (step S102). Thereafter, the update distribution device 20 ends the process of FIG.

  On the other hand, if the file new / old display items are “-”, some are “old”, or all are “new” (NO in step S101), the allocating unit 203 makes a processing request consistent. It is determined whether or not it is the first request (for example, an invitation of SIP (Session Initiation Protocol) protocol) in a necessary 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 distribution processing on the server 30 (new server) whose file new / old display item is “new” (step S104). ).

On the other hand, when the processing request is not the first request (step S103—NO), the allocating unit 203 determines whether the processing request is a processing request that does not require session maintenance (step S105). When 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, if it is not a request for a process that does not require session maintenance, that is, a request for a process that requires session maintenance (NO in step S105), whether or not the allocating unit 203 can discard the process request. When determining (step S106) the processing request may be discarded (step S106-YES), the allocating unit 203 performs load distribution processing on the new server (step S107). Here, a request for processing that requires session maintenance, but the case where the processing request may be discarded is a processing request before ACK when, for example, SIP protocol Confirmed Daialog is used as call rescue.

In the process of step S106, if the processing request should not be discarded (NO in step S106), the allocating unit 203 uses the information of the server 30 processed at the time of the previous processing request (for example, the Record-Route header of the SIP protocol). ) Is determined whether there is a server 30 that matches (step S108). When there is a 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). Thereafter, the allocating unit 203 determines whether or not the previously processed server 30 has the previously processed information (step S110). When there is information processed last time in the server 30 processed last time (step S110-YES), the update distribution device 20 ends the distribution processing. For example, the distribution unit 203 determines that there is information processed last time in the server 30 processed last time when the notification that the processing request cannot be processed is not acquired from the server 30 processed last time.
On the other hand, when there is no information processed last time in the server 30 processed last time (step S110-NO), the distribution unit 203 performs load distribution processing on the server 30 having different contents of the file old and new display items (step S111). For example, the distribution unit 203 determines that the previously processed server 30 does not have the previously processed information when the notification that the processing request cannot be processed is acquired from the previously processed server 30.

Next, the allocating unit 203 determines whether or not there is information processed last time in the server 30 having the contents different in the file old / new display items (step S112). When there is information processed last time in the server 30 having different contents in the file old / new display items (step S112—YES), the update distribution device 20 ends the distribution process.
On the other hand, when there is no information processed last time in the server 30 with different contents of the file new and old display items (NO in step S112), the distribution unit 203 discards the processing request (step S113). Thereafter, the update distribution device 20 ends the distribution process.

Further, in the process of step S108, if there is no server 30 processed at the time of the previous process request (step S108-NO), the allocating unit 203 performs load distribution processing on the old server (step S114). Thereafter, the distribution unit 203 determines whether or not there is information processed last time in the server 30 whose file old / new display item is “old” (step S115). When there is information processed last time in the server 30 whose file new / old display item is “old” (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).

Thereafter, the allocating unit 203 determines whether or not there is information processed last time in the server 30 whose file new / old display item is “new” (step S117). If there is information processed last time in the server 30 whose file new / old display item is “new” (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). Thereafter, the update distribution device 20 ends the distribution process.

  In the cluster system 100 configured as described above, the update management apparatus 40 updates the corresponding server 30 when the service being processed in the server 30 before the update ends. Thereby, data transfer processing 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 the processing request to the corresponding server 30. Therefore, the cost required for the data transfer process can be reduced. Therefore, it is possible to reduce the development cost required when updating software in the cluster system.

  If the processing request is not a request that can be discarded, and there is a server 30 that has processed the processing request, the distribution unit 203 may distribute the processing request to the server 30 that has processed the processing request, and the processing request may be discarded. If there is no server 30 that has processed the processing request instead of the request, the processing request is distributed to the old server.

<Modification>
In the cluster system 100 according to the present embodiment, when there is a resource margin in the server pool such as IaaS, another server resource may be used when updating the software. In that case, if the number of servers in operation is N, additional 1 to N servers 30 are required for updating. An update method when N servers are additionally prepared for update will be described with reference to FIG. In FIG. 10, a software update method 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 the software of the distribution information file is updated. For example, the state shown in FIG. In the example shown in FIG. 10A, software update is not required, so “−” is registered in the file old / new display item for all four servers 30.

When software update becomes necessary, that is, when a software update command is input to the update management apparatus 40, the command processing unit 401 transmits an update request to the update distribution apparatus 20. In addition, the command processing unit 401 transmits 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 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 using the software to be updated and the software for updating.
When receiving the update request from the update management apparatus 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 (hereinafter referred to as “addition request”) indicating that the software is installed in the new server 30 to the update distribution apparatus 20 via the command processing unit 401. The addition request includes the server name (for example, “E” server) of the server 30 on which the software is newly installed.

  When receiving the addition request from the update management apparatus 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 update 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 “E” server as the server name of the distribution information file and “new” as the item of file new / old 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-described processing for the number of old software operations (four in FIG. 10). An example of the distribution information file after this processing is shown in FIG. Processing requests from the client received by the update distribution device 20 after this time are 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 whose load is equal to or less than a predetermined threshold. Here, it is assumed that the “D” server is equal to or less than the threshold value. In this case, the server management unit 403 stops the “D” server. Thereafter, the server management unit 403 transmits a stop request to the update distribution apparatus 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 information indicating “D” server is included in the stop request.
When receiving the stop request from the update management apparatus 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 a record including information related to 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 updates the software after stopping the servers 30 as the load on the server 30 decreases. By repeating this process, the file new / old display item of at least one server 30 is finally set to the “old” state. In the example of FIG. 10F, only the “A” server has the file old / old display item “old”. Server management at the time when processing on the server with the "old / old" display item is completed, or when processing on the server with the "old / old" display item is forcibly terminated manually, etc. The unit 403 stops the last remaining “A” server. Thereafter, the server management unit 403 transmits a stop request to the update distribution apparatus 20 via the command processing unit 401. The stop request in this process includes information indicating the “A” server.
When receiving the stop request from the update management apparatus 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 a record including information on 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 server 30 to which the file old / new display items of the distribution information file are newly added becomes “new”. This completes the upload. Thereafter, 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.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes designs and the like that do not depart from the gist of the present invention.

DESCRIPTION OF SYMBOLS 10 ... Client apparatus, 20, 20-1-20-M ... Update distribution apparatus, 30, 30-1-30-N ... Server, 40 ... Update management apparatus, 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 (8)

A cluster system comprising: an update management device that updates software of a server having an N-Active configuration; and an update distribution device that distributes processing requests to the server to any one of the servers,
The update management device includes:
A server management unit that updates software used by the server in response to termination of a service provided by the server that is a target of the software update when an instruction to update the software is given;
With
The update distribution device includes:
Based on the processing request, it is determined whether the processing request to the server during the software update is to be processed by the new server in which the software is updated or the old server in which the software is not updated. The distribution part that distributes to the server
A cluster system comprising: A server that updates the software used by the server in response to the termination of the service provided by the server that is the target of the software update when an instruction to update the software of the server having the N-Active configuration is given Management Department,
With
The server management unit is an update management apparatus that monitors a load of the server, stops providing a service of a server whose load is equal to or less than a predetermined threshold, and updates software used by the stopped server. An update distribution apparatus in a cluster system comprising: an update management apparatus that updates software of a server having an N-Active configuration; and an update distribution apparatus that distributes processing requests to the server to any one of the servers,
Based on the processing request, it is determined whether the processing request to the server during the software update is to be processed by the new server in which the software is updated or the old server in which the software is not updated. The distribution part that distributes to the server
With
When the processing request is the first request in a series of processes requiring consistency, the distribution unit determines that the processing request should be processed by the new server, and distributes the processing request to the new server Update distribution device.   When the processing request is not a processing request that does not require session maintenance and is a request that can be discarded, the distribution unit determines that the processing request should be processed by a new server, and sends the request to the new server. The update distribution device according to claim 3, wherein distribution is performed. 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 processing requests to the server to any of the servers,
When the update management device is instructed to update the software, a server that updates the software used by the server in response to termination of the service provided by the server that is the target of the software update Administrative steps,
The update distribution apparatus processes a processing request to the server that is updating the software, either on a new server that has been updated based on the processing request, or on an old server that has not been updated. An update management method comprising a distribution step of determining whether to perform distribution to one of the servers. A server that updates the software used by the server in response to the termination of the service provided by the server that is the target of the software update when an instruction to update the software of the server having the N-Active configuration is given Administrative steps,
Have
In the server management step, an update management method for monitoring a load of the server, stopping service provision of a server whose load is equal to or less than a predetermined threshold, and updating software used by the stopped server. An update distribution method performed by an update distribution apparatus in a cluster system including an update management apparatus that updates software of a server having an N-Active configuration and an update distribution apparatus that distributes processing requests to the server to any of the servers There,
Based on the processing request, it is determined whether the processing request to the server during the software update is to be processed by the new server in which the software is updated or the old server in which the software is not updated. The distribution step to distribute to the server
Have
In the allocating step, when the processing request is the first request in a series of processes requiring consistency, the processing request is determined to be processed by the new server, and is distributed to the new server. Update distribution method.   The program for functioning a computer as an apparatus as described in any one of Claims 2-4.

Images