JP3429559B2 - System version switching method and system version switching method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a multi-server system version switching method and a multi-server system version switching method, and more particularly to a system version switching method and system version number of a multi-server system in which distributed processing is performed by a plurality of processor modules. Regarding the switching method.

[0002]

2. Description of the Related Art In a system of a multiprocessor type computer, a plurality of processor modules (hereinafter referred to as PM) composed of a CPU and a memory are connected by a high-speed bus, and a plurality of servers for providing functions are connected to the PM server. Works on. In this way, the function provided to the user is divided into a plurality of servers, and the function of each server is
The system distributed and provided by M is a multi-server system.

Since such a system is often used for an online system such as a system for selling various tickets, it is necessary to perform maintenance work without stopping as much as possible. Therefore, even when the version number of the system is switched, control is performed so as to reflect the software (load module) absorbing the additional function and the failure correction in the system without stopping the function of the entire system.

The switching of the system version number is performed for each PM. Therefore, when switching the version number of a PM, the server that exists in the PM and provides the service is moved to another PM so that the service is not stopped, and then the version number of the PM system is switched. . The operation is executed for all PMs.

FIG. 6 is a diagram showing the transition status of the server when the system version number is switched by the conventional method. In this example, for the sake of simplicity, a multi-server system having five PMs provides services, and the transition status of one application and one server operating in this multi-server system will be described. Actually, there are tens to hundreds of servers (not shown), which are distributed to and processed by each PM.

Step 21 shows a state before the system version switching process is started. Each PM has an operating environment set to either active, standby, or standby. PM
1 is a working β, and PM2 is a working α, which provides application services. Application 30
It is operating on PM1. PM3 is a standby PM, and is ready to start providing services immediately when the active PM stops. The server 23 operates on PM3. PM4 and PM5 are spare PMs. The spare PM is changed to a working PM or a standby PM as needed. yet,
All PMs are running on older systems.

Here, the application and the server are restricted by the following conditions. First, the application is always operating on the system of the active PM, and when the active PM stops, the standby PM is changed to the active PM, and then the application becomes the newly active PM.
Switched to work on M. The server can be moved to any PM, but after switching the version number of the PM, it is returned to the environment set for the original PM in order to balance the performance. That is, the server operating in the standby PM is returned to the standby PM after switching the version number of the PM.

Under such conditions, when switching the PM1 system to the new version, the PM1 must be stopped. Therefore, the application 30 operating on the PM1 is moved to another PM.

Step 22 shows the state of the PM1 after system switching. Here, PM1 has been switched to the new version, and other PM2, PM3, PM4, and P
M5 is an old version system. Since PM1 is once stopped, it becomes a backup, and instead, PM3 is currently in use β, and the application 30 is operating on this PM3. Further, since the PM 3 is currently in use, the PM 4 is in the standby PM, and the server 23 is moved onto this PM 4. At this time, the server 23 is operating in the old version system.

Next, when the PM4 system is switched, the server 23 needs to move to another PM. The order of switching the system is arbitrary, and the order may be switched in any order.

Step 23 shows the situation after the server 23a has been moved for switching the PM4 system. The server 23a has been moved to PM1 and is running on the new version of the system. At this time, PM1 is a spare PM, P
M2 is active PM, PM3 is active PM, PM4 is standby P
M and PM5 are spare PMs.

After the PM4 system is switched, the server 23 must return to the standby PM, which is the environment in which it was operating before the movement. Step 24
Shows the status of the server 23 after switching the PM4 system. The system of PM4 has been switched to the new version, the server 23 has moved to PM5, and is running on the system of the old version. At this time, PM1 is a spare P
M and PM2 are active PM, PM3 is active PM, PM4 is standby PM, and PM5 is standby PM.

By switching all PM systems while moving the server in this way, the version number of the entire multi-server system can be switched. As such an example, the present applicant has filed Japanese Patent Application Laid-Open No. 4-24732.

[0014]

However, when switching the version number of a PM, the destination server of the server operating on the PM is arbitrary, so that the server operating on the old version of the system is a new version. After moving to another system, it may be reverted to an older system. In the above example, the server that was running on the old version system in step 22 is moved to the new version system in step 23, and the server is moved to step 24.
Has been reverted to the old version of the system.

When the server operates in the new version or the old version, the new function whose service has been started once the server operates in the new version stops when the server operates in the old version. In addition, the problem that is fixed in the new version of the system may occur again.

Further, when the version number of one PM is switched, the number of times the server moves is not limited to one, and there are cases where the server moves a plurality of times. Even in the above example, PM
The server has moved twice in order to switch the version number of 4.

As the server moves, the service is temporarily delayed. Therefore, if you move the server a lot,
The service is interrupted for a long time, and the processing speed of the entire system is reduced.

As described above, in the conventional method, since the order of PMs for which the system version number should be switched and the destination of moving the server are not determined, the version number of the system on which the server operates is chaotically fluctuated. There is a problem that the operation of is unstable and the number of times of switching the server is increased, so that the processing speed of the entire system is reduced.

The present invention has been made in view of the above points, and is a system in which the version number of a system in which a server operates does not return from a new version to an old version, and the number of server movements is kept to a necessary minimum number. The purpose is to provide a version number switching method.

Another object of the present invention is to prevent the version number of the system on which the server operates from returning from the new version to the old version,
Another object of the present invention is to provide a system version number switching method that keeps the number of server movements to the minimum necessary number.

[0021]

FIG. 1 is a principle diagram of a system version switching system of the present invention for achieving the above object. In the present invention, each processor module PM1, PM2, P
M3 is weighted, and the order determination means 1 for determining the order so that the system version is switched from the less important processor module, and the movement of the servers 21, 22, 23 existing in the processor module. Ahead
The migration destination determining means 2 for deciding to move to a processor module whose importance is one step lower, and the server existing in the processor module whose system version number should be switched when switching the system version number A server moving means 3 that moves to a destination determined by the determining means,
Version number switching means 4 for switching the version numbers of the system of the processor modules in the order determined by the order determining means.

In addition, weighting is applied to each processor module, and for all processor modules, the servers existing in the processor modules are moved in order from the processor module having a lower importance to the processor module having a lower importance one level. Then, a system version switching method is provided, which is characterized by switching the system version of the processor module.

[0023]

Operation: The order determining means 1 includes the processor modules P.
Weighting is applied to M1, PM2, and PM3, and the order is determined so that the system version is switched from the processor module having a low importance. The destination determining means 2 is the server 21 or 2 existing in the processor module.
The destinations of 2 and 23 are determined to be moved to the processor module whose importance is one step lower. Based on these determinations, the server moving unit 3 moves the server existing in the processor module whose system version should be switched to the destination determined by the destination determining unit 2 when switching the system version. To do. The version number switching means 4 switches the version number of the system of processor modules in the order determined by the order determining means 1.

In addition, weighting is applied to each processor module, and for all processor modules, the servers existing in the processor modules are moved in order from the processor module having a lower importance to the processor module having a lower importance one level. After that, switch the system version of the processor module.

As a result, the server can be implemented without moving from the new version system to the old version system, and the number of server moves can be minimized.

[0026]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a principle diagram of the system version switching method of the present invention. The order determining means 1 weights the processor modules PM1, PM2, and PM3, and determines the order such that the system version is switched from a processor module having a low importance. Destination determination means 2
Are servers 21, 2 existing in the processor module
The destinations of 2 and 23 are determined to be moved to the processor module whose importance is one step lower. Based on these determinations, the server moving means 3 moves the server existing in the processor module whose system version number should be switched to the destination determined by the destination determining means 2 when switching the system version number. To do. The version number switching means 4 switches the version number of the system of processor modules in the order determined by the order determining means 1.

FIG. 2 is a block diagram showing a schematic configuration of the multi-server system of the present invention. Multiple PM1, PM
2 and PM3 have CPUs 111, 121 and 131 and memories 112, 122 and 132, respectively, and are connected to each other by a high-speed bus 40. The PM management mechanism 5 sets names to these PMs and creates a PM correspondence management table indicating the correspondence between the names and attributes. The attributes are
There are three types: active, standby, and standby. Order determination mechanism 1a
Determines the order of switching so that the attributes assigned to PMs are weighted in the order of active, standby, and standby, and the system version is switched from the PM with the lowest importance,
Create a switching order determination table. The server migration destination determining mechanism 2a moves the server existing in the active PM to the standby PM, the server existing in the standby PM to the standby PM, and the server existing in the standby PM to another standby PM. , The server move destination is determined, and the server move destination determination table is created.

The system version switching mechanism 4a should switch the system version from the server migration destination determining mechanism 2a.
After confirming M, a server move request is output to the server move mechanism 3a. The server moving mechanism 3a moves the server existing on the PM to the moving destination determined by the server moving destination determining mechanism 2a. The PM restart mechanism 4b restarts the PM after the PM to be switched is stopped and the system version switching mechanism 4a switches the system version number.

As a result, the server operating in the new version system will not return to the old version during the system version switching. In addition, the server can be moved a minimum number of times (when possible, one server can be switched only once).

The job execution control mechanism 6 stops, enters, and blocks various jobs (conversation session, batch job, application server, etc.) when the system version number is switched. The abnormality detection mechanism 7 detects an abnormal stop of the PM or the server. If an error is detected during system version switching, an error notification is sent to the system version switching mechanism 4
Notify a. The system version switching mechanism 4a cancels the system version switching work and outputs a job blockage recovery command to the job execution control mechanism 6. The job execution control mechanism 6 that has received the job block collection command releases the job block and the stop of the application server.

Thus, if any abnormality occurs when the version number of the system is switched, the blockage can be collected, and the abnormality can be recovered by operating the terminal device or by remote operation. As a cause of abnormality,
It is possible that there is a bug in the new version of the system.

FIG. 3 is a diagram showing an example of the switching order determination table. In this table, PM name, purpose, P of implementation
There are four items, M, and order. The order is determined to be the order of standby, standby, and working. In addition, PM
The PM management mechanism 5 manages the name, the purpose, and the installed PM, and the order determination mechanism 1a manages the order of switching the system version numbers for these PMs.

FIG. 4 is a diagram showing an example of the server move destination determination table. In this table, PM names (A, B, C,
D, E), application, mounting PM, and destination PM. The destination PM is determined such that the active PM is on standby, the standby PM is on standby, and the standby PM is on another standby. The server migration destination PM of each PM is managed by the server migration destination determining mechanism 2a.

Here, how the server transits will be described with reference to the switching order determination table shown in FIG. 3 and the server move destination determination table shown in FIG. FIG. 5 is a diagram showing the transition status of the server when the system version number is switched. In this example, for the sake of clarity, 5 PM
The transition status of two servers providing a service in a multi-server system having the above will be described. Actually, there are tens to hundreds of servers (not shown),
It is distributed to each PM and processed.

Step 11 shows the state before the system version switching process is started. Each PM has an operating environment set to either active, standby, or standby. PM
1 is a working β, PM2 is a spare, PM3 is a working α, PM4 is a standby, and PM5 is a spare. The server 21 is operating on PM1 and the server 22 is operating on PM4.

First, the spare PMs PM2 and PM5 are switched to the new version system in the order shown in the switching order determination table shown in FIG. Step 12 is P
The state after system switching of M2 and PM5 is shown. Here, PM2 and PM5 have been switched to the new version, and the other PM1, PM3, and PM4 remain in the old version of the system. Server 21 is running on PM1,
The server 22 is operating on PM4.

Next, the system of PM4, which is the standby PM, is switched. Step 13 shows the state after switching the system of PM4. The system of PM4 has been switched to the new version, the server 22a has been moved to PM2, and is running on the new system. At this time, PM2 is on standby, and PM1, PM3, and PM15 are not changed. The server 21 is operating on PM1.

Next, the system of PM1 which is the active PM is switched. Step 14 shows a state after switching the PM1 system. The system of PM1 has been switched to the new version, PM4 becomes active β, server 2
1a moves to PM4. At this time, PM2, PM
3 and PM5 are unchanged, the server 22a is PM2.
Is working on.

As described above, the system in which the server operates does not return from the new version to the old version. Therefore, the processing can be stably executed even when the system version number is switched. Also,
Since one server needs to be moved only once, it is possible to reduce the processing delay time associated with the server movement.

Further, when a trouble occurs during the system version switching, the system version switching work can be stopped, various jobs can be blocked and the application server can be released from the stop, so that the system version switching can be performed. Even if a failure occurs inside, the system can be restored.

[0041]

As described above, according to the present invention, each processor module is weighted, and the system is switched in order from the processor module with the lowest importance. By moving to a processor module that is one step lower, the version of the system on which the server operates does not return from the new version to the old version, and the number of server moves can be suppressed to the minimum necessary number. It is possible to secure the stability of the operation when switching the number and reduce the delay time of the processing due to the movement of the server.

[Brief description of drawings]

FIG. 1 is a principle diagram of a system version switching system of the present invention.

FIG. 2 is a block diagram showing a schematic configuration of a multi-server system of the present invention.

FIG. 3 is a diagram showing an example of a switching order determination table.

FIG. 4 is a diagram showing an example of a server move destination determination table.

FIG. 5 is a diagram showing a transition status of a server when a system version number is switched.

FIG. 6 is a diagram showing a transition state of servers when a system version is switched by a conventional method.

[Explanation of symbols]

1 Order determination means 2 Destination decision means 3 server transportation 4 Version switching means 21, 22, 23 servers PM1, PM2, PM3 Processor Module

Front page continuation (58) Fields surveyed (Int.Cl. ⁷ , DB name) G06F 15/177 G06F 11/00 G06F 9/455 G06F 13/00

Claims (4)

(57) [Claims] 1. A system version number switching mode multiserver system for performing distributed processing by a plurality of processor modules, <br/> only performs weighting to determine the importance For each processor module, the version number of the system switch between, and order determining means to determine the order to be performed from the lower processor modules of the importance, the destination when moving the functions of the server that provides the processor module, the importance 1 stage moving destination determination means to decide to move to a lower processor module
And the server provided by the processor module that should switch the system version when switching the system version .
Server of the function, said the server moving means to move the moving destination determined by the destination determining unit, switching the version number to perform the version number of the switching system of the processor module in the given order in the order determination means system version number switching method characterized by having <br/> hand stage, the. Wherein said order determining hands stage, the weighting of each processor module, the order of importance, the active, standby,
The system version switching method according to claim 1, wherein the system version switching method is performed in three preliminary steps. 3. While switching the version number of the system,
2. The system version switching method according to claim 1, further comprising job execution control means for stopping the job and restarting the stopped job when an abnormality occurs. 4. In a system version switching method of a multi-server system in which a plurality of processor modules perform distributed processing, each processor module is weighted to determine its degree of importance , and all processor modules are weighted. In contrast, the professional
When the server function is operating in the sessor module
Checks the function of the server before switching the system version.
Moved to the processor module whose importance is one step lower
And, wherein in order from less important processor module, the flop <br/> ii processor module system version number switching method characterized by switching the version number of the system.