JP2013016041A - Distribution control device, distribution control method, and distribution control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent deterioration of the execution efficiency of a specific command.SOLUTION: A distribution control device retains processing states of a distributed server group for every predetermined time till a time when a specific command is issued by an administrative server. The distribution control device collects the processing states of the distributed server group for every predetermined time, compares the collected processing states with the retained processing states, and predicts an occurrence of a specific command. Later, when the occurrence of the specific command is predicted, the distribution control device inhibits the transmission of commands other than the specific command to any one of the distributed servers that constitute the distributed server group.

Description

  The present invention relates to a distribution control device, a distribution control method, and a distribution control program.

  2. Description of the Related Art Conventionally, there has been known a technique for executing processing distributed to a plurality of servers when processing to access a network device existing on a network. For example, there is known control for equalizing the entire load, such as assigning processes to a plurality of servers in order or assigning processes to the server with the fastest response.

  FIG. 19 is a diagram for explaining load distribution according to the prior art. As shown in FIG. 19, this system includes a management server 1, a command load balancer 2, a distributed server 5, a distributed server 6, an event load balancer 7, and a managed device.

  The management server 1 issues a management command to the network device to be managed via the command load balancer 2. The command load balancer 2 distributes the command issued from the management server 1 to the distributed server 5 or the distributed server 6 to distribute the load on the distributed server. The distributed server 5 or the distributed server 6 executes the command received from the command load balancer 2 on the network device to be managed, aggregates the events received from the event load balancer 7, and transmits the collected events to the management server 1.

  The event load balancer 7 distributes various events received from managed network devices to the distributed server 5 or the distributed server 6 to distribute the load on the distributed server. The managed network device is a network device such as a router, an L3 switch, a switching hub, or an L2 switch, and transmits an event such as a failure notification or log information to the management server 1.

  As described above, in the system according to the conventional technique, the command load balancer 2 distributes the load of the command issued from the management server 1, and the event load balancer 7 distributes the load of the event issued from the network device to be managed.

JP-A-62-175832 JP 2002-278776 A

  However, in the conventional technology, there is a case where an urgent emergency command cannot be executed urgently, and there is a problem that the execution efficiency of a specific command is deteriorated.

  For example, in conventional load balancing, as the number of processes increases, the overall load is controlled so that the overall load becomes high. Therefore, there is no choice but to allocate emergency commands to high-load servers. The command execution wait time becomes long and cannot be executed urgently. Although a method of separately preparing a server having a low constant load in the system is conceivable, it is not a preferable method because it costs for the server to be prepared.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a distribution control device, a distribution control method, and a distribution control program capable of preventing deterioration in execution efficiency of a specific command such as an emergency command. And

  In one aspect, a distribution control device, a distribution control method, and a distribution control program disclosed in the present application transmit a command issued from a management server device to any distributed server device forming a distributed server group. This is a distribution control device. The distribution control device includes a holding unit that holds the processing status of the distributed server group every predetermined time until a time when a specific command is issued by the management server device. The distribution control device compares the processing status collected by the collection unit and the processing status held in the holding unit with a collection unit that collects the processing status of the distributed server group every predetermined time, A prediction unit for predicting the occurrence of the specific command. The distribution control device suppresses transmission of a command other than the specific command to any one of the distributed server devices forming the distributed server group when occurrence of the specific command is predicted by the prediction unit. It has a control part.

  According to one aspect of the distribution control device, the distribution control method, and the distribution control program disclosed in the present application, it is possible to prevent the execution efficiency of a specific command from being deteriorated.

FIG. 1 is a diagram illustrating an example of the overall configuration of a system according to the first embodiment. FIG. 2 is a functional block diagram illustrating the configuration of the distribution control device according to the first embodiment. FIG. 3 is a diagram illustrating an example of information stored in the emergency command information table. FIG. 4 is a diagram illustrating an example of information stored in the statistical information table. FIG. 5 is a diagram illustrating an example of information stored in the pattern information table. FIG. 6 is a diagram illustrating an example of information stored in the emergency pattern information table. FIG. 7 is a diagram illustrating an example of information stored in the weighting information table. FIG. 8 is a diagram illustrating an example of information stored in the prediction result table. FIG. 9 is a diagram illustrating an example of information stored in the configuration information table. FIG. 10 is a diagram for explaining a comparative example of pattern information in the prediction process. FIG. 11 is a diagram illustrating weighting in the prediction process. FIG. 12 is a diagram illustrating an example of prediction determination. FIG. 13 is a flowchart illustrating a flow of processing at the time of command execution in the distribution control device according to the first embodiment. FIG. 14 is a flowchart illustrating the flow of the prediction process in the distribution control device according to the first embodiment. FIG. 15 is a functional block diagram illustrating the configuration of the distribution control device according to the second embodiment. FIG. 16 is a diagram illustrating an example of weight learning. FIG. 17 is a flowchart illustrating the flow of the learning process in the distribution control device according to the second embodiment. FIG. 18 is a diagram illustrating an example of a hardware configuration of a computer that executes a distribution control program. FIG. 19 is a diagram for explaining load distribution according to the prior art.

  Hereinafter, embodiments of a distribution control device, a distribution control method, and a distribution control program disclosed in the present application will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

[overall structure]
FIG. 1 is a diagram illustrating an example of the overall configuration of a system according to the first embodiment. As illustrated in FIG. 1, the system includes a management server 10, a distribution control device 20, a distributed server 50, a distributed server 60, an event load balancer 70, and a management target device. In the embodiment, an explanation will be given by taking an emergency command that is desired to be executed urgently as a specific command in preference to a normal command. Note that the present invention is not limited to the emergency command, and can be similarly applied to other commands designated by the administrator or the like.

  The management server 10 is a server device that issues a management command to the network device to be managed via the distribution control device 20. The distribution control device 20 is a load distribution device that distributes the command issued from the management server 10 to the distributed server 50 or the distributed server 60 to distribute the load of the distributed server. The distributed server 50 or the distributed server 60 executes the command received from the distribution control device 20 on the network device to be managed, and aggregates the events received from the event load balancer 70 and transmits them to the management server 10 It is.

  The event load balancer 70 is a load distribution device that distributes various events received from network devices to be managed to the distributed server 50 or the distributed server 60 and distributes the load of the distributed server. The managed network device is a network device such as a router, an L3 switch, a switching hub, or an L2 switch, and is a server device that transmits an event such as a failure notification or log information to the management server 10.

  In such a system, the distribution control device 20 holds the processing status of the distributed server group every predetermined time until the time when the emergency command is issued by the management server 10. Then, the distribution control device 20 collects the processing status of the distributed server group every predetermined time, compares the collected processing status with the held processing status, and predicts the occurrence of an emergency command. Thereafter, when the occurrence of an emergency command is predicted, the distribution control device 20 suppresses transmission of commands other than the emergency command to any of the distributed servers that form the distributed server group.

  For example, when it is predicted that the management server 10 issues an emergency command, the distribution control device 20 suppresses distribution to the distributed server 50 and an instruction to suppress distribution to the distributed server 50 as an event load. Send to balancer 70. Therefore, distribution to the distributed server 50 can be suppressed, and an increase in the load on the distributed server 50 can be suppressed. For this reason, even when an emergency command is issued from the management server 10, the distribution control device 20 can distribute to the distributed server 50 that is excluded from the distribution destination of the normal command. Can be prevented.

[Device configuration]
FIG. 2 is a functional block diagram illustrating the configuration of the distribution control device according to the first embodiment. As illustrated in FIG. 2, the distribution control device 20 includes a communication control I / F unit 21, a storage unit 22, and a processor 25.

  The communication control I / F unit 21 is an interface that controls communication with other communications. For example, the communication control I / F unit 21 receives a normal command and an emergency command from the management server 10. Note that an urgent command is a command that sets a route that, for example, identifies an excess traffic volume and bypasses part of the traffic when an alarm is detected from a managed device. It is a command. The normal command is a command other than an emergency command, such as a command for executing acquisition of route information or load information.

  Further, the communication control I / F unit 21 transmits a normal command and an emergency command to the distributed server 50 or the distributed server 60. The communication control I / F unit 21 receives event information and command execution results from the distributed server 50 or the distributed server 60. Similarly, the communication control I / F unit 21 transmits event information and command execution results to the management server 10. The event information is, for example, monitoring information monitored by SNMP (Simple Network Management Protocol), failure information detected by an SNMP trap, event log of a device to be managed, and the like.

  The storage unit 22 is a storage device such as a semiconductor memory element or a hard disk, and includes an emergency command information table 22a, a statistical information table 22b, and a pattern information table 22c. The storage unit 22 includes an emergency pattern information table 22d, a weighting information table 22e, a prediction result table 22f, and a configuration information table 22g.

  The emergency command information table 22a stores information related to emergency commands set by an administrator or the like. FIG. 3 is a diagram illustrating an example of information stored in the emergency command information table. As illustrated in FIG. 3, the emergency command information table 22a stores “command name, urgency e, application date and time” in association with each other. The “command name” stored here is the name of the emergency command. “Urgent level e” is an urgent level represented by, for example, 0 to 7, with 7 being the most urgent and 0 being the least urgent. “Applicable date / time zone” indicates a date / time zone treated as an emergency command.

  For example, in the case of FIG. 3, the command “ChangeRoute” having an urgency level of “7” indicates that it is recognized as an all-day emergency command. Also, the command “BlockTraffic” with an urgency level of “5” is recognized as an emergency command only if it was issued between 21:00 and 24:00, and commands issued in other time zones are normal commands. To be treated as

  The statistical information table 22b stores the number of commands issued to the distributed server, the number of specific events that match a predetermined condition among the number of events received from the distributed server, and the CPU (Central Processing Unit) load of each distributed server. . FIG. 4 is a diagram illustrating an example of information stored in the statistical information table. As shown in FIG. 4, the statistical information table 22 b includes “collection items (number of executed commands, number of executed commands, number of received specific events, average CPU load (A), average CPU load (B)), collection time, collection. "Value" is stored in association with each other.

  The “number of executed commands” stored here indicates the number of commands issued from the management server 10, in other words, the number of commands executed by the distributed server 50 or the distributed server 60. The “number of types of executed commands” indicates the number of types of commands issued from the management server 10, in other words, the number of types of commands executed by the distributed server 50 or the distributed server 60. The “specific event reception count” indicates the number of events that match a specific condition among events received from the distributed server 50 or the distributed server 60. “Average CPU load (A)” indicates the average value of the CPU load of the distributed server 50 during the collection time, and “Average CPU load (B)” indicates the average value of the CPU load of the distributed server 60 during the collection time.

  The “collection value” is a value collected for each collection item, and the “collection time” is the time when the collection value is collected. The number of execution commands and the number of execution command types are collected in the distribution control device 20, and the number of specific events, average CPU load (A), and average CPU load (B) are collected from the distributed servers. Further, the number of execution commands and the number of execution command types may include emergency commands in addition to normal commands.

  In the case of FIG. 4, for example, the distribution control device indicates that “10:06” indicates that five execution commands are executed by the distributed server and the number of types of executed commands is two. In the distribution control device, the number of specific events received at “10:06” is 400, the average CPU load of the distributed server 50 at “10:06” is 80%, and the average CPU load of the distributed server 60 is Was 80%. In FIG. 4, the collection time is in units of 1 minute, but is not limited to this and can be set arbitrarily. In the case of FIG. 4, the time when the emergency command prediction is started is “10:10”.

  The pattern information table 22c stores information indicating the tendency of each collection item from the information stored in the statistical information table 22b. FIG. 5 is a diagram illustrating an example of information stored in the pattern information table. As shown in FIG. 5, the pattern information table 22 c includes “collection items (number of executed commands, number of executed commands, number of received specific events, average CPU load (A), average CPU load (B)), collection time, trend "Is stored in association with each other. The “collected items (number of executed commands, number of executed commands, number of received specific events, average CPU load (A), average CPU load (B)), collection time” stored here is the same as in FIG. Omitted. “Trend” indicates the tendency of each collection item at the time as viewed from the whole.

  In the case of FIG. 5, for example, the “execution command number” collected at the collection time “10:08” is in an increasing tendency, the “execution command type number” is in a “maintenance tendency” without change, and the “specific event” The “number of receptions”, “average CPU load (A)”, and “average CPU load (B)” are “decreasing”.

  The emergency pattern information table 22d stores, for each emergency command, information indicating a change tendency before a certain time before the emergency command is executed. FIG. 6 is a diagram illustrating an example of information stored in the emergency pattern information table. As shown in FIG. 6, the emergency pattern information table 22d includes “execution command name, collection item (execution command number, execution command type number, specific event reception number, average CPU load (A), average CPU load (B))”. , “Collection time, trend” ”in association with each other.

  The value of each collection item stored here is a value collected every certain time when the emergency command is executed. For example, in the case of FIG. 6, from “9:15” one minute before “ChangeRoute” is executed to “9:12” three minutes before, the number of execution commands tends to increase, and the number of execution command types tends to decrease. It shows that the number of specific events received, average CPU load (A), and average CPU load (B) tended to increase or decrease. The number of execution commands and the number of execution command types may include emergency commands. The collection time interval can be arbitrarily set, but is preferably the same as the collection time interval shown in FIGS.

  The weighting information table 22e stores weighting information for each emergency command. FIG. 7 is a diagram illustrating an example of information stored in the weighting information table. As shown in FIG. 7, the weighting information table 22e stores a weight for each collection item and a weight for the collection time. The “collection item” and “collection time” stored here have been described with reference to FIG. The “collection item weight” indicates a weight given to each collection item, and the “collection time weight” indicates a weight given to each collection time.

  In the case of FIG. 7, the time when emergency command prediction is started, in other words, the time “1” is 1 minute before the time when the statistical information is generated, and the weight “0.7” is 3 times before the time 2 minutes ago. It shows that weight “0.5” is given to the time before minutes. In addition, the weight “0.3” is given to the time 4 minutes before the time when the emergency command prediction is started, and the weight “0.2” is given to the time 5 minutes before. The collection item “execution command” has a weight “1”, “execution command type number” has a weight “0.5”, “specific event reception number” has a weight “1”, “average CPU load ( “A)” is given a weight “0.2”, and “average CPU load (B)” is given a weight “0.2”.

  The prediction result table 22f stores a result of predicting whether or not an emergency command is executed. FIG. 8 is a diagram illustrating an example of information stored in the prediction result table. As illustrated in FIG. 8, the prediction result table 22 f stores “execution command name, past determination times prediction result, prediction success rate” in association with each other. The “execution command name” stored here is information indicating the emergency command to be predicted. “Past determination times prediction result” is information indicating a predetermined number of past prediction determination results. For example, when prediction is successful, that is, when an emergency command is issued as predicted, “◯” is stored, and when prediction fails, that is, when an emergency command is not issued, “×” is stored. The “prediction success rate” is the prediction success rate calculated from the past judgment round prediction result.

  For example, in the case of FIG. 8, the emergency command “ChangeRoute” indicates that the predicted success rate is 1 because all of the predicted past five times have been successful. Further, regarding the emergency command (Shutdown), four of the predicted five times have succeeded, and thus the prediction success rate is 4/5 = 0.8.

  The configuration information table 22g stores configuration information of each device forming the system shown in FIG. FIG. 9 is a diagram illustrating an example of information stored in the configuration information table. As illustrated in FIG. 9, the configuration information table 22g stores “server name, IP, role, allocation possibility” in association with each other.

  The “server name” stored here indicates the name of the device such as a host name, “IP” indicates the IP (Internet Protocol) address of the server, and “role” indicates the role in the system executed by the device. “Distribution availability” indicates whether load distribution is possible. For example, the server name “MNG” indicates a management server to which IP (A) is assigned and is not subject to load distribution. “DSP1” is a load distribution target to which IP (B) is assigned, and indicates a distribution server 50 capable of load distribution.

  Similarly, “DSP2” indicates a distributed server 60 to which IP (C) is assigned and which is a load distribution target and capable of load distribution. “ELB” indicates an event load balancer 70 to which IP (D) is assigned and is not subject to load distribution. “CED” indicates the distribution control device 20 to which IP (E) is assigned and is not subject to load distribution. In addition, when “O” is stored in “Allocation availability”, it indicates that allocation is possible, and when “−” is stored in “Allocation availability”, it indicates that the allocation is not permitted, When “x” is stored, it indicates that distribution is impossible.

  The processor 25 is an electronic circuit such as a CPU that controls the entire distribution control device 20, and includes an analysis unit 25a, a recording unit 25b, a prediction unit 25c, a load avoidance unit 25d, and a timer control unit 25e.

  The analysis unit 25a transfers the command received from the management server 10 to the load avoidance unit 25d, executes command analysis for determining whether the received command is an emergency command or a normal command, and sends the command information to the recording unit 25b. It is a processing unit that notifies.

  For example, when the analysis unit 25a receives a command from the management server 10, the analysis unit 25a compares the information stored in the header or the like of the command with the information stored in the emergency command information table 22a. It is determined whether or not. If the analysis unit 25a determines that the command is an emergency command, the analysis unit 25a adds an emergency command flag to the received command and transfers the command to the load avoidance unit 25d. If the analysis unit 25a determines that the command is a normal command, the analysis unit 25a transfers the received command to the load avoidance unit 25d and specifies the type of the received command and notifies the recording unit 25b.

  For example, when the received command includes an identifier for identifying “ChangeRoute” or the like, the analysis unit 25a determines that the command is an emergency command. The analysis unit 25a also includes an identifier for identifying “ConfigBackup” in the received command, and if the received time is between 0:00 and 6:00, the command is designated as an emergency command. judge. In addition, the analysis unit 25a determines that the received command includes an identifier for identifying “BlockTraffic” and the received command is a normal command when the reception time is not between 21:00 and 24:00. To do.

  The recording unit 25b stores a history of command information notified from the analysis unit 25a, collects statistical information from the distributed server, and generates pattern information. For example, the recording unit 25b sequentially stores command information notified from the analysis unit 25a in a work area or the like of the storage unit 22. Then, when the recording unit 25b receives the prediction start instruction from the timer control unit 25e, the recording unit 25b refers to the command information stored in the work area of the storage unit 22 and starts 5 minutes before the time when the prediction start instruction is received. The number of executed commands and the number of types of executed commands are generated. Further, the recording unit 25b receives the number of specific events together with the average CPU load from each distributed server. And the recording part 25b produces | generates the statistical information which matched these, and stores it in the statistical information table 22b. The distributed server collects the average CPU load and the number of specific events at predetermined intervals using monitoring software or the like, and the recording unit 25b acquires information collected by each of the distributed servers.

  After that, the recording unit 25b fits the collected values for 5 times of each collection item collected as statistical information using the second-order least square method, etc. Then, a change pattern indicating whether it is a maintenance tendency, an increase / decrease tendency, or a decrease / increase tendency is determined. In the example described above, the recording unit 25b generates pattern information in which the determination results are associated with each collection time from one minute to five minutes before, and stores the pattern information in the pattern information table 22c. Although an example using a quadratic function has been described here, a linear function may be used, in which case the determination result is either increased or decreased.

  The prediction unit 25c is activated by the timer control unit 25e, and compares information stored in the pattern information table 22c with information stored in the emergency pattern information table 22d. The prediction unit 25c is a processing unit that calculates the degree of similarity by adding a weight to the comparison result, evaluates the pattern prediction result, and predicts the occurrence of the emergency command.

  For example, the prediction unit 25c compares each emergency pattern information stored for each emergency command with the pattern information stored in the pattern information table 22c, and creates a scoring table that shows how much the information matches for each collection time. Generate. Subsequently, the prediction unit 25c generates a weighted scoring table in which the collection time stored in the weighting table 22e and the weight for each collection item are added to the generated scoring table. After that, the prediction unit 25c calculates the weighted similarity of each emergency command from the weighted scoring table calculated for each emergency command, and calculates a predicted evaluation value in which the predicted success rate is added to each calculated weighted similarity. . Then, the prediction unit 25c predicts that an emergency command can occur after the current time when there is an emergency command with a predicted evaluation value equal to or greater than a predetermined value.

  An example will be described with reference to FIGS. FIG. 10 is a diagram for explaining a comparative example of pattern information in the prediction process. FIG. 11 is a diagram illustrating weighting in the prediction process. FIG. 12 is a diagram illustrating an example of prediction determination. As illustrated in FIG. 10, the prediction unit 25 c compares the past pattern information of the emergency command “ChangeRoute” with the current pattern information, stores “1” in the matching time, and sets the mismatch time as Generates a scoring table storing “0”. Specifically, the prediction unit 25c determines that the number of execution commands two minutes before the time when the emergency command is executed is “increase / decrease” and the pattern information two minutes before the current time is “increase”. The scoring result 2 minutes before is set to “0”.

  Subsequently, as shown in FIG. 11, the predicting unit 25c performs weighted scoring by multiplying each of the collection time and the collection items of the scoring table generated by the processing of FIG. 10 by the weight stored in the weighting table 22e. Generate a table. Specifically, the prediction unit 25c sets the collection time weight “0.5” and the collection item weight to “1”, which is a scoring result of “−3” indicating the collection time 3 minutes before the current time. Multiply by “0.5” to calculate “0.25” as the weighted scoring result. And the prediction part 25c performs the multiplication of the weight mentioned above for every collection time of each collection item stored in a scoring table, produces | generates a weighted scoring result, and added the value of each weighted scoring result. Calculated as “weighted similarity”. In the case of FIG. 11, the prediction unit 25c calculates “6.15” as the “weighted similarity”. Note that the prediction unit 25c executes each process of FIG. 10 to FIG. 11 for each emergency command.

  After that, as shown in FIG. 12, the prediction unit 25c multiplies the weighted similarity calculated for each emergency command by the past prediction success rate stored in the prediction result table 22f, and calculates the prediction evaluation value. calculate. Specifically, the prediction unit 25c sets “6.1” to “6.15” because the prediction success rate of “ChangeRoute” calculated as the weighting similarity “6.15” is “1”. The multiplied “6.15” is calculated as the “predictive evaluation value” of “ChangeRoute”. Similarly, since the prediction success rate of “Shutdown” with the weighted similarity degree calculated as “2.12” is “0.8”, the prediction unit 25c sets “0.82” to “0.8”. "1.796" obtained by rounding "1.696" multiplied by "" is calculated as the "predicted evaluation value" of "Shutdown".

  Then, the predicting unit 25c predicts that an emergency command is generated if the maximum value of the “predicted evaluation value” calculated in this way is equal to or greater than a predetermined value such as “5”. In the case of FIG. 12, the prediction unit 25 c predicts that there is a high possibility that “ChangeRoute” will be issued. Then, when predicting the occurrence of the emergency command, the prediction unit 25c notifies the load avoidance unit 25d of a load avoidance instruction.

  Returning to FIG. 2, the load avoidance unit 25d is a processing unit that distributes the command transferred from the analysis unit 25a to a distributed server that can distribute the command. Further, when the prediction unit 25c notifies that the emergency command has been predicted, the load avoidance unit 25d determines a distributed server that suppresses distribution, and suppresses distribution to the determined distributed server. In addition, the load avoidance unit 25d notifies the event load balancer 70 of an instruction to suppress event distribution to the determined distributed server.

  For example, when the load avoidance unit 25d receives a command from the analysis unit 25a, the load avoidance unit 25d refers to the configuration information table 22g and transmits the command to any of the distributed servers whose distribution possibility is “◯”. The load avoidance unit 25d performs load avoidance when the prediction unit 25c is notified that an emergency command has been predicted and the distribution availability of each distributed server is “◯”. Note that the load avoiding unit 25d is notified that the emergency command has been predicted from the predicting unit 25c, and if the distribution availability of any of the distributed servers is “x”, the load avoiding unit 25d has already avoided the load, so that a new load Do not perform evasion.

  More specifically, the load avoidance unit 25d acquires the CPU load of each distributed server from each distributed server, and identifies the distributed server having the smallest CPU load as the load avoidance target server. Here, the distributed server 50 is a load avoidance target server. Then, the load avoidance unit 25d changes the distribution server 50 in the configuration information table 22g from “O” to “X” and changes the distribution server 50 while avoiding the load. In addition, the load avoidance unit 25d notifies the event load balancer 70 that the distribution to the distributed server 50 is to be suppressed. By doing so, the load avoidance unit 25d prevents a normal command from being issued to the distributed server 50 and also prevents the event load balancer 70 from distributing events to the distributed server 50.

  Command distribution in this state, that is, in a state where the distribution server 50 is “×” and the distribution server 60 is “O” will be described. For example, when receiving a normal command from the analysis unit 25a, the load avoidance unit 25d distributes the command to the distributed server 60 whose distribution availability is “◯”. In addition, when receiving an emergency command from the analysis unit 25a, the load avoidance unit 25d distributes the emergency command to the distributed server 50 whose allocation possibility is “x”. In the above state, for example, after a certain period of time such as 1 minute has elapsed, the load avoidance unit 25d changes the distribution server 50 distribution permission / inhibition to “O”, cancels the distribution server 50 distribution inhibition, and performs both distributions. Enable distribution to the server.

  Note that the load avoidance unit 25d determines whether or not the command received from the analysis unit 25a is an emergency command based on whether or not an emergency command flag is added to the command. That is, the load avoidance unit 25d determines that the command is an emergency command when the emergency command flag is added to the command.

  The timer control unit 25e is a processing unit that periodically starts the prediction processing of the recording unit 25b and the prediction unit 25c. For example, the timer control unit 25e measures time and notifies the recording unit 25b and the prediction unit 25c that a predetermined time such as an interval of 5 minutes has been reached. By receiving this notification, the recording unit 25b and the prediction unit 25c start collecting statistical information and predicting.

[Process flow]
Next, processing executed by the distribution control apparatus according to the first embodiment will be described with reference to FIGS. 13 and 14. Here, an operation flow during command execution and an operation flow during prediction processing will be described.

(Operation flow during command execution)
FIG. 13 is a flowchart illustrating a flow of processing at the time of command execution in the distribution control device according to the first embodiment. As illustrated in FIG. 13, the analysis unit 25a of the distribution control device 20 refers to the emergency command information table 22a and determines whether or not the command received from the management server 10 is an emergency command (S101).

  If the analysis unit 25a determines that the command is an emergency command (Yes in S101), the analysis unit 25a sets an emergency command flag for the command (S102). On the other hand, when the analysis unit 25a determines that the command is not an emergency command (No in S101), the recording unit 25b records information on the command in the storage unit 22 or the like (S103).

  Thereafter, when the emergency command flag is set in the command transferred from the analysis unit 25a (Yes in S104), the load avoidance unit 25d refers to the configuration information table 22g to determine whether there is a distributed server that is avoiding the load. It is determined whether or not (S105).

  When it is determined that there is a distributed server that is avoiding the load (Yes in S105), the load avoiding unit 25d distributes the command determined as an emergency command to the distributed server that is avoiding the load (S106). On the other hand, when the load avoidance unit 25d determines that there is no distributed server under load avoidance (No in S105), the load avoidance unit 25d determines that one of the distributed servers identified using general load distribution processing is an emergency command. The commands are distributed (S107).

  Further, even when the emergency command flag is not set in the command transferred from the analysis unit 25a (No in S104), the load avoidance unit 25d refers to the configuration information table 22g and there is a distributed server that is avoiding the load. It is determined whether or not (S108).

  If the load avoidance unit 25d determines that there is a distributed server under load avoidance (Yes in S108), the load avoidance unit 25d distributes the command determined as a normal command to a distributed server other than the distributed server under load avoidance (S109). On the other hand, if the load avoidance unit 25d determines that there is no distributed server under load avoidance (No in S108), the load avoidance unit 25d determines that one of the distributed servers identified using general load distribution processing is a normal command. The commands are distributed (S107).

(Operation flow during prediction processing)
FIG. 14 is a flowchart illustrating the flow of the prediction process in the distribution control device according to the first embodiment. As shown in FIG. 14, the recording unit 25b of the distribution control device 20 is notified from the timer control unit 25e that the prediction trigger has been reached (Yes in S201). Then, the recording unit 25b generates statistical information in the statistical information table 22b, generates pattern information from the generated statistical information, and stores it in the pattern information table 22c (S202).

  Subsequently, the prediction unit 25c compares the pattern information generated by the recording unit 25b with each of the emergency pattern information stored in the emergency pattern information table 22d, and generates a scoring table for each emergency command (S203). ). Then, the prediction unit 25c performs weighting on the scoring table for each emergency command generated in S203 using the weighting information stored in the weighting information table 22e, and generates a weighted scoring table for each emergency command. (S204).

  Subsequently, the prediction unit 25c adds the items of the weighted scoring table for each generated emergency command, and calculates the weighted similarity for each emergency command (S205). Then, the prediction unit 25c multiplies each weighted similarity for each emergency command by the prediction success rate stored in the prediction result table 22f to calculate a prediction evaluation value for each emergency command (S206). ).

  Thereafter, when there is a predicted evaluation value equal to or greater than the predetermined value (Yes in S207), the load avoiding unit 25d refers to the configuration information table 22g and determines whether there is a distributed server that is avoiding the load (S208). Then, when there is no distributed server under load avoidance (No at S208), the load avoiding unit 25d acquires the CPU load from each distributed server and determines whether there is a distributed server with a CPU load less than a predetermined value. (S209).

  Then, when there is a distributed server having a CPU load less than the predetermined value (Yes in S209), the load avoiding unit 25d executes load avoidance to the distributed server having the smallest CPU load (S210). In other words, the load avoidance unit 25d changes the “distribution availability” of the distributed server with the smallest CPU load to “x” in the configuration information table 22g.

  Further, when there is no predicted evaluation value equal to or greater than the predetermined value (No at S207), when there is a distributed server that is avoiding load (Yes at S208), when there is no distributed server whose CPU load is less than the predetermined value (No at S209), The control device 20 ends the prediction process.

[Effects of Example 1]
The distribution control device 20 according to the first embodiment avoids the processing load of a specific distributed server to other distributed servers so that an emergency command can be executed even in a situation where the entire load is high, and the specific distributed server Can execute the command you want to execute immediately. In addition, since the distribution control device 20 according to the first embodiment does not prepare a special server for an emergency command, server resources can be effectively used and the cost for system construction can be reduced.

  In addition, when the distribution control device 20 generates the scoring table, it compares not only the processing load and the processing status itself, but also the processing load change and the processing status change. A likely situation can be detected. As a result, since the distribution control device 20 can predict the possibility of occurrence of an emergency command with a wide range, it can detect a situation where the number of occurrences of an emergency command is relatively small. Even if the possibility of occurrence is low, it can be detected without omission.

  In the second embodiment, an example in which a prediction result and a weight are learned based on whether or not the prediction described in the first embodiment is successful will be described. FIG. 15 is a functional block diagram illustrating the configuration of the distribution control device according to the second embodiment. As illustrated in FIG. 15, the distribution control device 20 includes a communication control I / F unit 21, a storage unit 22, and a processor 25. The communication control I / F unit 21, the storage unit 22, the analysis unit 25a, the recording unit 25b, the prediction unit 25c, the load avoidance unit 25d, and the timer control unit 25e of the processor 25 have the same functions as those in the first embodiment. Detailed description will be omitted.

[Device configuration]
Here, the learning unit 26 having a function different from that of the first embodiment will be described. The learning unit 26 updates the emergency pattern information table 22d based on the notification from the analysis unit 25a, determines the success or failure of the prediction determination notified from the prediction unit 25c, recalculates the prediction success rate, and determines whether the prediction determination is successful. Is a processing unit that optimizes various weights based on Here, each learning which the learning part 26 performs is demonstrated concretely.

(Update prediction judgment result)
The learning unit 26 receives, for example, a command type as command information of the emergency command from the analysis unit 25a. The learning unit 26 determines that the prediction is successful when the received command identification matches the emergency command stored in the emergency pattern information table 22d or the like, and determines that the prediction fails when it does not match. The learning unit 26 determines that the prediction has failed when the prediction is not received within a predetermined time such as one minute after the prediction is completed by the prediction unit 25c.

  When the learning unit 26 determines that the prediction is successful or the prediction failure, the learning unit 26 updates the prediction result table 22f with reference to the predicted time. Taking an example of updating from the state of the table shown in FIG. 8, when the learning unit 26 determines that the prediction is successful, it is assumed that the emergency commands actually executed are “ChangeRoute” and “ConfigBachup”. In this case, the learning unit 26 sets “−1, ○, ×, ×, ○” as new prediction results, and calculates the prediction success rate from the prediction results from four minutes before.

  Specifically, the learning unit 26 selects “−1, ChangeRoute: ○, BlockTraffic: ×, Shutdown: ×, ConfigBackup: ○”, “−2, ChangeRoute: ○, BlockTraffic: ○, Shutdown: ○, ConfigBackup: ×. Update to Similarly, the learning unit 26 sets “−3, ChangeRoute: ○, BlockTraffic: ○, Shutdown: ○, ConfigBackup: ×”, “−4, ChangeRoute: ○, BlockTraffic: ×, Shutdown: ○, ConfigBackup: ×”. Update. Similarly, the learning unit 26 updates “−5, ChangeRoute: ○, BlockTraffic: ○, Shutdown: ×, ConfigBackup: ×”.

  Then, the learning unit 26 calculates the rate of successful prediction for each emergency command. In the case of the above example, the learning unit 26 sets “prediction success rate” to “1” because “ChangeRoute” has been predicted successfully 5 times out of 5 times predicted. Similarly, the learning unit 26 sets the “prediction success rate” to “0.6” because “BlockTraffic” has been predicted only three times out of the five predicted times. Similarly, the learning unit 26 sets “success prediction rate” to “0.6” because “Shutdow” is predicted only three times out of five predicted times. Similarly, the learning unit 26 sets “prediction success rate” to “0.2” because “ConfigBackup” has been predicted only once out of 5 predicted times. If the learning unit 26 determines that the prediction has failed, “−1, ×, ×, ×, ×” is used as a new prediction result, and the prediction success rate is calculated from the prediction results up to four minutes before. To do. Then, the prediction unit 25c executes the subsequent emergency command prediction process using the prediction result table 22f updated by the learning unit 26.

(Emergency pattern update)
The learning unit 26 updates the emergency pattern information table 22d with reference to the time when the emergency command is newly executed. For example, when the emergency command is distributed to the distributed server at “11:03” by the load avoiding unit 25d or when the distributed server executes the emergency command at “11:03”, the learning unit 26 “11:03” The emergency pattern from “03” to 5 minutes before is generated.

  Specifically, the learning unit 26 determines the number of execution commands, the number of execution command types for each of “11:02”, “11:01”, “11:00”, “10:59”, and “10:58” The number of specific events received and each average CPU load are collected from information stored in the storage unit 22 by the recording unit 25b. Then, the learning unit 26 patterns the collected information using the same method as the recording unit 25b of the first embodiment, and updates the emergency pattern information table 22d. Thereafter, the prediction unit 25c executes the subsequent emergency command prediction process using the emergency pattern information table 22d updated by the learning unit 26.

(Weight update)
The learning unit 26 updates the information in the weighting table 22e based on the predicted success / failure of the emergency command. For example, the learning unit 26 acquires, from the prediction unit 25c, a scoring table for each emergency command generated by the prediction unit 25c during the prediction process. When the learning unit 26 determines that the prediction is successful, the learning unit 26 increases the weight of the most matched item among the collection time or the collected items in the scoring table, and sets the weight of the least matched item. Lighten.

  FIG. 16 is a diagram illustrating an example of weight learning. For example, it is assumed that the learning unit 26 determines that the prediction is successful in the state where the weight information is illustrated in the left diagram of FIG. Assume that the scoring table at that time is the right diagram of FIG. In this case, the learning unit 26 refers to the collection time in the right diagram of FIG. 10 and determines that the comparison results are the same because the collection times “−1” are all 1, and the collection time “−5” is the same. It is determined that the comparison result is not the same.

  Then, as illustrated in FIG. 16, the learning unit 26 increases the weight of the collection time “−1” by “0.1” and decreases the weight of the collection time “−5” by “0.1”. Although the example of updating the collection time weight has been described here, the collection item weight may be updated by a similar method.

[Process flow]
FIG. 17 is a flowchart illustrating the flow of the learning process in the distribution control device according to the second embodiment. As shown in FIG. 17, when the emergency command is executed, that is, when the analysis unit 25a receives the emergency command information (Yes in S301), the learning unit 26 regenerates the emergency pattern information table 22d (S302). . That is, the learning unit 26 generates new emergency pattern information based on the time when the emergency command is executed, and updates the emergency pattern information table 22d.

  When the executed emergency command is a command for which the scoring table is notified, in other words, the emergency command is a command described in the scoring table (Yes in S303), the learning unit 26 validates the scoring table. It is determined whether the time limit has passed (S304).

  When the expiration date of the scoring table has not elapsed (Yes at S304), the learning unit 26 updates the prediction result table 22f as a prediction success (S305), and updates the weighting information table 22e (S306). If the expiration date of the scoring table has passed (No at S304), the learning unit 26 updates the prediction result table 22f as a prediction failure (S307).

  In S303, when the executed emergency command is a command that is not described in the scoring table (No in S303), the learning unit 26 ends the process.

[Effects of Example 2]
As described above, the distribution control device 20 according to the second embodiment not only predicts an emergency command, but also predicts the prediction pattern 25c such as an emergency pattern, a weight, and a prediction determination result depending on whether the prediction succeeds or fails. Update the information used. As a result, the accuracy of the prediction process can be improved as needed, and a more accurate prediction process can be executed.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different forms other than the embodiments described above. Therefore, different embodiments will be described below.

(Processing status)
In the first and second embodiments, an example of collecting “execution command count, execution command type count, specific event reception count, average CPU load” as the processing status of the distributed server has been described. However, the processing status is limited to this. is not. For example, the memory usage rate may be collected as the processing status, and arbitrary information that can detect the processing load of the distributed server can be collected.

(Specify numerical values, etc.)
In the first and second embodiments, the collection time has been described by taking a unit of one minute as an example. In addition, the number of collection items, the type of emergency command, and the like can be arbitrarily set. In addition, items to be learned can be arbitrarily set. For example, learning can be performed in any number and in any combination, such as learning only the weights or learning only the weights and prediction results.

(Comparison with emergency pattern)
In the first embodiment, the example in which the pattern of statistical information at the time of avoiding prediction is compared with the pattern at the time of execution of a past emergency command has been described. However, the present invention is not limited to this. For example, the statistical information at the time of prediction avoidance is compared with the statistical information itself at the time of execution of the past emergency command, and the number of matches is searched. It can also be predicted that it will be executed.

(system)
In addition, among the processes described in the present embodiment, all or a part of the processes described as being automatically performed can be manually performed. Alternatively, all or part of the processing described as being performed manually can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of each device is not limited to that shown in the figure. In other words, all or a part thereof is configured to be functionally or physically distributed / integrated in arbitrary units, such as a configuration without the timer control unit 25e, for example, according to various loads and usage conditions. Can do. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

(Hardware configuration)
FIG. 18 is a diagram illustrating an example of a hardware configuration of a computer that executes a distribution control program. As illustrated in FIG. 18, the computer 100 includes a CPU 102, an input device 103, an output device 104, a communication interface 105, a medium reading device 106, an HDD (Hard Disk Drive) 107, and a RAM (Random Access Memory) 108. 18 are connected to each other by a bus 101.

  The input device 103 is a mouse or a keyboard, the output device 104 is a display or the like, and the communication interface 105 is an interface such as a NIC (Network Interface Card). The HDD 107 stores each information stored in each table shown in FIG. As an example of the recording medium, the HDD 107 is taken as an example. However, various programs are stored in other computer-readable recording media such as a ROM (Read Only Memory), a RAM, and a CD-ROM, and are read by the computer. Also good. Note that a storage medium may be arranged in a remote place, and the computer may acquire and use the program by accessing the storage medium. At that time, the acquired program may be stored in a recording medium of the computer itself and used. The CPU 102 executes each function shown in FIG.

  Further, the HDD 107 stores a distribution control program 107a for executing control of each processing unit shown in FIG. Then, the CPU 102 can operate the distribution control process 108a that executes each function described with reference to FIG. 2 and the like by reading the distribution control program 107a and expanding it in the RAM 108. That is, the distribution control process 108a performs the same functions as the analysis unit 25a, the recording unit 25b, the prediction unit 25c, the load avoidance unit 25d, the timer control unit 25e, and the learning unit 26 described in FIGS. As described above, the computer 100 operates as an information processing apparatus that executes the function of the distribution control apparatus by reading and executing the program.

  The computer 100 can also realize the same function as the above-described embodiment by reading the distribution control program 107a from the recording medium by the medium reader 106 and executing the read distribution control program 107a. . Note that the program referred to in the other embodiments is not limited to being executed by the computer 100. For example, the present invention can be similarly applied to a case where another computer or server executes the program or a case where these programs cooperate to execute the program.

DESCRIPTION OF SYMBOLS 10 Management server 20 Distribution control device 21 Communication control I / F part 22 Storage part 22a Emergency command information table 22b Statistical information table 22c Pattern information table 22d Emergency pattern information table 22e Weighting information table 22f Prediction result table 22g Configuration information table 25 Processor 25a Analysis unit 25b Recording unit 25c Prediction unit 25d Load avoidance unit 25e Timer control unit 26 Learning unit 50, 60 Distributed server 70 Event load balancer

Claims (10)

A distribution control device that transmits a command issued from a management server device to any distributed server device forming a distributed server group,
A holding unit for holding the processing status of the distributed server group every predetermined time until a time when a specific command is issued by the management server device;
A collection unit that collects the processing status of the distributed server group every predetermined time;
A prediction unit that predicts the occurrence of the specific command by comparing the processing status collected by the collection unit with the processing status held in the holding unit;
A deterrence control unit that suppresses transmission of a command other than the specific command to any of the distributed server devices forming the distributed server group when occurrence of the specific command is predicted by the prediction unit;
A distribution control device comprising: The holding unit holds a change in the processing status of the distributed server group during the predetermined time,
The collection unit detects and holds a change in the processing status collected for a predetermined time from the processing status collected from the distributed server group,
The prediction unit compares the change in the processing status held by the collection unit with the change in the processing status held in the holding unit, and predicts the occurrence of the specific command. 2. The distribution control device according to 1.   The predicting unit compares the processing status collected by the collecting unit with the processing status held in the holding unit, identifies a matching location, and the processing status has for the identified location The distribution control device according to claim 1, wherein an occurrence of the specific command is predicted based on an item or a weight set for each predetermined time and based on the result.   When the specific command predicted by the prediction unit is issued from the management server device within a predetermined time from the predicted time, the weight of the matching part is increased and the weight of the non-matching part is reduced. The distribution control device according to claim 3, further comprising: a learning unit that performs the learning.   The prediction unit compares the processing status collected by the collection unit with the processing status held in the holding unit, identifies a matching location, and considers the past prediction success rate for the identified location. The generation control device according to claim 1, wherein the occurrence of the specific command is predicted based on a result taken into account.   Based on whether the specific command predicted by the prediction unit has been issued from the management server device within a predetermined time from the predicted time, the past prediction success rate based on the predicted time The distribution control device according to claim 5, further comprising a learning unit that recalculates.   Based on whether the specific command predicted by the prediction unit is issued from the management server device within a predetermined time from the predicted time, the processing status of the distributed server group held in the holding unit is determined. The distribution control device according to claim 1, further comprising a learning unit to be updated.   The suppression control unit is determined to suppress transmission of a command other than the specific command to a load distribution device other than the distribution control device that distributes processing to any of the distributed server devices forming the distributed server group. The distribution control device according to claim 1, wherein an instruction to suppress distribution to the distributed server device is transmitted. A computer that transmits a command issued from the management server device to any of the distributed server devices forming the distributed server group,
Collect the processing status of the distributed server group every predetermined time,
Predict the occurrence of the specific command by comparing the collected processing status with the processing status of the distributed server group held every predetermined time until the time when the specific command is issued by the management server device And
When the occurrence of the specific command is predicted, the transmission of commands other than the specific command is suppressed with respect to any distributed server device forming the distributed server group.
A distribution control method characterized by executing processing. To any of the distributed server devices forming the distributed server group, to the computer that transmits the command issued from the management server device,
Collect the processing status of the distributed server group every predetermined time,
Predict the occurrence of the specific command by comparing the collected processing status with the processing status of the distributed server group held every predetermined time until the time when the specific command is issued by the management server device And
When the occurrence of the specific command is predicted, the transmission of commands other than the specific command is suppressed with respect to any distributed server device forming the distributed server group.
A distribution control program characterized by causing processing to be executed.

Images