CN111800472A - Block link point load balancing method, device, medium and equipment - Google Patents

Block link point load balancing method, device, medium and equipment Download PDF

Info

Publication number
CN111800472A
CN111800472A CN202010533346.3A CN202010533346A CN111800472A CN 111800472 A CN111800472 A CN 111800472A CN 202010533346 A CN202010533346 A CN 202010533346A CN 111800472 A CN111800472 A CN 111800472A
Authority
CN
China
Prior art keywords
reverse proxy
eos
proxy server
node
load balancing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010533346.3A
Other languages
Chinese (zh)
Inventor
游海涛
邓敬渔
傅福斌
王琳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xiamen Wanshi Shunyi Technology Co Ltd
Ylz Information Technology Co ltd
Original Assignee
Xiamen Wanshi Shunyi Technology Co Ltd
Ylz Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Xiamen Wanshi Shunyi Technology Co Ltd, Ylz Information Technology Co ltd filed Critical Xiamen Wanshi Shunyi Technology Co Ltd
Priority to CN202010533346.3A priority Critical patent/CN111800472A/en
Publication of CN111800472A publication Critical patent/CN111800472A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing
    • H04L67/1008Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083Techniques for rebalancing the load in a distributed system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • H04L43/103Active monitoring, e.g. heartbeat, ping or trace-route with adaptive polling, i.e. dynamically adapting the polling rate
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/16Threshold monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101Access control lists [ACL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Hardware Redundancy (AREA)

Abstract

The invention relates to the technical field of load balancing, in particular to a method, a device, a medium and equipment for balancing load of block chain nodes, wherein the method for balancing load of the block chain nodes comprises the steps of arranging a plurality of reverse proxy servers between a plurality of EOS nodes and a user; setting a keep-alive mechanism on the reverse proxy server to ensure the normal use of the reverse proxy server; polling and detecting an EOS node by a reverse proxy server; and forwarding the request to the EOS node according to the configuration of the reverse proxy server according to the detection result. The high availability of the virtual IP address for providing the service to the outside on the reverse proxy server is ensured by arranging the keep-alive mechanism on the reverse proxy server, the loads of all EOS nodes are balanced according to the configuration of the reverse proxy server, and meanwhile, a black and white list is arranged on the accessed IP address for limiting the current, thereby avoiding the request failure and even the downtime caused by the overload of the EOS node.

Description

Block link point load balancing method, device, medium and equipment
Technical Field
The invention relates to the technical field of load balancing, in particular to a block link point load balancing method, device, medium and equipment.
Background
The block chain technology has wide application prospect as a new distributed storage service. EOS is a new blockchain architecture promulgated by block. Unlike the common recognition mode PoW of bitcoin or ether house, EOS employs DPoS mechanism, has short block-out time and high tps (transaction persistent), and is considered as a representative public link item of the block link 3.0 technology in the industry.
With the development of an EOS blockchain network, more and more DAPPs are deployed on an EOS main network, an EOS node is used as an entrance of the EOS blockchain network, and mainly provided is a super node of the EOS or an interface node built by an enterprise user, but due to the occurrence of a large number of network crawlers and malicious attackers, the EOS node and the EOS node face the problem of load bearing bottleneck.
When an EOS node faces an attack and a load bearing limit, a request is easy to fail or even go down, in the prior art, a failed EOS node is manually switched to other nodes, but a single EOS node cannot provide service after being failed.
Disclosure of Invention
In order to solve the above-mentioned deficiency that EOS nodes are easy to cause request failure or even crash when facing attack and load bearing limit in the prior art, the block link point load balancing method, device, medium and equipment provided by the invention make each EOS node load balanced, and ensure that the EOS node can provide service.
In a first aspect, an embodiment of the present application provides a block link point load balancing method, including the following steps:
s100: arranging a plurality of reverse proxy servers between a plurality of EOS nodes and users;
s200: setting a keep-alive mechanism on the reverse proxy server to ensure normal use of the reverse proxy server;
s300: the reverse proxy server polls and detects the EOS node;
s400: and forwarding the request to the EOS node according to the configuration of the reverse proxy server according to the detection result.
Further, in S200, keep-alive mechanisms are set on all the reverse proxy servers to form a router group, each reverse proxy server includes a main server and a plurality of backup servers, the main server is provided with a virtual IP address for providing services to the outside, and the main server is configured to send multicast of a route redundancy protocol to the backup servers.
Further, when the alternative servers do not receive the route redundancy protocol, one of the alternative servers is elected as a new main server according to the priority of the route redundancy protocol, and the virtual IP address is shifted to the new main server to ensure that an external IP address is available.
Further, in S300, the reverse proxy server distributes to different EOS nodes one by one according to a request sequence, and detects availability of each EOS node; and when the EOS node fails, the EOS node is removed from the EOS node cluster, and when the failed EOS node recovers, the EOS node is automatically added to the EOS node cluster.
Further, in S400, a monitoring and analyzing system is used to collect and analyze data information of the reverse proxy server, and modify or set the configuration of the reverse proxy server according to the data information.
Furthermore, the monitoring and analyzing system modifies or sets the speed limit configuration of the reverse proxy server according to the known degree and the request frequency of the user IP address, and sets a corresponding black and white list to be issued to the reverse proxy server.
Further, the monitoring analysis system sets a monitoring threshold, judges and analyzes the utilization rate of the CPU of the EOS node according to the monitoring threshold, and modifies or sets the distribution weight configuration of the reverse proxy server to the EOS node.
In a second aspect, an embodiment of the present application provides a block link point load balancing apparatus, including:
the system comprises a setting module, a processing module and a processing module, wherein the setting module is used for setting a plurality of reverse proxy servers between a plurality of EOS nodes and a user;
the keep-alive module is used for setting a keep-alive mechanism on the reverse proxy server to ensure the normal use of the reverse proxy server;
the polling module is used for polling and detecting the EOS node by the reverse proxy server;
and the forwarding module is used for forwarding the request to the EOS node according to the detection result and the configuration of the reverse proxy server.
In a third aspect, embodiments of the present application provide a computer-readable storage medium, which stores computer instructions, and when executed by a processor, implement a block link point load balancing method as described in any one of the above.
In a fourth aspect, embodiments of the present application provide a node load balancing apparatus, including at least one processor, and a memory communicatively connected to the processor, where the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to cause the processor to perform a block-link point load balancing method as described in any one of the above.
Compared with the prior art, the block link node load balancing method, the block link node load balancing device, the block link node load balancing medium and the block link node load balancing equipment have the advantages that the reverse proxy servers are arranged between the user and the EOS nodes, the keep-alive mechanism is arranged on the reverse proxy servers to ensure high availability of the virtual IP addresses providing services to the outside on the reverse proxy servers, the EOS nodes are detected in a polling mode by the reverse proxy service areas, the EOS nodes are balanced in load according to the configuration of the reverse proxy servers, meanwhile, the black and white lists are arranged on the IP addresses of the accessed users to limit current, and request failure and even downtime caused by overload of the EOS nodes are avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a first embodiment of the present invention;
FIG. 2 is a schematic diagram of an architecture of a first embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a fourth embodiment of the present invention.
Reference numerals:
10 setup module 20 keep-alive module 30 poll module
40 forwarding module 50 memory 60 processor
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Furthermore, the technical features designed in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Example one
Fig. 1 is a flowchart of a block link point load balancing method according to an embodiment of the present application, and as shown in fig. 1, the method includes:
s100: arranging a plurality of reverse proxy servers between a plurality of EOS nodes and users;
in specific implementation, as shown in fig. 1 and fig. 2, the EOS interface node is an API interface node, a user needs to access the API node when accessing the EOS node, a plurality of EOS nodes or API nodes form a node cluster, and a plurality of reverse proxy servers are arranged between the user and the node cluster formed by the plurality of EOS nodes or API nodes to receive a request of the user.
S200: setting a keep-alive mechanism on the reverse proxy server to ensure normal use of the reverse proxy server;
in specific implementation, as shown in fig. 1 and fig. 2, keep-alive mechanisms are set on a plurality of reverse proxy servers to form a router group, and preferably, the keep-alive mechanism set on the reverse proxy server in this embodiment is keepalived; the reverse proxy server in the router group comprises a main server and a plurality of standby servers, wherein the main server is provided with a virtual IP address for providing service to the outside, and simultaneously, the main server sequentially sends multicast of a route redundancy protocol to the standby servers.
When the alternative servers do not receive the route redundancy protocol sent by the main server, one of the alternative servers is elected according to the priority of the route redundancy protocol, and when the new main server is used, the virtual IP address drifts to the new main server, so that the IP address for providing service to the outside is ensured to be available.
S300: the reverse proxy server polls and detects the EOS node;
in specific implementation, as shown in fig. 1 and fig. 2, the reverse proxy server trains and detects the EOS nodes or API nodes in turn, and distributes the EOS nodes or API nodes to different back-end EOS nodes or API nodes one by one according to the request sequence, and the proxy server will automatically detect the availability of the back-end EOS nodes or API nodes.
Specifically, when a certain EOS node or API node fails, the reverse proxy server removes the failed EOS node or API node from the node cluster; when the failure EOS node or API node is eliminated and recovered, the failure EOS node or API node is automatically added into the node cluster, so that each EOS node or API node can effectively provide services.
S400: and forwarding the request to the EOS node according to the configuration of the reverse proxy server according to the detection result.
In specific implementation, as shown in fig. 1 and 2, according to a result that the reverse proxy server detects whether the EOS node or the API node is available, the request is forwarded to the EOS node or the API node according to the configuration of the reverse proxy server, and the reverse proxy server is provided with a monitoring and analyzing system for modifying or setting the configuration of the reverse proxy server.
Specifically, the monitoring and analyzing system modifies or sets the speed limit configuration of the reverse proxy server according to the known degree and the request frequency of the user IP address, preferably, when the accessed user IP address is a known IP address, such as the IP address of a partner DAPP, the configuration of the reverse proxy server is set to limit the speed of the known IP address, the monitoring and analyzing system adds the known IP address to a white list and sends the white list to the configuration of the reverse proxy server, and the user IP address in the white list can be directly accessed;
and other unknown IP addresses are distributed to the configuration of the request times per second, specifically, the monitoring and analyzing system analyzes an http request header, when a large number of request logs of an unknown IP address or Agent appear in a short time, or a large number of requests with the same address and the same request header appear in a short time, and illegal contracts, violence and other requests appear in the request content, the monitoring and analyzing system recognizes the requests as crawler requests, shields the crawler requests, adds the crawler requests to a blacklist, and sends the crawler requests to the configuration of the reverse proxy server.
Meanwhile, the monitoring analysis system can also set a monitoring threshold, judge and analyze the CPU utilization rate of the EOS node or the API node according to the monitoring threshold, and modify or set the distribution weight configuration of the reverse proxy server to the EOS node or the API node; preferably, in this embodiment, the monitoring threshold is that the EOS node or the API node CPU reaches 90% utilization, when the utilization of a certain EOS node or API node CPU reaches 90% and then is prone to cause an access failure, the monitoring analysis system actively modifies the distribution weight of the backend node cluster of the reverse proxy server, and switches the access request to another EOS node or API node, and the other EOS node or API node may schedule according to different rules according to its load condition, the IP address of the accessing user, or different time periods, thereby avoiding a request failure or even downtime caused by overload of the EOS node or API node.
Compared with the prior art, the block link point load balancing method provided by the invention has the advantages that the reverse proxy servers are arranged between the user and the EOS nodes, the keep-alive mechanism is arranged on the reverse proxy servers to ensure high availability of the virtual IP addresses providing services to the outside on the reverse proxy servers, the EOS nodes are polled and detected by the reverse proxy service areas, the loads of the EOS nodes are balanced according to the configuration of the reverse proxy servers, and meanwhile, black and white lists are arranged on the accessed IP addresses for current limiting, so that the problem that the request fails or even crashes caused by overload of the EOS nodes is avoided.
Fig. 3 is a schematic diagram of a block link point load balancing device according to a second embodiment of the present application, where the block link point load balancing device is configured to execute a block link point load balancing method according to any one of the foregoing descriptions, and as shown in fig. 3, the block link point load balancing device includes: a setup module 10, a keep alive module 20, a polling module 30, and a forwarding module 40.
In specific implementation, the setting module 10 is configured to set a plurality of reverse proxy servers between a plurality of EOS nodes and a user; the keep-alive module 20 is used for setting a keep-alive mechanism on the reverse proxy server to ensure the normal use of the reverse proxy server; the polling module 30 is configured to poll and detect the EOS node by the reverse proxy server; the forwarding module 40 is configured to forward the request to the EOS node according to the configuration of the reverse proxy server according to the detection result. The working principle of the setting module 10, the keep-alive module 20, the polling module 30 and the forwarding module 40 is specifically described with reference to the related description of the embodiment of the method of the present application, and is not described herein again.
EXAMPLE III
A third embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method for balancing block link point loads according to any one of the above embodiments may be implemented.
In specific implementation, the computer-readable storage medium is a magnetic Disk, an optical Disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a flash Memory (FlashMemory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid-State Drive (SSD), or the like; the computer readable storage medium may also include a combination of memories of the above kinds.
Example four
Fig. 4 is a node load balancing apparatus according to a fourth embodiment of the present application, and as shown in fig. 4, the node load balancing apparatus includes at least one processor 60 and a memory 50 communicatively connected to the processor 60, where the memory 50 stores instructions executable by the at least one processor 60, and the instructions are executed by the at least one processor 60, so that the processor 60 executes a block link point load balancing method according to any one of the above-mentioned embodiments, specifically referring to the description in the above-mentioned method embodiments.
In one embodiment, the number of the processors 60 may be one or more, and the processor 60 may be a Central Processing Unit (CPU). The Processor 60 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 50 and the processors 60 may be communicatively connected by a bus or other means, and the memory 50 stores instructions executable by the at least one processor 60, the instructions being executed by the at least one processor 60 to cause the processor 60 to perform a block link point load balancing method as described in any one of the above.
Compared with the prior art, the block link node load balancing method, the block link node load balancing device, the block link node load balancing medium and the block link node load balancing equipment have the advantages that the reverse proxy servers are arranged between a user and the EOS nodes, the keep-alive mechanisms are arranged on the reverse proxy servers to ensure high availability of virtual IP addresses providing services to the outside on the reverse proxy servers, the EOS nodes are detected in a polling mode by the reverse proxy service areas, the EOS nodes are balanced in load according to the configuration of the reverse proxy servers, meanwhile, black and white lists are arranged on the accessed IP addresses for current limiting, and the problem that requests fail or even crash is caused by overload of the EOS nodes is avoided.
Although terms such as setup module, keep-alive module, polling module, forwarding module, memory, and processor are used more often herein, the possibility of using other terms is not excluded. These terms are used merely to more conveniently describe and explain the nature of the present invention; they are to be construed as being without limitation to any additional limitations that may be imposed by the spirit of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. A block link point load balancing method is characterized by comprising the following steps:
s100: arranging a plurality of reverse proxy servers between a plurality of EOS nodes and users;
s200: setting a keep-alive mechanism on the reverse proxy server to ensure normal use of the reverse proxy server;
s300: the reverse proxy server polls and detects the EOS node;
s400: and forwarding the request to the EOS node according to the configuration of the reverse proxy server according to the detection result.
2. A block link point load balancing method according to claim 1, characterized in that: in S200, keep-alive mechanisms are set on all the reverse proxy servers to form a router group, each reverse proxy server includes a main server and a plurality of backup servers, the main server is provided with a virtual IP address for providing services to the outside, and the main server is configured to send multicast of a route redundancy protocol to the backup servers.
3. A block link point load balancing method according to claim 2, characterized in that: when the alternative servers do not receive the route redundancy protocol, one of the alternative servers is elected as a new main server according to the priority of the route redundancy protocol, and the virtual IP address is drifted to the new main server to ensure that an external IP address is available.
4. A block link point load balancing method according to claim 1, characterized in that: in S300, the reverse proxy servers are distributed to different EOS nodes one by one according to a request sequence, and detect the availability of each EOS node; and when the EOS node fails, the EOS node is removed from the EOS node cluster, and when the failed EOS node recovers, the EOS node is automatically added to the EOS node cluster.
5. A block link point load balancing method according to claim 1, characterized in that: in S400, a monitoring and analyzing system is used to collect and analyze data information of the reverse proxy server, and modify or set the configuration of the reverse proxy server according to the data information.
6. The block link point load balancing method according to claim 5, wherein: and the monitoring and analyzing system modifies or sets the speed limit configuration of the reverse proxy server according to the known degree and the request frequency of the user IP address, and sets a corresponding black and white list to be issued to the reverse proxy server.
7. The block link point load balancing method according to claim 5, wherein: and the monitoring analysis system sets a monitoring threshold, judges and analyzes the utilization rate of the CPU of the EOS node according to the monitoring threshold, and modifies or sets the distribution weight configuration of the reverse proxy server to the EOS node.
8. A block link point load balancing device, comprising:
the system comprises a setting module, a processing module and a processing module, wherein the setting module is used for setting a plurality of reverse proxy servers between a plurality of EOS nodes and a user;
the keep-alive module is used for setting a keep-alive mechanism on the reverse proxy server to ensure the normal use of the reverse proxy server;
the polling module is used for polling and detecting the EOS node by the reverse proxy server;
and the forwarding module is used for forwarding the request to the EOS node according to the detection result and the configuration of the reverse proxy server.
9. A computer-readable storage medium characterized by: the computer-readable storage medium stores computer instructions which, when executed by a processor, implement a block link point load balancing method as claimed in any one of claims 1 to 7.
10. A node load balancing device, characterized by: comprising at least one processor and a memory communicatively coupled to the processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to cause the processor to perform a block link point load balancing method as claimed in any one of claims 1 to 7.
CN202010533346.3A 2020-06-12 2020-06-12 Block link point load balancing method, device, medium and equipment Pending CN111800472A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010533346.3A CN111800472A (en) 2020-06-12 2020-06-12 Block link point load balancing method, device, medium and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010533346.3A CN111800472A (en) 2020-06-12 2020-06-12 Block link point load balancing method, device, medium and equipment

Publications (1)

Publication Number Publication Date
CN111800472A true CN111800472A (en) 2020-10-20

Family

ID=72803316

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010533346.3A Pending CN111800472A (en) 2020-06-12 2020-06-12 Block link point load balancing method, device, medium and equipment

Country Status (1)

Country Link
CN (1) CN111800472A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112699322A (en) * 2021-01-06 2021-04-23 润联软件***(深圳)有限公司 Hierarchical weakly centralized block chain browser generation method and related components thereof
CN113472864A (en) * 2021-06-21 2021-10-01 湖南大学 High-performance block chain distributed storage system, method, equipment and storage medium
CN113746918A (en) * 2021-09-03 2021-12-03 上海幻电信息科技有限公司 Hypertext transfer protocol proxy method and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208026A (en) * 2015-09-29 2015-12-30 努比亚技术有限公司 Hostile attack preventing method and network system
CN108933829A (en) * 2018-07-10 2018-12-04 浙江数链科技有限公司 A kind of load-balancing method and device
CN110708309A (en) * 2019-09-29 2020-01-17 武汉极意网络科技有限公司 Anti-crawler system and method
CN111213128A (en) * 2019-10-16 2020-05-29 支付宝(杭州)信息技术有限公司 Implementing blockchain based web services
CN114911602A (en) * 2021-02-07 2022-08-16 中移(苏州)软件技术有限公司 Load balancing method, device, equipment and storage medium for server cluster

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208026A (en) * 2015-09-29 2015-12-30 努比亚技术有限公司 Hostile attack preventing method and network system
CN108933829A (en) * 2018-07-10 2018-12-04 浙江数链科技有限公司 A kind of load-balancing method and device
CN110708309A (en) * 2019-09-29 2020-01-17 武汉极意网络科技有限公司 Anti-crawler system and method
CN111213128A (en) * 2019-10-16 2020-05-29 支付宝(杭州)信息技术有限公司 Implementing blockchain based web services
CN114911602A (en) * 2021-02-07 2022-08-16 中移(苏州)软件技术有限公司 Load balancing method, device, equipment and storage medium for server cluster

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李纪人,黄诗峰等: "《air MAX无线网络原理、技术与应用》", 西安电子科技大学出版社, pages: 127 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112699322A (en) * 2021-01-06 2021-04-23 润联软件***(深圳)有限公司 Hierarchical weakly centralized block chain browser generation method and related components thereof
CN113472864A (en) * 2021-06-21 2021-10-01 湖南大学 High-performance block chain distributed storage system, method, equipment and storage medium
CN113746918A (en) * 2021-09-03 2021-12-03 上海幻电信息科技有限公司 Hypertext transfer protocol proxy method and system

Similar Documents

Publication Publication Date Title
US8850043B2 (en) Network security using trust validation
CN111800472A (en) Block link point load balancing method, device, medium and equipment
CN112671882B (en) Same-city double-activity system and method based on micro-service
US6658595B1 (en) Method and system for asymmetrically maintaining system operability
US8108715B1 (en) Systems and methods for resolving split-brain scenarios in computer clusters
CN111800458B (en) Dynamic load balancing method and system for Kubernetes container cloud platform
US7844691B2 (en) Scalable distributed storage and delivery
US6757836B1 (en) Method and apparatus for resolving partial connectivity in a clustered computing system
US20130159487A1 (en) Migration of Virtual IP Addresses in a Failover Cluster
US20060195561A1 (en) Discovering and monitoring server clusters
US9075660B2 (en) Apparatus and method for providing service availability to a user via selection of data centers for the user
JP2016520904A (en) Asymmetric packet flow in distributed load balancers
CN111130835A (en) Data center dual-active system, switching method, device, equipment and medium
WO2017215430A1 (en) Node management method in cluster and node device
US8051202B2 (en) Method and apparatus for providing alarm correlation for a gateway router
US8131871B2 (en) Method and system for the automatic reroute of data over a local area network
WO2013126264A1 (en) Multi-blade network traffic management apparatus with improved failure handling and methods thereof
CN111052092A (en) Cluster system, cluster system control method, server device, control method, and non-transitory computer-readable medium storing program
US9674061B2 (en) Management system, management apparatus and management method
US8370897B1 (en) Configurable redundant security device failover
US8868731B1 (en) Technique for false positives prevention in high availability network
US11057478B2 (en) Hybrid cluster architecture for reverse proxies
CN112583951B (en) Application layer double-live method, device, equipment and storage medium
US10237122B2 (en) Methods, systems, and computer readable media for providing high availability support at a bypass switch
CN113805788A (en) Distributed storage system and exception handling method and related device thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20201020