JP2018049471A - Pseudo server control device, pseudo server control method, and pseudo server control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To surely and easily carry out planning for grasping a situation and improving a situation for maintaining service availability. A pseudo server control device includes a request transfer module that transfers a request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server. It is provided with a request storage module that temporarily stores the requests transferred to the pseudo system network and controls the transmission timing of the requests to the pseudo server according to the load status of the pseudo server. [Selection diagram] Fig. 1

Description

  The present invention mainly relates to a pseudo server control device, a pseudo server control method, and a pseudo server control program used in a web service system that provides web services.

  When providing a web service, maintenance of service availability (also called availability / ability to keep a system or the like usable) is an important mission for a service provider. In order to maintain the availability, for example, a system design that operates normally without being down even if the server is in a high load state due to centralized access of requests or the like is required. Usually, these system designs are thoroughly considered before the product is shipped (for example, at the design stage), and in many cases, problems do not occur.

  However, it may be found that an unexpected number of requests are concentrated on the server after the actual operation is started at the customer. When the load on the server exceeds a predetermined level, there is a possibility that the server may go down in the worst case.

  Therefore, from the viewpoint of service availability, the service provider needs to make a plan for grasping the situation and managing availability in advance even after the actual operation is started so that the above situation does not occur. .

  For example, in a production environment, which is an environment for actually providing web services to users, the production server itself that is actually operated in parallel while executing the original operation service aims to grasp the situation and solve the problem. A method for executing the planning of a new plan can be considered.

  In addition, for example, apart from the production environment that the web service actually provides to the user, a pseudo environment that can reproduce the request status equivalent to the production environment is created, and the performance tuning of the production environment can be maintained on this pseudo environment (the availability can be maintained) To change the system scale).

  Patent Document 1 describes a technique in which a request is temporarily stored in a queue and transmitted to a production server after waiting for a waiting time determined by the system.

  Japanese Patent Application Laid-Open No. 2004-228688 describes a technique for relieving a packet exchanged network by distributing the network load and transferring the packet, which normally had to be discarded, by another route.

  Patent Document 3 describes a processing request transfer apparatus that transmits a processing request (request) from a web server to a production server and registers the processing request in a processing queue. With this processing request transfer device, it is possible to transfer a request to a test server and to control the transfer interval of the request.

JP 2004-348491 A Japanese Patent Laid-Open No. 2003-077855 Japanese Patent Laying-Open No. 2015-10951

  However, in recent years, the scale of web service systems (especially the number of clients and servers in the production environment accompanying an increase in the number of web usages) has become significant. Therefore, in the case of a method that grasps the situation and plans in parallel with the original service in the production environment, the load of the availability handling process itself increases the load of the entire production server. There is also a risk that the processing capacity is reduced.

  On the other hand, in the case of a configuration that performs performance tuning of the production environment on the simulated environment, the production environment is fatefully reproduced, and as the scale of the production environment increases, the cost of the simulated environment and the complexity of the device configuration inevitably increase. Concerned.

  The techniques of Patent Document 1 and Patent Document 2 are techniques for preventing data (especially requests) from being missed on the production server, and for the purpose of grasping the situation to maintain service availability and making plans for improving the situation. Is not a technology.

  Further, the processing request transfer apparatus of Patent Document 3 is arranged between a web server and an application server that actually performs processing. Therefore, a request for static content whose processing is completed only by the web server is not a target. That is, since the technique of Patent Document 3 cannot grasp all requests that go through the entire system, it cannot reliably carry out planning for situation grasp or situation improvement.

  The present invention has been made to solve the above-described problem, and is a pseudo server control device capable of reliably and easily implementing a plan for situation grasp and situation improvement for maintaining service availability, An object is to provide a pseudo server control method and a pseudo server control program.

  The pseudo server control device of the present invention, the request transfer module for transferring the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server, A request storage module that temporarily stores the request transferred to the pseudo network and controls transmission timing of the request to the pseudo server according to a load state of the pseudo server.

  The pseudo server control method of the present invention transfers the request received from a device that generates a processing request to a production system network including at least a production server and a pseudo system network including at least a pseudo server, and the pseudo system network. The request transferred to the server is temporarily stored, and the transmission timing of the request to the pseudo server is controlled according to the load state of the pseudo server.

  The pseudo server control program of the present invention is a request transfer process for transferring the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server; Temporarily storing the request transferred to the pseudo network and causing a computer to execute a request accumulation process for controlling a transmission timing of the request to the pseudo server according to a load state of the pseudo server. It is a program for.

  According to the present invention, it is possible to surely and easily implement a plan for grasping a situation for maintaining service availability and improving the situation.

It is a block diagram which shows the structural example of the pseudo | simulation server control apparatus of the 1st Embodiment of this invention. It is a flowchart for demonstrating the operation example of the pseudo | simulation server control apparatus shown in FIG. It is a block diagram which shows the structural example of the pseudo | simulation server control apparatus of the 2nd Embodiment of this invention. It is a block diagram which shows the structural example of the web service system containing the pseudo | simulation server control apparatus of the 3rd Embodiment of this invention. FIG. 5 is a block diagram illustrating a configuration example of a system including the request transfer module illustrated in FIG. 4 and peripheral modules. FIG. 5 is a block diagram illustrating a configuration example of a system of a pseudo network including the request accumulation module illustrated in FIG. 4. It is a data block diagram which shows the structural example of the request management table constructed | assembled in a request database. It is a flowchart for demonstrating the operation example of a request transfer module. It is a flowchart for demonstrating the 1st operation example (operation | movement until it stores a request in a request database) of a request storage module. It is a flowchart for demonstrating the 2nd operation example (operation | movement until it reads a request from a request database and it transfers to a pseudo | simulation server) of a request storage module.

[First Embodiment]
(Description of configuration)
FIG. 1 is a block diagram illustrating a configuration example of the pseudo server control apparatus 10 according to the first embodiment of this invention. The pseudo server control device 10 includes a request transfer module 12 and a request storage module 14. The request transfer module 12 transfers a request received from a device (for example, an end user device) that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server. Here, the production server is, for example, an actual operation server used in a production environment that a web service actually provides to a user. The request accumulation module 14 temporarily accumulates the request transferred to the pseudo network, and controls the transmission timing of the request to the pseudo server according to the load state of the pseudo server.
(Description of operation)
FIG. 2 is a flowchart for explaining an operation example of the pseudo server control apparatus 10 shown in FIG. The request transfer module 12 transfers the request received from the end user device to the production network including at least the production server and the pseudo network including at least the pseudo server (step S1). The request accumulation module 14 temporarily accumulates the requests transferred to the pseudo network, and according to the load state of the pseudo server, for example, the transmission timing of the request to the pseudo server so that the server does not enter a high load state. Is controlled (step S2).
(Explanation of effect)
In the first embodiment described above, a request from an end user device is transferred (mirrored) to the pseudo network by the request transfer module 12 and then temporarily stored in the request storage module 14. The accumulated requests are transmitted to the pseudo server by the request accumulation module 14 according to the load state of the pseudo server.

  According to the first embodiment, it is possible to reproduce a request situation equivalent to that of a production system network (particularly a production server) on a pseudo system network (particularly, a pseudo server). Therefore, it is possible to execute a plan for grasping the situation and improving the situation in order to maintain the service availability without affecting the processing load on the production network.

  Furthermore, in the case of the first embodiment, the request is temporarily stored in the request storage module 14, and the transmission timing can be adjusted so that the pseudo server does not enter a high load state. That is, according to the first embodiment, it is possible to construct a pseudo system network more simply and at a lower cost than a production system network including a load balancer and a large number of production servers.

Summarizing the above, according to the first embodiment, it is possible to reliably and easily carry out planning for grasping the situation and maintaining the situation for maintaining service availability.
[Second Embodiment]
FIG. 3 is a block diagram illustrating a configuration example of the pseudo server control device 30 according to the second embodiment of this invention. The pseudo server control device 30 includes a storage unit 32 and a control unit 34. The storage unit 32 is a computer-readable recording medium and stores the pseudo server control program 40. The pseudo server control program 40 is a program for causing the control unit 34 to execute the processing shown in FIG.

  According to the second embodiment described above, as in the first embodiment, it is possible to reliably and easily carry out a plan for grasping a situation for maintaining service availability and improving the situation. .

Examples of the control unit 34 include a CPU (Central Processing Unit) and a memory that stores instructions executed by the CPU. The computer-readable recording medium is, for example, a non-transitory storage device. Examples of non-temporary storage devices include a magneto-optical disk, a ROM (Read Only Memory), a portable medium such as a nonvolatile semiconductor memory, and a hard disk built in a computer system. The computer-readable recording medium may include a temporary storage device. As an example of a temporary storage device, for example, a communication line in the case of transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a volatile memory inside a computer system can be cited.
[Third Embodiment]
(Description of configuration)
FIG. 4 is a block diagram illustrating a configuration example of the web service system 100 including the pseudo server control device 150 according to the third embodiment of the present invention.

  The web service system 100 includes one or more end user devices 102-1 to 102-n (n is a natural number), a load balancer package 104, one or more production servers 106-1 to 106-n, and request accumulation. The module 108 and the pseudo server 110 are included.

  The end user devices 102-1 to 102-n transmit requests (processing requests) to the production servers 106-1 to 106-n in order to receive a desired web service.

  The production servers 106-1 to 106-n provide services corresponding to the requests received from the end user devices 102-1 to 102-n.

  The requests transmitted from the end user devices 102-1 to 102-n are once input to the load balancer package 104. The load balancer package 104 includes a load balancer module 120 and a request transfer module 122.

  The request transfer module 122 transfers the requests received from the end user devices 102-1 to 102-n to the production network including at least the production servers 106-1 to 106-n and the pseudo network including at least the pseudo server 110. Forward. Specifically, the request transfer module 122 transfers the request to the load balancer module 120, which is one of the elements constituting the production network, and forwards the request to the request storage module 108 that constitutes the pseudo network (this transfer). May be called mirroring).

  The load balancer module 120 transmits the received request while considering the load of the production servers 106-1 to 106-n to be distributed.

  The pseudo server control device 150 (shown by a one-dot chain line in FIG. 4) of the present embodiment includes a request transfer module 122 and a request storage module 108. The pseudo server control device 150 is an example of the pseudo server control device 10 of the first embodiment, and may be configured by a computer including a processor like the pseudo server control device 30 of the second embodiment.

  FIG. 5 is a block diagram illustrating a configuration example of a system including the request transfer module 122 illustrated in FIG. 4 and peripheral modules. The request transfer module 122 includes a request reception unit 200 (an example of a request reception unit) and a request transfer unit 202 (an example of a request transfer unit).

  The request reception unit 200 receives requests from the end user devices 102-1 to 102-n, and transfers the received requests to the load balancer module 120 (one of the elements constituting the production network). Further, the request reception unit 200 mirrors the received request to the request transfer unit 202 (one of the elements constituting the pseudo system network).

  The request transfer unit 202 transfers the request mirrored by the request reception unit 200 to the request storage module 108.

  Note that the request transfer module 122 may be disposed in the load balancer package 104 including at least the load balancer module 120.

  FIG. 6 is a block diagram showing a configuration example of a pseudo network system including the request accumulation module 108 shown in FIG. The request accumulation module 108 includes a request database 300, a request accumulation control unit 302 (request accumulation control unit), and a request transmission control unit 304 (request transmission control unit).

  The request database 300 temporarily holds the request transferred from the request transfer module 122. At least until the request is received from the request transfer module 122 and the request is transferred to the pseudo server 110, a request management table 330 for managing the transmission of the request is created in the request database 300. .

  FIG. 7 is a data configuration diagram showing a configuration example of the request management table 330 constructed in the request database 300. The request management table 330 includes at least one record information including the request itself and at least one field information for managing transmission of the request.

  The field information is data in the column direction (for example, Index, Method, Request, etc.) in FIG. In FIG. 7, the record information is data in the row direction (for example, a collection of field information and a request for Index = 1).

  In FIG. 7, Index is a number assigned to identify record information, and is normally assigned in the order of reception of the requests included in the record information (that is, the record information including the request received earlier). The smaller the index, the smaller the value).

  Method is a method used when transferring data to a website (= web server, corresponding to the production servers 106-1 to 106-n in the present embodiment). Methods include, for example, a GET method and a POST method. Generally, a request is composed of a header part including a URL (Uniform Resource Locator) and a body part. The GET method is a method for adding user data such as form input after a URL. On the other hand, the POST method is a method for storing user data in the body part.

  Request is the request itself used in the present embodiment. Host is the name of a web server (for example, production servers 106-1 to 106-n). A cookie is a file (information) transmitted from a web browser (for example, the end user devices 102-1 to 102-n) when the website (for example, the production server 106-1 to 106-n) is accessed. ). For example, data specified by the website (web server) can be stored in the cookie. Content-Length indicates the length of data, for example, the length of data of record information, or the length of data of request.

  The request accumulation control unit 302 controls accumulation of requests in the request database 300, more specifically, writing to the request management table 330. The request accumulation control unit 302 rewrites the request destination information to the destination information of the pseudo server 110 when writing the request to the request management table 330.

  The request transmission control unit 304 controls the transmission timing of the request to the pseudo server 110 according to the load state of the pseudo server 110. In the present embodiment, as an example of control according to the load state, a case where the pseudo server 110 is controlled so as not to be in a high load state is taken as an example. For example, when the request transmission control unit 304 transmits a predetermined request, if the TAT (Turn Around Time) value of another request transmitted before the predetermined request is below a predetermined threshold, It is determined that the server 110 is not in a high load state, and a predetermined request is transmitted to the pseudo server 110.

  That is, the request transmission control unit 304 does not simply transmit the request of the request management table 330 but controls the number of request transmissions per unit time to the pseudo server 110 so that the pseudo server 110 does not become a high load. If necessary, delay sending the request.

This avoids missing requests. That is, the pseudo server 110 can receive the same number of requests as the production servers 106-1 to 106-n. This means that the same environment as that of the production servers 106-1 to 106-n is reproduced on the pseudo server 110.
(Description of operation)
Hereinafter, the operation of the pseudo server control apparatus 150 will be described. Note that the description of the operation of the device not directly related to the pseudo server control device 150 in FIG. 4 (for example, the operation of the load balancer module 120 and the production servers 106-1 to 106-n) will be omitted.

  FIG. 8 is a flowchart for explaining an operation example of the request transfer module 122. The request reception unit 200 of the request transfer module 122 receives requests from the end user devices 102-1 to 102-n, and transfers the received requests to the load balancer module 120 (step S10). Furthermore, the request reception unit 200 mirrors the received request to the request transfer unit 202 (step S11). The request transfer unit 202 of the request transfer module 122 transfers the request mirrored by the request reception unit 200 to the request accumulation module 108 (step S12).

  FIG. 9 is a flowchart for explaining a first operation example (operation until a request is stored in the request database 300) of the request accumulation module 108. The request accumulation control unit 302 of the request accumulation module 108 rewrites the destination information of the request transferred from the request transfer module 122 with the destination information of the pseudo server 110 (step S20). The destination information is, for example, the name of an FQDN (Fully Qualified Domain Name) or a host (for example, the production servers 106-1 to 106-n). The request accumulation control unit 302 registers this request in the request management table 330 (step S21).

  FIG. 10 is a flowchart for explaining a second operation example (operation until a request is read from the request database 300 and transferred to the pseudo server 110) of the request accumulation module 108.

  The request transmission control unit 304 of the request accumulation module 108 determines whether there is a request to be transmitted in the request management table 330 (step S30). When there is no request to be transmitted (No in step S30), the request transmission control unit 304 executes the process of step S30 again.

  When there is a request to be transmitted in the request management table 330, the request transmission control unit 304 determines whether or not the pseudo server 110 is in a high load state (step S31). Here, the high load state refers to, for example, a state in which a value of a certain physical quantity indicating a load exceeds a predetermined threshold value. For example, the request transmission control unit 304 can determine the load state of the pseudo server 110 based on the TAT (time) of another request transmitted before the request to be transmitted.

  When the pseudo server 110 is in a high load state (Yes in step S31), the request transmission control unit 304 does not transmit the request and executes the process of step S31 again. That is, in this case, the request is not waited until the pseudo server 110 is in a low load state and transmitted.

When the pseudo server 110 is in a low load state (No in Step S31), the request transmission control unit 304 extracts a request included in the record information with the smallest Index from the request management table 330 (Step S32). The request transmission control unit 304 transmits the extracted request to the pseudo server 110 (step S33).
(Explanation of effect)
In the third embodiment described above, requests from the end user devices 102-1 to 102-n are mirrored by the request transfer module 122 and then temporarily stored in the request storage module 108. The accumulated requests are transmitted to the pseudo server 110 by the request accumulation module 108 so that the pseudo server 110 does not enter a high load state.

  According to the third embodiment, it is possible to reproduce a request situation equivalent to that of the production network (particularly, the production servers 106-1 to 106-n) on the pseudo system network (particularly, the pseudo server 110). Therefore, it is possible to execute a plan for grasping the situation and improving the situation in order to maintain the service availability without affecting the processing load on the production network.

  Furthermore, in the case of the third embodiment, the request is temporarily stored in the request storage module 108 and the transmission timing is adjusted so that the pseudo server 110 does not enter a high load state. That is, according to the third embodiment, it is possible to construct a pseudo system network at a simpler and lower cost than a production system network including the load balancer module 120 and a large number of production servers 106-1 to 106-n. It becomes possible.

Summarizing the above, according to the third embodiment, it is possible to reliably and easily carry out planning for grasping the situation for maintaining service availability and improving the situation.
(Description of modification)
In the third embodiment described above, a plurality of request management tables 330 (see FIG. 7) can be provided (for example, another one is added). Thereby, a plurality of pseudo servers 110 can be created.

  When a request is registered in the added request management table 330, for example, a rule that stores only a specific request may be provided. Thus, in addition to the normal pseudo server 110, another pseudo server 110 in which only a specific request is concentrated can be added. This is extremely useful for survey analysis and the like when the current production environment is scaled out (addition of production servers 106-1 to 106-n).

  Further, in the third embodiment described above, the pseudo server control device 150 and the pseudo server 110 can be connected by a dedicated line to ensure secure communication. This makes it possible to build production environment information that is not allowed to be leaked in a closed in-house network on the service operator side.

  Furthermore, in the third embodiment described above, the request accumulation control unit 302 can analyze the request method and add processing corresponding to the method to each of the GET request and the POST request. For example, processing such as “no response is received from the pseudo server 110 for a GET request” or “a response is picked up for a POST request and a processing branch according to an http response is provided” can be added. As a result, the pseudo server control device 150 can arbitrarily control the state of the pseudo server 110.

  Further, in the third embodiment described above, for example, as in the second embodiment, the operations shown in FIGS. 8 to 10 are described as a program and stored in a computer-readable recording medium, and the program is stored in a CPU. It can also be set as the structure performed by arithmetic units, such as. If the operations shown in FIGS. 8 to 10 cannot be executed by a single computer, a plurality of computers may share these operations.

  As mentioned above, although this invention was demonstrated using each embodiment, the technical scope of this invention is not limited to description of said each embodiment. It is obvious to those skilled in the art that various modifications or improvements can be added to the above embodiments. Therefore, it is needless to say that embodiments with such changes or improvements are also included in the technical scope of the present invention. The numerical values and names of the components used in the embodiments described above are illustrative and can be changed as appropriate.

Moreover, a part or all of each embodiment mentioned above can be described also as the following additional remarks.
(Appendix 1)
A request transfer module that transfers the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server;
A request storage module that temporarily stores the request transferred to the pseudo network and controls transmission timing of the request to the pseudo server according to a load state of the pseudo server;
A pseudo server control device comprising:
(Appendix 2)
The request accumulation module includes:
A request database that temporarily holds the request transferred from the request transfer module;
Request accumulation control means for controlling accumulation of the request in the request database;
The pseudo server control device according to claim 1, further comprising request transmission control means for controlling the transmission timing of the request.
(Appendix 3)
The request transmission control means, when a TAT (Turn Around Time) value of another request transmitted before transmitting the predetermined request is below a predetermined threshold, The pseudo server control device according to appendix 2, which is transmitted to a server.
(Appendix 4)
The request database is a table for managing the transmission of the request until at least the request is received from the request transfer module and the request is transferred to the pseudo server. And a request management table comprising at least one piece of request record information, and the pseudo server control device according to claim 2 or 3, characterized in that a request management table comprising at least one piece of request record information is constructed. .
(Appendix 5)
5. The pseudo server control device according to appendix 4, wherein the request accumulation control means rewrites the destination information of the request with the destination information of the pseudo server when the request is accumulated in the request management table.
(Appendix 6)
The request transfer module includes:
A request receiving means for receiving the request from the end user device, transferring the received request to the production network, and mirroring the pseudo network;
Request transfer means for transferring the request mirrored by the request reception means to the request storage module;
The pseudo server control device according to any one of appendix 1-5, including:
(Appendix 7)
The pseudo server control device according to appendix 6, wherein the request receiving means transfers the received request to a load balancer module that distributes a load to the production server.
(Appendix 8)
The pseudo server control device according to appendix 7, wherein the request transfer module is arranged in a load balancer package including at least the load balancer module.
(Appendix 9)
Transfer the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server,
The pseudo server control method, wherein the request transferred to the pseudo network is temporarily stored, and the transmission timing of the request to the pseudo server is controlled according to a load state of the pseudo server.
(Appendix 10)
The request transferred to the pseudo network is temporarily stored in a request database,
Control the accumulation of the request in the request database;
The pseudo server control method according to appendix 9, wherein the transmission timing of the request is controlled.
(Appendix 11)
A request transfer process for transferring the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server;
A request accumulation process for temporarily accumulating the request transferred to the pseudo network and controlling a transmission timing of the request to the pseudo server according to a load state of the pseudo server;
A pseudo server control program for causing a computer to execute.
(Appendix 12)
The request accumulation process includes:
A holding process for temporarily holding the request transferred to the pseudo network in a request database;
A request accumulation control process for controlling accumulation of the request in the request database;
The pseudo server control program according to appendix 11, further comprising: a request transmission control process for controlling the transmission timing of the request.

DESCRIPTION OF SYMBOLS 10 Pseudo server control apparatus 12 Request transfer module 14 Request accumulation module 30 Pseudo server control apparatus 32 Memory | storage part 34 Control part 40 Pseudo server control program 100 Web service system 102-1 to 102-n End user apparatus 104 Load balancer package 106-1 106-n Production server 108 Request accumulation module 110 Pseudo server 120 Load balancer module 122 Request transfer module 150 Pseudo server control device 200 Request reception unit 202 Request transfer unit 300 Request database 302 Request accumulation control unit 304 Request transmission control unit 330 Request management table

Claims (10)

A request transfer module that transfers the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server;
A request storage module that temporarily stores the request transferred to the pseudo network and controls transmission timing of the request to the pseudo server according to a load state of the pseudo server;
A pseudo server control device comprising: The request accumulation module includes:
A request database that temporarily holds the request transferred from the request transfer module;
Request accumulation control means for controlling accumulation of the request in the request database;
The pseudo server control device according to claim 1, further comprising request transmission control means for controlling the transmission timing of the request.   The request transmission control means, when a TAT (Turn Around Time) value of another request transmitted before transmitting the predetermined request is below a predetermined threshold, The pseudo server control apparatus according to claim 2, wherein the pseudo server control apparatus transmits to a server.   The request database is a table for managing the transmission of the request until at least the request is received from the request transfer module and the request is transferred to the pseudo server. 4. The pseudo server control according to claim 2 or 3, wherein a request management table comprising at least one request record information is constructed, comprising at least one field information for managing transmission of the request. apparatus.   5. The pseudo server control apparatus according to claim 4, wherein the request accumulation control means rewrites the request destination information to the pseudo server destination information when the request is accumulated in the request management table. The request transfer module includes:
A request receiving means for receiving the request from the end user device, transferring the received request to the production network, and mirroring the pseudo network;
Request transfer means for transferring the request mirrored by the request reception means to the request storage module;
The pseudo server control apparatus according to claim 1, wherein the pseudo server control apparatus includes:   The pseudo server control apparatus according to claim 6, wherein the request reception unit transfers the received request to a load balancer module that performs load distribution to the production server.   The pseudo server control apparatus according to claim 7, wherein the request transfer module is arranged in a load balancer package including at least the load balancer module. Transfer the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server,
The pseudo server control method, wherein the request transferred to the pseudo network is temporarily stored, and the transmission timing of the request to the pseudo server is controlled according to a load state of the pseudo server. A request transfer process for transferring the request received from a device that generates a processing request to a production network including at least a production server and a pseudo network including at least a pseudo server;
A request accumulation process for temporarily accumulating the request transferred to the pseudo network and controlling a transmission timing of the request to the pseudo server according to a load state of the pseudo server;
A pseudo server control program for causing a computer to execute.

Images