WO2010100859A1 - 分散システム - Google Patents
分散システム Download PDFInfo
- Publication number
- WO2010100859A1 WO2010100859A1 PCT/JP2010/001196 JP2010001196W WO2010100859A1 WO 2010100859 A1 WO2010100859 A1 WO 2010100859A1 JP 2010001196 W JP2010001196 W JP 2010001196W WO 2010100859 A1 WO2010100859 A1 WO 2010100859A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- distributed
- client
- load distribution
- processing
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
Definitions
- the present invention relates to load distribution in an information processing system.
- the present invention relates to a technique for realizing processing load distribution in a distributed cluster environment.
- the present invention can also be applied to an online order system, a batch account management system, and the like in a financial institution.
- Patent Document 1 in order to solve the problem caused by starting up a load distribution server (RPC server) for all servers in advance, the load of the own node is stored using load storage means, and an overload is detected. In this case, it is described that a destination node capable of increasing a load is selected and a load movement instruction is moved to the destination node.
- RPC server load distribution server
- load distribution in a distributed cluster environment in which processing is performed using a plurality of nodes is generally a load distribution method for general-purpose business processing, or a load distribution method for distributed nodes having uniform processing capability.
- load distribution method that is conscious of a distributed cluster environment composed of a plurality of business processes with priorities and distributed nodes having non-uniform processing performance.
- the present invention selects a load distribution method that indicates how to distribute the load to each node according to the characteristics of each business process for each process in a distributed cluster environment in which a plurality of business processes are performed in the same system.
- the characteristics include the priority of the business process and the processing capability of the distributed node that executes the process.
- the present invention also includes adjusting the load according to a predetermined (stored) load threshold.
- a storage means for storing a load distribution method according to the characteristics of each client in each business, Means for detecting resource usage at each node; means for determining whether load distribution is required in any node as a result of the detection; and at a node determined to require load distribution as a result of the determination It is determined whether the business process is a business process for which client process, a load distribution method according to the determined business process characteristic is specified from the storage unit, and a load is determined according to the specified load distribution method. And means for performing distribution.
- the characteristics include at least one of the priority for each business process and the processing capability of each node.
- the storage system further includes second storage means for storing the resource usage status in each node, and third storage means for storing a threshold value of the resource usage status in each node, It is also included in the present invention that the determination means compares the contents stored in the second storage means and the third storage means.
- the distributed cluster environment, node load distribution method, and node load distribution that enable the maximum use of the resources of the distributed cluster environment by parallel execution
- the purpose is to provide a program.
- the present invention enables a technology that enables node selection processing that appropriately distributes processing according to business requirements for processing by defining load distribution conditions for each business.
- nodes with different performance are introduced at different times in a distributed cluster environment, it is possible to provide a uniform service without degrading the service level. .
- FIG. 1 shows a configuration diagram of the entire system in the present embodiment.
- the system according to the present embodiment includes each distributed node and each client, and is connected in a state where they can communicate with each other on the same network.
- the client has a function as an input terminal and a gateway function that aggregates information input from a plurality of input terminals and information transmitted from other systems and requests processing to distributed nodes.
- the distributed node has, as processing information acquisition means, a gateway function for acquiring a transmission request from a client and receiving a transmission request transmitted from a client from another distributed node.
- the gateway function in the distributed node and the client may be the same device or may be separated into different devices.
- the distributed nodes 100 and the clients are the same.
- the client 200 will be described as a representative example.
- the distributed node 100 includes a CPU 101, a memory 102, a storage medium 103, and a communication interface 110.
- an information processing program 104 having logic for performing a plurality of business processes, a resource threshold used in the distributed processing
- a resource monitoring program 106 that monitors resource usage at regular time intervals
- an in-memory database 107 that stores information processing results.
- the storage medium 103 may be realized by any medium that can store information, such as a hard disk and a memory.
- the resource threshold table 105 may be any target as long as it can be periodically monitored, such as the amount of information transmitted and received in the CPU, memory, and network. In this description, the CPU will be described below as a representative example.
- the values in the resource threshold table 105 are set by the user when the node is activated.
- the client 200 includes a CPU 201, a memory 202, a storage medium 203, and a communication interface 210.
- an information request program 204 for requesting information processing to an information processing program of a distributed node On the memory 202, an information request program 204 for requesting information processing to an information processing program of a distributed node, a client A node management table 206 that holds network information for all connectable distributed nodes, a processing time management table 207 that measures and holds the time required for information processing in each distributed node, and a distributed processing method (mode) for each job ) Is defined, and a mode content program 209 having the contents of each distributed processing mode exists.
- the storage medium 203 includes a master file 205 in which information to be given to the information request program 204 is recorded.
- information to be given to the information request program 204 may be transmitted through the communication interface 210 via a network.
- the storage medium 203 may be realized by any medium that can store information.
- the client 200 may have a configuration that forms a hierarchical structure in the client. For example, when another client 20a existing in the same network transmits information specifying a range to be processed to the client 200, the client 200 operates the information request program 204 based on this information. It may be operated as a relay function to the distributed node.
- FIG. 2 shows an example of the contents of the node management table 206.
- An entry in the node management table 206 includes a distributed node ID 2061 that is unique within the same network of each distributed node, a group ID 2062 that indicates grouping of the distributed nodes by the user, an IP address (including a port number) 2063, and processing among the startup times. It consists of an operation rate 2064 indicating the proportion of time that was present in the candidate node list, a flag 2065 indicating whether or not it is a transmission target in the distributed processing method, and a threshold correction coefficient 2066 used in the threshold adjustment method described later.
- the distributed node transmits its own information to all clients when it starts and ends, so that the client adds and deletes the entry of the distributed node in the node management table.
- the client uses the node management table 206 when determining the destination of the distributed node in the information request program.
- FIG. 3 shows an example of the contents of the time management table 207.
- Each client records the time from requesting processing to the distributed node until receiving notification of processing end.
- the processing time management table 207 includes a unique node ID 2071 for each distributed node, an average processing time 2072 so far, and 2073 indicating the number of updates from the start to the present.
- FIG. 4 shows an example of the contents in the two types of tables that the mode setting table 208 has.
- the business mode table 2081 records business processing 20811 performed by the client and a load distribution mode 20812 described later as a pair, and the time mode table 2082 sets the date and time 20821 when the processing is executed and the load distribution mode 20822 as a pair. It is what is recorded in.
- the information request program 204 of the client 200 interprets the text file 2083 at the time of startup.
- the contents are reflected in the business mode table 2081 and the date mode table 2082.
- the client 200 receives information indicating that the resource utilization rate threshold has been exceeded from the distributed node 100 when transmitting information for processing to the distributed node, the client 200 is set in the business using the mode setting table 208. Specify the load balancing mode.
- each client selects a distributed node to request processing from among each distributed node in the distributed processing
- the client 200 selects a distributed node to request processing using the round robin method while referring to the node management table 206, and selects the distributed node 100 for the selected distributed node 100 (in this example, the distributed node 100 using the round robin method).
- the distributed node 100 specifies the business from the transmitted information and transmits the information for processing. The process is executed using the corresponding logic.
- the unit of business processing that the client requests processing to the distributed node is, for example, in the case of securities business, by parallelization realized by the distributed cluster environment such as one account in batch processing for multiple accounts (for example, all accounts). In order to enjoy the effect of improving the calculation performance as much as possible, it is desirable to divide into units as fine as possible.
- the form according to the present invention is not necessarily limited to the unit of business processing.
- the resource monitoring program 106 executed by another thread in the distributed node 100 is executed at regular time intervals.
- the resource utilization rate exceeds the resource utilization rate threshold value set in the resource threshold value table 105 by the user in advance the fact that the distributed node 100 has exceeded the threshold value is recorded in the resource threshold value table 105 for each client.
- the threshold value that has been set is transmitted.
- the mode setting table 208 is referred to, and the load distribution mode set for the current job is set. , Has a mechanism to change the behavior.
- the first mode is the “normal mode”, and even when the client 200 receives from the distributed node 100 that the resource utilization rate threshold has been exceeded, the client 200 continues to determine a distributed node to request processing in a round-robin manner.
- the distributed nodes that are subject to round robin examination in the normal mode are the entries of the distributed nodes recorded in the node management table 206.
- the second mode is the “compliance mode”.
- the client 200 receives from the distributed node 100 that the resource utilization rate threshold has been exceeded, the client 200 sets the transmittable flag 2065 in the entry of the distributed node 100 in the node management table 206. Change from “OK” to “NG”.
- a distributed node that is subject to round-robin scrutiny in the compliance mode only targets entries for which the transmittable flag 2065 is “OK”.
- the distributed node once the transmission enable flag 2065 becomes “NG” information for processing is prevented from being transmitted from the client to which the compliance mode is applied unless it returns to “OK” again. Also good.
- the third mode is the “adjustment mode”, and when the client 200 receives from the distributed node 100 that the resource utilization rate threshold has been exceeded, the resource threshold that the distributed node 100 that has transmitted that the resource threshold has been exceeded has It is determined whether the contents of the table 105 provide the maximum efficiency in the current job. The contents of this determination will be described in the next paragraph.
- the distributed node that is the target of the round robin in the adjustment mode is an entry whose transmission enable flag 2065 is “OK” as in the compliance mode.
- Fig. 5 shows the contents of determination in the adjustment mode.
- the client 200 receives a message indicating that the threshold has been exceeded from the distributed node 100 (step 502)
- the client 200 refers to the mode setting table 208 and knows that the current process is the adjustment mode.
- request information for requesting processing is continuously transmitted to the distributed node 100 that has transmitted that the resource threshold has been exceeded (step 503).
- the time required for this process is compared with the processing time management table 207 that records the time required for the process in the state before receiving the message that the resource threshold has been exceeded (step 504).
- step 505 when the value of the processing time record table 207 is exceeded three times in succession (step 505), the distributed node 100 determines that normal business processing is impossible for exceeding the resource threshold, and the client 200 The transmission enable flag 2065 of the distributed node 100 in the management table 206 is changed from “OK” to “NG” (step 506). Further, even when the value of the processing time recording table 207 is not exceeded three times continuously in step 505, when the average of the processing times of five times exceeds the value of the processing time recording table 207 (step 507). ), And the process proceeds to Step 506.
- the number of times (3 times and 5 times) in steps 505 and 507 is an example, and other numbers may be used. These times are stored in advance in the system.
- step 507 when the average of the five processing times does not exceed the value of the processing time recording table 207, the normal business process is judged from the time required for processing even though the current threshold is exceeded.
- a command is transmitted from the client 200 to change the content from 70 to 72 after rounding.
- the distributed node 100 updates the value of the resource threshold table 105.
- the threshold value is raised step by step to a value at which it is determined that the business process is hindered (the time required for the process is delayed). However, if the correction value exceeds 100, the command is not transmitted (the command is transmitted when not exceeding).
- step 601 When the resource usage rate of the distributed node 100 exceeds the value of the resource threshold table 105 by monitoring (step 601), the fact that the threshold is exceeded and the threshold value are transmitted to each client (step 602). If the resource usage rate drops below a certain value in the resource threshold table 105 after step 602, the client is notified that the resource usage rate has dropped (step 603).
- the constant value may be defined for each distributed node. For example, when the value in the resource threshold value table 105 is less than 80%, step 603 may be applied.
- FIG. 7 shows the behavior of the client 200 due to the reception of the resource utilization rate decrease from the distributed node 100 (each client receives the resource threshold excess reception from the distributed node 100, but all clients have the same logic). Therefore, the case of the client 200 will be described here).
- the client 200 receives a notification that the resource utilization rate has decreased from the distributed node 100 (step 701)
- the node management table 206 of the client 200 is confirmed, and the transmission enable flag 2065 of the entry of the node 100 is “ NG "is checked (step 702).
- the transmittable flag 2065 of the distributed node 100 is “NG”, the resource utilization rate has been increased again in the node where the business processing has been hindered due to the excess of the resource utilization rate.
- step 704 if the node 100 does not exist in the excluded node list 2062, the processing is continued until the situation in step 701 comes.
- each client there is a possibility that all the entries in the node management table 206 become “NG” for the transmission enable flag 2065 due to the resource excess notification from each distributed node.
- the node list referred to by the round robin method is only “OK” in the transmittable flag 2065, from any distributed node in which the transmittable flag 2065 is “NG”.
- a request for a new process is sent to each distributed node (transmission of request information for requesting the process).
- the transmission of request information may be suppressed).
- the client enters a process waiting state.
- a node that requests information processing is selected from all entries in the node management table 206, so that no waiting state occurs.
- each client and each distributed node in a distributed cluster environment can cooperate to select any load distribution mode for each business. It becomes possible.
- the load balancing mode not only follows the specified threshold, but also tries to adjust the threshold set by the user autonomously within a range where the service level does not decrease due to the decrease in the time required for business processing. Provides a mode.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
前記各ノードにおけるリソースの利用状況を検知する手段と、前記検知の結果、いずれかのノードにおいて負荷分散が必要かを判断する手段と、前記判断の結果、負荷分散が必要と判断されたノードにおける業務処理が、いずれのクライアントの処理に対する業務処理かを判定し、判定された業務処理の特性に応じた負荷分散方式を前記記憶手段から特定する手段と、特定された前記負荷分散方式に従って、負荷分散を実行する手段とを有するものである。
モードの1つめは「通常モード」であり、クライアント200はリソース利用率閾値超過の旨を分散ノード100より受信した場合でも、引き続きラウンドロビン方式にて処理を依頼する分散ノードを決定する。通常モードにおけるラウンドロビンの精査対象となる分散ノードは、ノード管理テーブル206に記録されている分散ノードの各エントリが対象となる。
Claims (9)
- 分散配置された複数のノードと複数のクライアントが互いに接続された分散システムにおいて、
前記各クライアントにおける業務毎のその特性に応じた負荷分散方式が記憶される記憶手段と、
前記各ノードにおけるリソースの利用状況を検知する手段と、
前記検知の結果、いずれかのノードにおいて負荷分散が必要かを判断する手段と、
前記判断の結果、負荷分散が必要と判断されたノードにおける業務処理が、いずれのクライアントの処理に対する業務処理かを判定し、判定された業務処理の特性に応じた負荷分散方式を前記記憶手段から特定する手段と、
特定された前記負荷分散方式に従って、負荷分散を実行する手段とを有することを特徴とする分散システム。 - 請求項1に記載の分散システムにおいて、
前記特性には、前記業務処理毎の優先順位および前記各ノードの処理能力のうち少なくとも一方を含むことを特徴とする分散システム。 - 請求項1に記載の分散システムにおいて、
前記各ノードにおける前記リソース利用状況を記憶する第2の記憶手段と、
前記各ノードにおけるリソース利用状況の閾値を記憶する第3の記憶手段とを更に有し、
前記判定する手段は、前記第2の記憶手段と前記第3の記憶手段に記憶された内容を比較して判定することを特徴とする分散システム。 - 請求項1に記載の分散システムにおいて、
前記クライアントは、クライアントの中で階層構造を成し、同一ネットワークにおいて情報処理依頼の範囲を指定するクライアントと情報処理依頼をするクライアントに分かれ、前記分散ノードへの情報処理を実現することを特徴とする負荷分散システム。 - 請求項3に記載の分散システムにおいて、
前記第2の記憶手段は、前記リソース利用状況を示すリソースの利用率を格納したリソース利用率管理テーブルを有し、
前記第3の記憶手段は、前記リソース利用状況の閾値を示すリソース閾値テーブルを有し、
前記判定する手段は、予め定められた間隔にて前記リソース利用率管理テーブルを監視し、当該監視の結果前記リソース閾値テーブルの値を超過した場合及び前記リソース閾値テーブルの値の一定値未満へ低下した場合において、各クライアントに対しその旨を通知することを特徴とする分散システム。 - 請求項1に記載の分散システムにおいて、
前記各ノードに関するノード情報であって、更なる処理依頼の送信が可能かを示すフラグを含むノード情報を格納したノード情報テーブルを保持した第4の記憶手段と、
前記特定された負荷分散方式において前記フラグを利用し、処理依頼の送信対象の分散ノードの取捨選択を実行する手段とをさらに有することを特徴とする分散システム。 - 請求項6に記載の分散システムにおいて、
前記記憶手段に格納された前記負荷分散方式の1つに、前記処理依頼が送信されるノードリストのエントリを順に読み込み、送信先を選択する負荷分散方式が含まれることを特徴とする分散システム。 - 請求項6に記載の分散システムにおいて、
前記記憶手段に格納された前記負荷分散方式の1つに、当該分散システムにおいて、前記ノードからリソース閾値超過の旨を受信した場合、前記受信したノードのエントリを処理を除外する除外ノードへ変更することで、前記処理依頼の送信先から除外することを可能する負荷分散方式が含まれることを特徴とする分散システム。 - 請求項6に記載の分散システムにおいて、
前記記憶手段に格納された前記負荷分散方式の1つに、各ノードからリソース閾値超過の旨を受信した場合、当該分散ノードにおける処理時間を計測し、レスポンスタイムによる性能劣化が見られない場合に当該分散ノードのリソース利用率管理テーブルの値を上方修正する命令を送る負荷分散方式が含まれることを特徴とする分散システム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/203,106 US20120016994A1 (en) | 2009-03-03 | 2010-02-23 | Distributed system |
CN2010800076778A CN102317916A (zh) | 2009-03-03 | 2010-02-23 | 分散*** |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009-048724 | 2009-03-03 | ||
JP2009048724A JP2010204876A (ja) | 2009-03-03 | 2009-03-03 | 分散システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010100859A1 true WO2010100859A1 (ja) | 2010-09-10 |
Family
ID=42709429
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/001196 WO2010100859A1 (ja) | 2009-03-03 | 2010-02-23 | 分散システム |
Country Status (5)
Country | Link |
---|---|
US (1) | US20120016994A1 (ja) |
JP (1) | JP2010204876A (ja) |
CN (1) | CN102317916A (ja) |
TW (1) | TW201101186A (ja) |
WO (1) | WO2010100859A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103856512A (zh) * | 2012-11-30 | 2014-06-11 | 华为技术有限公司 | 云计算的管理服务器、工作和闲置主机以及资源调度方法 |
CN115633041A (zh) * | 2022-10-31 | 2023-01-20 | 中科星图数字地球合肥有限公司 | 多集群的管理方法、装置、电子设备和可读存储介质 |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7343413B2 (en) | 2000-03-21 | 2008-03-11 | F5 Networks, Inc. | Method and system for optimizing a network by independently scaling control segments and data flow |
US10721269B1 (en) | 2009-11-06 | 2020-07-21 | F5 Networks, Inc. | Methods and system for returning requests with javascript for clients before passing a request to a server |
US9141625B1 (en) | 2010-06-22 | 2015-09-22 | F5 Networks, Inc. | Methods for preserving flow state during virtual machine migration and devices thereof |
US10015286B1 (en) | 2010-06-23 | 2018-07-03 | F5 Networks, Inc. | System and method for proxying HTTP single sign on across network domains |
US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
EP2633667B1 (en) | 2010-10-29 | 2017-09-06 | F5 Networks, Inc | System and method for on the fly protocol conversion in obtaining policy enforcement information |
US10135831B2 (en) | 2011-01-28 | 2018-11-20 | F5 Networks, Inc. | System and method for combining an access control system with a traffic management system |
JP5572585B2 (ja) * | 2011-04-28 | 2014-08-13 | 株式会社日立製作所 | 携帯電話型暗号認証デバイスシステムおよびその方法 |
US9246819B1 (en) | 2011-06-20 | 2016-01-26 | F5 Networks, Inc. | System and method for performing message-based load balancing |
US8850020B2 (en) * | 2011-07-29 | 2014-09-30 | Cisco Technology, Inc. | Resource aware parallel process distribution on multi-node network devices |
US9270766B2 (en) | 2011-12-30 | 2016-02-23 | F5 Networks, Inc. | Methods for identifying network traffic characteristics to correlate and manage one or more subsequent flows and devices thereof |
US10230566B1 (en) | 2012-02-17 | 2019-03-12 | F5 Networks, Inc. | Methods for dynamically constructing a service principal name and devices thereof |
US9231879B1 (en) | 2012-02-20 | 2016-01-05 | F5 Networks, Inc. | Methods for policy-based network traffic queue management and devices thereof |
WO2013163648A2 (en) | 2012-04-27 | 2013-10-31 | F5 Networks, Inc. | Methods for optimizing service of content requests and devices thereof |
US9003086B1 (en) * | 2012-10-27 | 2015-04-07 | Twitter, Inc. | Dynamic distribution of replicated data |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US10187317B1 (en) | 2013-11-15 | 2019-01-22 | F5 Networks, Inc. | Methods for traffic rate control and devices thereof |
US10015143B1 (en) | 2014-06-05 | 2018-07-03 | F5 Networks, Inc. | Methods for securing one or more license entitlement grants and devices thereof |
US11838851B1 (en) | 2014-07-15 | 2023-12-05 | F5, Inc. | Methods for managing L7 traffic classification and devices thereof |
WO2016018401A1 (en) * | 2014-07-31 | 2016-02-04 | Hewlett-Packard Development Company, L.P. | Dynamic adjustment of thresholds |
US10122630B1 (en) | 2014-08-15 | 2018-11-06 | F5 Networks, Inc. | Methods for network traffic presteering and devices thereof |
US10182013B1 (en) | 2014-12-01 | 2019-01-15 | F5 Networks, Inc. | Methods for managing progressive image delivery and devices thereof |
US11895138B1 (en) | 2015-02-02 | 2024-02-06 | F5, Inc. | Methods for improving web scanner accuracy and devices thereof |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US11350254B1 (en) | 2015-05-05 | 2022-05-31 | F5, Inc. | Methods for enforcing compliance policies and devices thereof |
US11757946B1 (en) | 2015-12-22 | 2023-09-12 | F5, Inc. | Methods for analyzing network traffic and enforcing network policies and devices thereof |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US11178150B1 (en) | 2016-01-20 | 2021-11-16 | F5 Networks, Inc. | Methods for enforcing access control list based on managed application and devices thereof |
US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
US10791088B1 (en) | 2016-06-17 | 2020-09-29 | F5 Networks, Inc. | Methods for disaggregating subscribers via DHCP address translation and devices thereof |
US11063758B1 (en) | 2016-11-01 | 2021-07-13 | F5 Networks, Inc. | Methods for facilitating cipher selection and devices thereof |
US10505792B1 (en) | 2016-11-02 | 2019-12-10 | F5 Networks, Inc. | Methods for facilitating network traffic analytics and devices thereof |
US10812266B1 (en) | 2017-03-17 | 2020-10-20 | F5 Networks, Inc. | Methods for managing security tokens based on security violations and devices thereof |
US10972453B1 (en) | 2017-05-03 | 2021-04-06 | F5 Networks, Inc. | Methods for token refreshment based on single sign-on (SSO) for federated identity environments and devices thereof |
US11343237B1 (en) | 2017-05-12 | 2022-05-24 | F5, Inc. | Methods for managing a federated identity environment using security and access control data and devices thereof |
US11122042B1 (en) | 2017-05-12 | 2021-09-14 | F5 Networks, Inc. | Methods for dynamically managing user access control and devices thereof |
US11122083B1 (en) | 2017-09-08 | 2021-09-14 | F5 Networks, Inc. | Methods for managing network connections based on DNS data and network policies and devices thereof |
US20220035684A1 (en) * | 2020-08-03 | 2022-02-03 | Nvidia Corporation | Dynamic load balancing of operations for real-time deep learning analytics |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0744505A (ja) * | 1993-08-03 | 1995-02-14 | Agency Of Ind Science & Technol | 並列計算機における負荷分散方法 |
JP2005182641A (ja) * | 2003-12-22 | 2005-07-07 | Hitachi Information Systems Ltd | 動的負荷分散システム及び動的負荷分散方法 |
JP2006012065A (ja) * | 2004-06-29 | 2006-01-12 | Honda Motor Co Ltd | 資源負荷適正化管理システム |
JP2006113827A (ja) * | 2004-10-15 | 2006-04-27 | Hitachi Ltd | Cpu余裕管理とトランザクション優先度による負荷分散方法 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3658420B2 (ja) * | 1994-04-14 | 2005-06-08 | 株式会社日立製作所 | 分散処理システム |
JP2000137692A (ja) * | 1998-10-30 | 2000-05-16 | Toshiba Corp | 分散ノード間負荷分散方式 |
WO2001013228A2 (en) * | 1999-08-13 | 2001-02-22 | Sun Microsystems, Inc. | Graceful distribution in application server load balancing |
US20050022202A1 (en) * | 2003-07-09 | 2005-01-27 | Sun Microsystems, Inc. | Request failover mechanism for a load balancing system |
-
2009
- 2009-03-03 JP JP2009048724A patent/JP2010204876A/ja active Pending
-
2010
- 2010-02-04 TW TW099103349A patent/TW201101186A/zh unknown
- 2010-02-23 US US13/203,106 patent/US20120016994A1/en not_active Abandoned
- 2010-02-23 CN CN2010800076778A patent/CN102317916A/zh active Pending
- 2010-02-23 WO PCT/JP2010/001196 patent/WO2010100859A1/ja active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0744505A (ja) * | 1993-08-03 | 1995-02-14 | Agency Of Ind Science & Technol | 並列計算機における負荷分散方法 |
JP2005182641A (ja) * | 2003-12-22 | 2005-07-07 | Hitachi Information Systems Ltd | 動的負荷分散システム及び動的負荷分散方法 |
JP2006012065A (ja) * | 2004-06-29 | 2006-01-12 | Honda Motor Co Ltd | 資源負荷適正化管理システム |
JP2006113827A (ja) * | 2004-10-15 | 2006-04-27 | Hitachi Ltd | Cpu余裕管理とトランザクション優先度による負荷分散方法 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103856512A (zh) * | 2012-11-30 | 2014-06-11 | 华为技术有限公司 | 云计算的管理服务器、工作和闲置主机以及资源调度方法 |
CN115633041A (zh) * | 2022-10-31 | 2023-01-20 | 中科星图数字地球合肥有限公司 | 多集群的管理方法、装置、电子设备和可读存储介质 |
CN115633041B (zh) * | 2022-10-31 | 2024-06-04 | 中科星图数字地球合肥有限公司 | 多集群的管理方法、装置、电子设备和可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20120016994A1 (en) | 2012-01-19 |
CN102317916A (zh) | 2012-01-11 |
JP2010204876A (ja) | 2010-09-16 |
TW201101186A (en) | 2011-01-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010100859A1 (ja) | 分散システム | |
CN109218355B (zh) | 负载均衡引擎,客户端,分布式计算***以及负载均衡方法 | |
EP3453148B1 (en) | System and method for latency-based queuing | |
US9729488B2 (en) | On-demand mailbox synchronization and migration system | |
EP2883329B1 (en) | Computer information system and dynamic disaster recovery method therefor | |
US9456056B2 (en) | Load balancing utilizing adaptive thresholding | |
US7062556B1 (en) | Load balancing method in a communication network | |
US8095935B2 (en) | Adapting message delivery assignments with hashing and mapping techniques | |
US7712103B2 (en) | Method and system for managing load balancing in data processing system | |
WO2023050901A1 (zh) | 一种负载均衡方法、装置、设备、计算机存储介质和程序 | |
US8930521B2 (en) | Method, apparatus, and computer program product for enabling monitoring of a resource | |
JP6378057B2 (ja) | 接続制御装置、接続制御方法、接続制御システムおよびコンピュータプログラム | |
EP2515504B1 (en) | Content delivery method, system and schedule server | |
Nakai et al. | Load balancing for internet distributed services using limited redirection rates | |
US9628556B2 (en) | Decentralized request routing | |
JP2010238051A (ja) | 負荷分散プログラム及び負荷分散装置 | |
GB2533017A (en) | A method and system for scalable job processing | |
CA3030504A1 (en) | Blockchain network and task scheduling method therefor | |
CN112711479A (zh) | 服务器集群的负载均衡***、方法、装置和存储介质 | |
JP4834622B2 (ja) | ビジネスプロセス運用管理システム、方法、プロセス運用管理装置およびそのプログラム | |
CN111078386A (zh) | 一种分布式调度***的控制方法及控制装置 | |
EP2580671B1 (en) | Http-based client-server communication system and method | |
JP6233141B2 (ja) | データベースシステム、データベースサーバ、データベースサーバプログラム、データベースクライアント及びデータベースクライアントプログラム | |
JP2011070435A (ja) | 計算機システム、リクエスト処理方法及びサーバ装置 | |
CN112698927A (zh) | 双向通信方法、装置、电子设备及机器可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080007677.8 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10748461 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13203106 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10748461 Country of ref document: EP Kind code of ref document: A1 |