JP2781060B2 - Resource usage right issuance processing method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Summary] Regarding a resource use right issuance processing method for issuing a resource use right to a FTized processing server, a method for issuing a resource use right from a standby processing server is described. The resource management server that issues the resource use right determines that the resource acquisition request message sent from the processing server has been resent. A registration mechanism for registering the right to use the resource to be issued, an adding mechanism for adding the identifier of the message from which the request for issuance of the right was issued, and an additional mechanism for determining that the message is a retransmission message. A checking mechanism for determining whether or not the right to use the resource is already registered according to the message from which the retransmission message is based by referring to the identifier added by the checking mechanism. When it is determined that more usage rights registration, disable the rights for said use, configured to issue to the processing server to register the new license again.

[Industrial applications]

The present invention relates to a resource usage right issuance processing method for issuing a resource usage right to a FT (fault tolerant) processing server, and more particularly to a resource usage right issuance request from a standby processing server. The present invention relates to a resource use right issuance processing method capable of promptly issuing a resource use right to a user.

[Conventional technology]

In the case of employing a configuration in which data communication is performed by performing message communication between application programs, if there is no response to the transmitted message, it is determined that the application program to which the message has been transmitted has gone down. Therefore, in the related art, when data processing is performed based on message communication, a configuration is adopted in which, if there is no response to a transmitted message, the processing is abnormally terminated.

However, if the message destination is a global service program that runs in a unique space in the system and confine system resources in the space and controls the resources of the entire system, the provision of that service is suspended. In order to prevent this, a configuration is adopted in which an active system and a standby system are provided, and when the active system goes down, the processing is taken over by the standby system, thereby realizing FT. From now on, when the destination of the message is the global service program, the source of the message will not be down even if there is no response to the transmitted message. It is conceivable to adopt a configuration of retransmitting the message.

That is, as shown in FIG. 9, the resource management server 3 (3a) is prepared as a global service program.
Indicates that the active processing server 2a, which executes predetermined service processing using the resource usage rights acquired by the active system and 3b is the standby system, has crashed by the nuclear program 4 (which also processes server management). When it is detected, the control is passed to the processing server 2b prepared as the standby system, and the processing server 2b of the standby system becomes a new active system, and the processing of the processing server 2a which has been operating as the active system until then. Will be taken over. On the other hand, at this time, the nuclear program 4 sends the crashed processing server to the active resource management server 3a.
The resource management server 3a sends a request message for collecting the resource usage right issued to 2a, and upon receiving this request message, executes a purging process of the resource usage right. Then, the processing server 2b switched to the active system retransmits the message to the active resource management server 3a to execute the acquisition process of the resource use right in order to execute the takeover process. . Note that the client 1 in FIG. 9 is an application program for making a service request to the processing servers 2a and 2b.

FIG. 10 shows a flowchart of processing of the processing servers 2a, 2b, the resource management servers 3a, 3b, and the core program 4, which are executed for realizing the FT processing. Here, FIG. 10 (a) shows the processing of the active processing server 2a,
FIG. 10B is a flowchart of the processing of the active resource management server 3a executed in response to the request from the processing server 2a. FIG. FIG. 9 illustrates the processing of the standby processing server 2b executed when the is detected.

Here, as shown in FIG. 11, the active processing server 2a
Sends a resource use right issue request message to the active resource management server 3a, and the resource management server 3a executes a process of registering and issuing the resource use right in response to this request. Therefore, when the active processing server 2a crashes, the active resource management server 3a
In response to the request, the resource management server 3a is notified of the issued resource use right purge request, and the resource management server 3a executes a purging process of the registered corresponding resource use right according to the request.

[Problems to be solved by the invention]

However, due to the retransmission of such messages, the FT
When the conversion process is simply executed, the active processing server 2a
Crashes, a resource usage right purge request notification notified from the nuclear program 4 and a resource usage right issue request retransmission message notified from the standby processing server 2b that has taken over the processing are asynchronously transmitted. The active resource management server 3a becomes a standby processing server.
There is a problem that the resource use right cannot be issued promptly in response to the resource use right issuance request from 2b.

That is, when the resource use server purge request notification to the active resource management server 3a comes first, the resource management server 3a, as shown in FIG. Although there is no problem by executing the resource use right deletion process and registering and issuing the resource use right in response to the resource use right issuance request from the processing server 2b which is sent subsequently, the process is performed. If the resource use right issuance request is notified first from the standby processing server 2b that has taken over the process, as shown in FIG. 13, the processing server 2a that has been operating as the active system is Since the issued resource usage right has not yet been deleted, the resource usage right cannot be issued to the standby processing server 2b that has taken over the processing even though the active processing server 2a has crashed. Because there was a point That.

At this time, if a method of directly using the resource usage right that has not been deleted is adopted, as shown in FIG. 14, the resource usage right that has been used is deleted by the resource usage right purge request notification notified later. The inconvenience of being done will occur. Then, the resource use right purge request notification notified thereafter cannot be ignored as can be seen from the example shown in FIG. From now on, it is not possible to adopt a method of directly issuing the resource use right that has not been deleted to the standby processing server 2b that has taken over the processing.

In this way, if the processing server 2a, 2b prepared as a global service program and the resource management server 3a, 3b are configured to simply convert to FT according to the retransmission of the message, the processing server 2b of the standby system There is a problem that the resource use right cannot be issued promptly in response to the resource use right issuance request.

The present invention has been made in view of such circumstances,
It is an object of the present invention to provide a new resource use right issuance processing method capable of promptly issuing a resource use right in response to a resource use right issuance request from a standby processing server.

[Means for solving the problem]

 FIG. 1 is a diagram illustrating the principle of the present invention.

In the figure, 1 is a client, which requests a service, 2a is a processing server that operates as an active system,
A service server 2b that provides a predetermined service process to the client 1, 2b is a processing server prepared as a standby system, and takes over the process when the processing server 2a crashes. The resource management server 3a, which provides a predetermined service process, operates as the active system, acquires the right to use the resource in response to a request from the active processing server 2a, and issues it to the processing server 2a. The resource management server 3b is provided as a standby system. The resource management server 3a takes over the processing when the resource management server 3a crashes, and provides a service for issuing the right to use the resource to the processing server 2a. Numeral 4 is a nuclear program which executes monitoring / management processing of the processing servers 2a and 2b and the resource management servers 3a and 3b and manages registered resource use rights. Those with a use right management mechanism 40.

The resource management servers 3a and 3b of the present invention include a retransmission detection mechanism 30,
A registration issuing mechanism 31, an identifier adding mechanism 32, and an inspection mechanism 33 are provided. The retransmission detection mechanism 30 performs processing to determine whether or not the message is a retransmission according to the identifier of the resource acquisition request message transmitted from the active processing server 2a. Acquires a resource use right in response to a resource acquisition request message sent from the server 2a, registers the acquired resource use right in the resource use right management mechanism 40 and issues it to the processing server 2a, Then, the processing server 2a executes processing for deleting the registered resource use right in response to a request from the nuclear program 4, and the identifier adding mechanism 32 causes the registration issuing mechanism 31 to notify the resource use right management mechanism 40 of the resource use right. When registering the usage right, processing is performed so that the identifier of the message that has issued the resource usage right is added to the resource usage right. When it is determined that the resource use right has been already registered and issued according to the message that is the source of the retransmission message, by referring to the identifier managed by the resource use right management mechanism 40 Process.

[Action]

When the resource management server 3a of the present invention determines that the resource acquisition request message sent from the processing server 2a is not a retransmission according to the processing of the retransmission detection mechanism 30, the resource management server 3a according to the processing of the registration issuing mechanism 31 The usage right is acquired, and the acquired resource usage right is used by the resource usage right management mechanism 40.
And is issued to the processing server 2a.
At the time of this registration processing, the resource management server 3a performs processing to add the identifier of the message that has been issued to the resource usage right to be registered, according to the processing of the identifier addition mechanism 32.

When the resource management server 3a determines that the resource acquisition request message sent from the processing server 2a is retransmission, the resource use right is already registered in accordance with the message from which the retransmission message is based, according to the processing of the inspection mechanism 33.・
Determine whether it has been issued. When the resource management server 3a determines that the resource use right has already been registered and issued by this determination processing, the resource management server 3a first invalidates the resource use right according to the processing of the registration and issuance mechanism 31, and then, The new resource use right is registered again (the message identifier is also added) and issued to the processing server 2b. On the other hand, when it is determined that the resource usage right has not been registered / issued yet, the resource management server 3a itself has crashed and could not be registered, or the resource usage right purge request notification has been issued because the processing server 2a has crashed. Since it has arrived first, the resource management server 3a registers the resource use right again (adds the message identifier) and issues it to the processing server 2b according to the processing of the registration issuing mechanism 31.

In accordance with this processing, as shown in FIG. 2, the processing is succeeded to the resource management server 3a prior to the resource use right purge request notification which is notified by the crash of the active processing server 2a. Even if a request for issuing a resource use right is notified from the standby processing server 2b,
This makes it possible to quickly issue a resource use right to the standby processing server 2b.

〔Example〕

 Hereinafter, the present invention will be described in detail with reference to examples.

FIG. 3 shows an embodiment of the present invention. In the figure, reference numeral 1 denotes a client which issues a file open request request, 5a denotes a file name server operating as an active system, 5b denotes a file name server prepared as a standby system, and 6a operates as an active system. File management server, 6b
Is a file management server prepared as a standby system, and 4 is a nuclear program, which processes the operation monitoring of the file name servers 5a and 5b and the file management servers 6a and 6b, manages the active / standby status, and uses the right to use the file. Is to handle the management.

The file name servers 5a and 5b can issue a file open request to any one of the plurality of active file management servers 6a when a file open request is received from the client 1. In order to execute the process, a message to the file management server 6a, 6b is sent in order to execute a file open request message to the identified file management server 6a. In addition to having a communication mechanism, as shown in the figure, it is configured to have a file name management mechanism 50 for managing the correspondence between a file name and its location.

The file management servers 6a and 6b manage the files themselves and issue file usage rights while performing exclusive control in response to an open request message from the file name server 5a. As shown in the figure, in addition to a file access management mechanism 60 for executing a file access process, a retransmission message detection mechanism 61, a file use right registration and issue mechanism 62, an ID addition mechanism
63 and a processed inspection mechanism 64. The retransmission message detection mechanism 61 performs processing to determine whether or not the open request message is a retransmission according to the identifier attached to the transmitted open request message. The processing for executing the registration / issuance / deletion processing of the usage right is performed, and the ID addition mechanism 63 becomes a request source of the file usage right for the file usage right during the registration processing of the file usage right. Processing is performed so as to add a message identifier, and the already-processed checking mechanism 64 performs processing to determine whether or not the file use right has been issued and registered according to the message that is the source of the retransmission message.

FIG. 4 shows an embodiment of the identifier attached to the open request message. The identifier of this embodiment is a multiple request used multiple times for a file open request.
ID and a request counter indicating the order of the multiple request ID (which will be incremented by one when a new request is made). In accordance with a retransmission counter that indicates the number of retransmissions of an open request message (to be incremented by one at the time of retransmission), the number of retransmissions of the open request message is displayed. From this, when receiving a message in which the value of the retransmission counter increases, the retransmission message detection mechanism 61 performs processing to determine that the message is a retransmission message. In order to implement the takeover process of FT, it is necessary to write the identifier of the transmitted open request message in the nonvolatile memory, but if such a multiple request ID to be reused is used,
This can prevent the memory area from increasing.

FIG. 5 to FIG. 7 show an embodiment of processing executed to realize the present invention. 5 is a flowchart executed by the file name servers 5a and 5b, FIG. 6 is a flowchart executed by the nuclear program 4, and FIG. 7 is a flowchart executed by the file management servers 6a and 6b. Things. Next, the processing of the present invention will be described in detail with reference to these flowcharts.

As shown in the flowchart of FIG. 5A, the active file name server 5a receives a file open request request from the client 1 and refers to the file name management mechanism 50 to determine the file having the open request. Is specified, and an open request message is sent to the specified file management server 6a. At this time, if the file receiving server 6a of the message transmission destination has crashed, processing is performed so that the message is retransmitted. Then, a reply is received from the file management server 6a.

On the other hand, as shown in the flowchart of FIG.
When it receives the takeover instruction from the server, it determines whether there is a process in progress and, if there is a process in progress, sends an open request message to the corresponding file management server 6a. At this time, when the file management server 6a to which the message is to be sent has crashed, processing is performed to resend the message. Then, a reply is received from the file management server 6a.

As shown in the flowchart of FIG. 6A, the nuclear program 4 always checks whether or not the active file name server 5a has crashed. To take over. Then, as shown in the flowchart of FIG. 6 (b), when the crashed active file name server 5a has a file usage right, a purge request of the file usage right is issued to the file management server 6a. I will do it.

In this way, the open request message is resent from the file name servers 5a and 5b to the active file management server 6a, and the nuclear program 4 sends a file use right purge request notification. It will come.

When the file management server 6a receives the file use right purge request notification from the nuclear program 4, FIG. 7 (a)
As shown in (2), it is determined whether or not the file usage right to be purged is valid, and if it is valid, a process of deleting it is executed.

On the other hand, the file management server 6a is a file name server
When the open request message is received from 5a, 5b, the seventh
First, as shown in the flowchart of FIG.
By checking the value of the retransmission counter of the identifier attached to the message, it is checked whether the open request message is retransmission, and the request is sent to the standby file management server 6b to take over the processing. Keep a record of Next, when it is determined by the inspection process that the message is not a retransmission message, the file use right is registered in the memory area of the nuclear program 4 in association with the message identifier, and the file use right registered in the file name server 5a of the request source is registered. Issue rights.

On the other hand, when it is determined by this checking process that the message is a retransmission message, it is checked whether the file usage right has already been registered according to the open request message sent up to that time. ,
The file use right is registered in association with the message identifier and issued to the requesting file name server 5a. If the file usage right has been registered, the file usage right is deleted, the new file usage right is registered in association with the message identifier, and issued to the requesting file name server 5a.

According to this processing, as shown in FIG. 8, the file management server 6a of the present invention performs the processing before the purge request notification of the file usage right which is notified by the crash of the active file name server 5a. Even if a file usage right issuance request is notified from the standby file name server 5b that has succeeded the file system, the file usage right can be issued to the standby file name server 5b quickly. It is.

〔The invention's effect〕

As described above, according to the present invention, two processing servers for executing predetermined data processing while using resources acquired by the resource management server are prepared for the active system and the standby system, and When a processing server crashes, in a data processing device configured to respond to a service provision request by allowing the standby processing server to take over the processing, a request to issue a resource usage right from the standby processing server is received. Resource usage rights can be issued quickly.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention, FIG. 2 is an explanatory diagram of the processing of the present invention, FIG. 3 is an embodiment of the present invention, FIG. 4 is an embodiment of an identifier, FIG. FIG. 6 is an embodiment of the processing of the nuclear program, FIG. 7 is an embodiment of the processing of the file management server, FIG. 8 is an explanatory diagram of the processing of the embodiment, FIG. And FIG. 10 is an explanatory diagram of the FT process by resending a message, FIG. 11 is an explanatory diagram of the process of issuing a resource use right, and FIG. 12, FIG. 13, FIG. 14, and FIG. It is explanatory drawing of a problem. In the figure, 1 is a client, 2a and 2b are processing servers, 3a and 3b are resource management servers, 4 is a nuclear program, 5a and 5b are file name servers, 6a and 6b are file management servers,
Reference numeral 30 denotes a retransmission detection mechanism, 31 denotes a registration / issuing mechanism, 32 denotes an identifier adding mechanism, 33 denotes an inspection mechanism, and 40 denotes a resource use right management mechanism.

Claims (3)

(57) [Claims] 1. A processing server (2) for executing predetermined data processing while using resources acquired by a resource management server (3) is prepared for an active system and a standby system. When the processing server (2) crashes, the resource management server (3) is a data processing device that performs processing so as to respond to a service provision request by causing the processing server (2) in a standby system to take over the processing. A retransmission detection mechanism (30) for judging whether or not the message is a retransmission according to the identifier of the message of the resource acquisition request sent from the processing server (2), and registering the right to use the issued resource The identifier addition mechanism (32) for adding the identifier of the message that has issued the usage right to the usage right, and the retransmission detection mechanism (30) determine that the message is a retransmission message. When checking, by referring to the identifier added by the identifier adding mechanism (32), the checking mechanism (judges whether or not the right to use the resource has already been registered according to the message that is the source of the retransmission message) 33), when the checking mechanism (33) determines the registration of the right to use the resource, the right to use is invalidated, and then the right to use the new resource is registered again and the processing server ( 2) A resource use right issuance processing method characterized by processing to be issued. 2. The resource use right issuance processing method according to claim 1, wherein the identifier of the message transmitted from the processing server (2) to the resource management server (3) is a unique identifier and the retransmission of the message. A retransmission detection mechanism (30) configured to be identified in accordance with a retransmission number identifier indicating the number of times, wherein the retransmission detection mechanism (30) performs processing to determine whether or not retransmission is performed according to the retransmission number identifier. Issuance processing method. 3. The resource use right issuance processing method according to claim 2, wherein the unique identifier is a multiple identifier used multiple times in response to a request to acquire the same resource, and the number of times the multiple identifier is issued. A resource use right issuance processing method characterized by being configured to be unique in accordance with an issuance number identifier to be displayed.