WO2023202182A1 - 后端服务器管理方法、装置、可读介质及电子设备 - Google Patents

后端服务器管理方法、装置、可读介质及电子设备 Download PDF

Info

Publication number
WO2023202182A1
WO2023202182A1 PCT/CN2023/074304 CN2023074304W WO2023202182A1 WO 2023202182 A1 WO2023202182 A1 WO 2023202182A1 CN 2023074304 W CN2023074304 W CN 2023074304W WO 2023202182 A1 WO2023202182 A1 WO 2023202182A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
health status
end server
health
indicator
Prior art date
Application number
PCT/CN2023/074304
Other languages
English (en)
French (fr)
Inventor
冷曼曼
Original Assignee
京东科技信息技术有限公司
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 京东科技信息技术有限公司 filed Critical 京东科技信息技术有限公司
Publication of WO2023202182A1 publication Critical patent/WO2023202182A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests

Definitions

  • the present disclosure relates to the field of load balancing technology, and specifically to a backend server management method, device, electronic device, and computer-readable storage medium.
  • load balancing can check the availability of the backend server by sending detection messages regularly. If the backend server service is abnormal, you need to wait for multiple detection cycles before the abnormal backend server can be removed.
  • a backend server management method is provided, which is applied to the backend server and includes:
  • Each server health status indicator includes an actual indicator value and a reference indicator value corresponding to the health status; wherein, the reference indicator value includes a reference indicator range;
  • a backend server management method is provided, which is applied to a load balancing server; including:
  • the load balancing server includes a health check service, and obtains corresponding health check data in the health check service;
  • the first response operation includes modifying the health check data;
  • the first monitoring parameter is deleted; the second response operation includes closing the health check service.
  • a backend server management device which is applied to the backend server and includes:
  • a receiving module configured to receive first monitoring parameters sent by the load balancing server, where the first monitoring parameters include one or more server health status indicators and corresponding reference indicator values;
  • a monitoring module used to monitor the actual indicator value of each server health status indicator in the back-end server
  • Determining the server status module is used to determine the health status of the back-end server based on the actual index value and the reference index value of each server health status indicator;
  • a request sending module configured to send a removal request to the load balancing server to remove the back-end server when it is determined that the health status of the back-end server does not meet the preset conditions.
  • a backend server management device applied to a load balancing server, including:
  • a sending module configured to send first monitoring parameters to the back-end server, where the first monitoring parameters include one or more server health status indicators, so as to facilitate monitoring of each server health status indicator in the back-end server and based on each server health status indicator.
  • the server health status indicator determines the health of the back-end server;
  • the removal module is used to remove the back-end server when receiving a removal request sent by the back-end server whose health condition does not meet the preset conditions.
  • an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the operation via executing the executable instructions. Perform any of the methods described above.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, any one of the above methods is implemented.
  • Figure 1 shows a schematic diagram of an exemplary system architecture of a back-end server management device to which embodiments of the present disclosure can be applied;
  • Figure 2 schematically shows a flow chart of a backend server management method according to one embodiment of the present disclosure
  • Figure 3 schematically illustrates a flow chart for receiving a first monitoring parameter according to one embodiment of the present disclosure
  • Figure 4 schematically shows a flow chart of requesting to remove a backend server according to one embodiment of the present disclosure
  • Figure 5 schematically shows a flow chart for sending first monitoring parameters according to one embodiment of the present disclosure
  • Figure 6 schematically shows a diagram showing a backend server management method according to one embodiment of the present disclosure
  • Figure 7 schematically illustrates a block diagram of a backend server device according to one embodiment of the present disclosure
  • Figure 8 schematically illustrates a block diagram of a backend server device according to one embodiment of the present disclosure
  • FIG. 9 schematically shows a structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present disclosure.
  • Example embodiments will now be described more fully with reference to the accompanying drawings.
  • Example embodiments may, however, be embodied in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of the example embodiments.
  • the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments.
  • numerous specific details are provided to provide a thorough understanding of embodiments of the disclosure.
  • those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced without one or more of the specific details described, or other methods, components, devices, steps, etc. may be adopted.
  • well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the disclosure.
  • FIG. 1 shows a schematic diagram of the system architecture of an exemplary application environment in which a back-end server management method and device according to embodiments of the present disclosure can be applied.
  • the system architecture 100 may include one or more of terminal devices 101, 102, 103, a network 104 and a server 105.
  • the network 104 is a medium used to provide communication links between the terminal devices 101, 102, 103 and the server 105.
  • Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
  • the terminal devices 101, 102, and 103 may be various electronic devices with display screens, including but not limited to desktop computers, portable computers, smart phones, tablet computers, and so on. It should be understood that the number of terminal devices, networks and servers in Figure 1 is only illustrative. Depending on implementation needs, there can be any number of end devices, networks, and servers.
  • the server 105 may be a server cluster composed of multiple servers.
  • the back-end server management method provided by the embodiment of the present disclosure can be executed on the server 105. Accordingly, the back-end server management device is generally provided in the server 105. The back-end server management method provided by the embodiment of the present disclosure can also be executed by the terminal devices 101, 102, and 103. Correspondingly, the back-end server management device can also be provided in the terminal devices 101, 102, and 103. This exemplary embodiment There are no special restrictions on this.
  • the server 105 may receive the first message sent by the load balancing server.
  • Monitoring parameters include one or more server health status indicators; monitoring each server health status indicator in the back-end server; determining the health status indicator of the back-end server based on each of the server health status indicators.
  • Health status when it is determined that the health status of the back-end server does not meet the preset conditions, a removal request is sent to the load balancing server to remove the back-end server; the above application scenarios are only for examples, and this exemplary The embodiment is not limited to this.
  • FIG. 2 schematically shows a flow chart of a backend server management method according to an embodiment of the present disclosure.
  • the backend server management method is applicable to the electronic device described in the previous embodiment.
  • the back-end server management method at least includes steps S210 to S240. The details are as follows:
  • Step S210 Receive first monitoring parameters sent by the load balancing server, where the first monitoring parameters include one or more server health status indicators;
  • Step S220 monitor the health status indicators of each server in the back-end server
  • Step S230 Determine the health status of the back-end server based on each server health status indicator
  • Step S240 When it is determined that the health status of the back-end server does not meet the preset conditions, send a removal request to the load balancing server to remove the back-end server.
  • the back-end server detects an abnormality in the deployed service and immediately notifies the load balancer to remove itself.
  • the back-end server's detection of its own service can more truly reflect the status of the service. Availability, and there is no need to wait for the detection cycle, thus shortening the removal time of abnormal servers; on the other hand, the way the back-end server detects its own services is not affected by external factors, such as network stability, which reduces service availability detection error, thereby improving the accuracy of simulated detection.
  • the first monitoring parameters include one or more server health indicators; wherein the first monitoring parameters can be used to monitor the health of the back-end server.
  • the first monitoring parameter can be port data.
  • the first monitoring parameter can also be a monitoring script.
  • the back-end server can monitor the specified
  • the available status of the service for example, can be determined by one or more server health status indicators and corresponding reference indicator values in the first monitoring script, where the server health status indicator can include the server health status indicator.
  • the actual measurement of health phenomena is used to reflect the health status of the server from a certain aspect or aspect.
  • the server health status indicator may refer to the server health performance indicator or the server health technical indicator.
  • the health status indicator of the server can also be reflected through the reference indicator value, which can be understood as representing the health status indicator of the server in the form of a parameter value; where the reference indicator value can be a standard used to measure whether the server is in a healthy state, the reference indicator The value may also have a reference indicator range. For example, in this embodiment, if the current indicator value of the server is within the reference indicator value range of the corresponding server, it is determined that the server service is healthy. It can be understood that the reference indicator The value is the indicator value corresponding to the backend server health status indicator.
  • the first script parameter sent by the load balancing server may be one or more server health status indicators and one or more server health status indicators.
  • the reference index value of the server health status index is not limited to this in this embodiment.
  • the health indicator may also include: if the backend server can correctly respond to the detection behavior, it is determined that the server meets the health indicator requirements. For example, a detection behavior is sent through a health check. If the backend server If the server responds correctly, it is determined that the corresponding back-end server is healthy; where the response of the back-end server may include the detection behavior, for example, it may be initiating a tcp (Transmission Control Protocol) connection, If the connection can be established normally, it is considered that the back-end server is normal; it can also be initiated by an HTTP (Hyper Text Transfer Protocol) request. When the back-end server can respond normally, the back-end server is considered normal. In this implementation This example is not limited to this.
  • tcp Transmission Control Protocol
  • the first monitoring parameter may be sent to the backend server through the following steps S310 to S320:
  • step S310 determine the service port of the back-end server that matches the first monitoring parameter; wherein the back-end server may include multiple service ports.
  • the service port information may include the health status indicator information of the back-end server, for example, the actual indicator value and the reference indicator value of the back-end server health status indicator.
  • the service port can compare the actual indicator value and the reference indicator value of each server health status indicator, and the service port can also receive the first monitoring parameter; in another embodiment of the present application, the service port can Receive a detection behavior sent by the health check, and can also make a correct response to the detection behavior through the service port.
  • the health status of the back-end server can be judged based on the information received by the service port. For example, you can initiate a TCP connection, receive the TCP connection according to the service port. If the connection can be established normally, it is considered that the detection back-end server is normal. You can also initiate an http request and receive the http request through the service port. If the back-end server can be normal response, the backend server is considered normal, which is not limited to this in the embodiment of the present application.
  • step S320 the first monitoring parameter is received through the service port; where the service port can be used to receive the first monitoring parameter.
  • the service port can receive one or more servers
  • the health status indicator and the corresponding reference indicator value are not limited to this in this embodiment.
  • step S220 monitor each server health status indicator in the back-end server; wherein, the server health status indicator may include the actual indicator value in the server health status.
  • the server health status indicator may be monitored by monitoring the server health status indicator.
  • the actual index value and the reference index value of each server health status indicator in the back-end server determine the status of the back-end server.
  • the actual index value may refer to the indicator corresponding to the health status indicator of the back-end server in a real-time state.
  • the actual indicator value can be used to measure the service status of the current back-end server of the server.
  • the service status of the current back-end server can be judged by comparing the reference indicator value and the actual indicator value of the back-end server health indicator value.
  • the actual index value of the health status indicator can be obtained by monitoring the service port of the backend server and based on the service port information.
  • step S230 determine the health status of the back-end server according to each server health status indicator; wherein, the back-end server may be determined based on the actual index value and reference index value of each server health status indicator.
  • health status for example, based on the actual index value and reference index value of each server health status index The difference between them can also be determined based on whether the actual indicator value reaches the range of the reference indicator value, thereby determining the health of the backend server.
  • the reference indicator value may include a reference indicator Range; wherein, the reference indicator range is a standard used to measure whether the server is healthy. For example, when the actual indicator value is within the reference indicator range, it is determined that the backend server is healthy; and/or the actual indicator value If it is not within the range of the reference indicators, it is determined that the backend server is unhealthy.
  • the server health status indicator may also include sending a detection behavior through a health check. If the backend server can correctly respond to the detection behavior, it is determined that the server is in a healthy state. For example, a tcp may be initiated. If the connection can be established normally, the detection backend server is considered normal, and this application is not limited to this.
  • step S240 when it is determined that the health status of the back-end server does not meet the preset conditions, a removal request is sent to the load balancing server to remove the back-end server, where the preset conditions may refer to The preset number of actual indicator values does not meet the corresponding reference indicator value standard.
  • the preset number can be two actual indicator values. That is, when more than two actual indicator values do not meet the standard, a removal request is sent to the load balancing server. It is also possible to preset that a certain indicator value does not reach the corresponding reference indicator value and send a removal request to the load balancing server.
  • the back-end server sends a removal request to the load balancing server. This embodiment is not limited to this.
  • the first monitoring parameters are sent to the back-end server to monitor each server health status indicator in the back-end server and determine the health status of the back-end server based on each server health status indicator.
  • the first monitoring parameter can be used to monitor the health of the back-end server, and the first monitoring parameter can include one or more server health status indicators.
  • the first monitoring parameter A monitoring parameter may be a first monitoring script, which is sent to the backend server through the load balancing server, and the health of the server is determined through the first monitoring script; the first monitoring parameter may also be a load The probing behavior sent by the health check of the balanced server determines the health of the server based on whether the backend server can respond correctly to the probing behavior. This embodiment is not limited to this.
  • the first monitoring parameter is sent to the backend server through steps S510 to S520:
  • the load balancing server includes a health check service and obtains health check data corresponding to the health check service; wherein the health check service can send a detection behavior. If the backend server makes a correct response, Then it is determined that the status of the back-end server is normal.
  • the health check can initiate a TCP connection. If the connection can be established normally, it is considered that the back-end server is normal. It can also initiate an http request. If the back-end server can respond normally, then The back-end server is considered normal; the health check service can also be used to send detection messages to the back-end server, and the health status of the back-end server can be determined based on the detection messages.
  • the health check service may also send the first monitoring parameter, and the health check service may also send one or more server health status indicators and corresponding reference indicator values to determine the health status of the server. This embodiment is not limited to this.
  • step S520 send the first monitoring parameter to the backend server according to the health check data; wherein the health check also includes a health check method, a health check period, a health check protocol, a health check domain name, a health check path, and return Status code, etc.
  • the health check service can send the first monitoring parameter to detect the health status of the backend server.
  • the first monitoring parameter can be sent through the health check service, and the first monitoring parameter can be sent according to the health check service.
  • the first monitoring parameter monitors the health status of the backend server.
  • step S420 when receiving the removal request sent by the back-end server whose health condition does not meet the preset conditions, the back-end server is removed; wherein the preset condition may be a preset time, for example, within a preset time , remove the back-end servers that fail to receive the first monitoring parameters sent by the load balancing. In this embodiment, it may also include removing the back-end servers whose actual indicator values are not within the reference indicator range. For example, When the actual index value of the back-end server is not within the reference index range, the back-end server sends a removal request to the load balancing server, and the load balancing server removes the back-end server.
  • the preset condition may be a preset time, for example, within a preset time , remove the back-end servers that fail to receive the first monitoring parameters sent by the load balancing.
  • the back-end server may also include removing the back-end servers whose actual indicator values are not within the reference indicator range. For example, When the actual index value of the back
  • it may also include Determine the backend server that fails to respond correctly to the first monitoring parameter as an abnormal server, and remove the abnormal server. For example, you can initiate a TCP connection. If the connection cannot be established normally, it is considered that the abnormality of the backend server is detected. , and remove it. This embodiment is not limited to this.
  • the first monitoring parameter can be adjusted by receiving a first response operation from the user, where the first response operation includes modifying the health check data
  • the first monitoring parameter may also be deleted by receiving a second response operation from the user, wherein the second response operation includes closing the health check service.
  • the first monitoring parameters sent by the load balancing server can be received, and the first monitoring parameters include one or more server health status indicators; monitoring the Each server health status indicator in the back-end server; determine the health status of the back-end server based on each server health status indicator; when it is determined that the health status of the back-end server does not meet the preset conditions, report to the The load balancing server sends a removal request to remove the backend server.
  • the back-end server detects an abnormality in the deployed service and immediately notifies the load balancer to remove itself.
  • the back-end server's detection of its own service can more truly reflect the availability of the service and does not require waiting for the detection cycle, thus shortening the time for the abnormal server to Removal time; on the other hand, the way the back-end server detects its own services is not affected by external factors, such as network stability, reducing service availability detection errors, thus improving the accuracy of simulated detection.
  • a health check request can be sent to the back-end server 602 according to the load balancing server 601.
  • the health check request There is a certain time interval when continuously sent.
  • the health check request includes sending first monitoring parameters.
  • the first monitoring parameters include one or more server health status indicators and corresponding reference indicator values.
  • the load balancing server 601 can monitor the The actual index value of each server health status indicator in the back-end server 602; in step S604, determine the server based on the actual index value and reference index value of each server health status indicator. If the deployed service is abnormal, in step S605, the service exception request deployed by the server is sent to the load balancing server 601, and the abnormal server is removed through the load balancing server 601.
  • Figure 7 schematically shows a block diagram of a backend server management device according to one embodiment of the present disclosure.
  • a backend server management device 700 includes a receiving module 710 , a monitoring module 720 , a server status determining module 730 , and a request sending module 740 .
  • the receiving module 710 is configured to receive the first monitoring parameters sent by the load balancing server, where the first monitoring parameters include one or more server health status indicators;
  • Monitoring module 720 is used to monitor the health status indicators of each server in the back-end server
  • Determine server status module 730 configured to determine the health status of the back-end server according to each server health status indicator
  • the request sending module 740 is configured to send a removal request to the load balancing server to remove the back-end server when it is determined that the health status of the back-end server does not meet the preset conditions.
  • the receiving module 710 includes:
  • Receiving unit determines the service port of the backend server that the first monitoring parameter matches, and receives the first monitoring parameter through the service port;
  • Monitoring unit monitors the service port and obtains the health status indicator based on the service port.
  • the determining server status module 730 includes:
  • each server health status indicator includes an actual indicator value and a reference indicator value corresponding to the health status; wherein, the reference indicator value includes a reference indicator range, and when the actual indicator value is within the reference indicator range, , then determine the health of the backend server; and/or
  • FIG. 8 schematically shows a block diagram of a backend server management device according to another embodiment of the present disclosure.
  • a backend server management device 800 includes a sending module 810 and a removal module 820 .
  • the sending module 810 is used to send first monitoring parameters to the back-end server, where the first monitoring parameters include one or more server health status indicators, so as to facilitate monitoring of each server health status indicator in the back-end server, And determine the health status of the back-end server based on the health status indicators of each server;
  • the removal module 820 is configured to remove the back-end server when receiving a removal request sent by the back-end server whose health condition does not meet the preset conditions.
  • the sending module 810 includes:
  • the load balancing server includes a health check, obtains health check data corresponding to the health check, and sends the first monitoring parameter to the backend server according to the health check data.
  • Adjusting parameter unit when receiving the user's first response operation, adjust the first monitoring parameter; the first response operation includes modifying the health check data; and/or
  • the second response operation includes closing Close the health check.
  • FIG. 9 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present disclosure.
  • computer system 900 includes a central processing unit (CPU) 901 that can operate according to a program stored in a read-only memory (ROM) 902 or loaded from a storage portion 908 into a random access memory (RAM) 903 And perform various appropriate actions and processing.
  • CPU 901, ROM 902 and RAM 903 are connected to each other through bus 904.
  • An input/output (I/O) interface 905 is also connected to bus 904.
  • the following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., speakers, etc.; and a storage section 908 including a hard disk, etc. ; and a communication section 909 including a network interface card such as a LAN card, a modem, etc.
  • the communication section 909 performs communication processing via a network such as the Internet.
  • Driver 910 is also connected to I/O interface 905 as needed.
  • Removable media 911 such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage portion 908 as needed.
  • embodiments of the present disclosure include a computer program product including a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart.
  • the computer program may be downloaded and installed from the network via communication portion 909 and/or installed from removable media 911 .
  • the computer program is executed by the central processing unit (CPU) 901, various functions defined in the methods and devices of the present application are executed.
  • the computer system 900 may also include an AI (Artificial Intelligence, artificial intelligence) processor, which is used to process computing operations related to machine learning.
  • AI Artificial Intelligence, artificial intelligence
  • the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a touch terminal, a network device, etc.) to execute the method according to the embodiments of the present disclosure.
  • a computing device which may be a personal computer, a server, a touch terminal, a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Debugging And Monitoring (AREA)
  • Computer And Data Communications (AREA)

Abstract

本公开提供一种后端服务器管理方法及装置、电子设备、计算机可读存储介质，上述后端服务器管理方法，包括：接收负载均衡服务器发送的第一监测参数，第一监测参数包括一个或多个服务器健康状态指标；监测后端服务器中各服务器健康状态指标；根据各服务器健康状态指标，确定后端服务器的健康情况；在确定后端服务器健康情况不符合预设条件时，向负载均衡服务器发送摘除请求，以将后端服务器摘除。

Description

后端服务器管理方法、装置、可读介质及电子设备
相关申请的交叉引用
本申请要求于2022年04月20日提交的申请号为202210418100.0、名称为“后端服务器管理方法、装置、可读介质及电子设备”的中国专利申请的优先权，该中国专利申请的全部内容通过引用全部并入本文。
技术领域
本公开涉及负载均衡技术领域，具体而言，涉及一种后端服务器管理方法、装置、电子设备以及计算机可读存储介质。
背景技术
在大流量、高可用业务场景下，客户往往都会部署负载均衡产品，负载均衡产品可以定期探测各后端服务器的健康状况。
举例而言，负载均衡可以通过定期发送探测报文检查后端服务器可用性，在后端服务器服务异常的情况下，需要等待多个探测周期，才能将异常后端服务器摘除。
发明内容
根据本公开的第一方面，提供一种后端服务器管理方法，应用于后端服务器，包括：
接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；
监测所述后端服务器中各所述服务器健康状态指标；
根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除；
确定所述第一监测参数匹配的后端服务器的服务端口，并通过所述服务端口接收所述第一监测参数；
监测所述服务端口，并通过所述服务端口获取所述健康状态指标；
各所述服务器健康状态指标包括健康状态对应的实际指标值及参考指标值；其中，所述参考指标值包括参考指标范围；
所述实际指标值在所述参考指标范围内时，则确定后端服务器健康；和/或
所述实际指标值不在所述参考指标范围内时，则确定后端服务器不健康。
根据本公开的第二方面，提供一种后端服务器管理方法，应用于负载均衡服务器；包括：
向后端服务器发送第一监测参数，以便于监测所述后端服务器中各所述服务器健康状 态指标及根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除；
所述负载均衡服务器包括健康检查服务，并获取所述健康检查服务中对应的健康检查数据；
根据所述健康检查数据向后端服务器发送第一监测参数；
在接收到用户的第一响应操作时，调整所述第一监测参数；所述第一响应操作包括修改所述健康检查数据；和/或
在接收到用户的第二响应操作时，删除所述第一监测参数；所述第二响应操作包括关闭所述健康检查服务。
根据本公开的第三方面，提供一种后端服务器管理装置，应用于后端服务器，包括：
接收模块，用于接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标以及对应的参考指标值；
监测模块，用于监测所述后端服务器中各所述服务器健康状态指标的实际指标值；
确定服务器状态模块，用于根据各所述服务器健康状态指标的实际指标值和参考指标值，确定所述后端服务器的健康情况；
请求发送模块，用于在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。
根据本公开的第四方面，提供一种后端服务器管理装置，应用于负载均衡服务器，包括：
发送模块，用于向后端服务器发送第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标，以便于监测所述后端服务器中各所述服务器健康状态指标及根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
摘除模块，用于在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除。
根据本公开的第五方面，提供一种电子设备，包括：处理器；以及存储器，用于存储所述处理器的可执行指令；其中，所述处理器配置为经由执行所述可执行指令来执行上述任意一项所述的方法。
根据本公开的第六方面，提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任意一项所述的方法。
附图说明
图1示出了可以应用本公开实施例的一种后端服务器管理装置的示例性系统架构的示意图；
图2示意性示出了根据本公开的一个实施例的后端服务器管理方法的流程图；
图3示意性示出了根据本公开的一个实施例中接收第一监测参数的流程图；
图4示意性示出了根据本公开的一个实施例中请求摘除后端服务器的流程图；
图5示意性示出了根据本公开的一个实施例中发送第一监测参数的流程图；
图6示意性示出了根据本公开的一个实施例中后端服务器管理方法展示图；
图7示意性示出了根据本公开的一个实施例中后端服务器装置的框图；
图8示意性示出了根据本公开的一个实施例中后端服务器装置的框图；
图9示意性示出了适于用来实现本公开实施例的电子设备的计算机系统的结构示意图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本公开将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施方式中。在下面的描述中，提供许多具体细节从而给出对本公开的实施方式的充分理解。然而，本领域技术人员将意识到，可以实践本公开的技术方案而省略所述特定细节中的一个或更多，或者可以采用其它的方法、组元、装置、步骤等。在其它情况下，不详细示出或描述公知技术方案以避免喧宾夺主而使得本公开的各方面变得模糊。
此外，附图仅为本公开的示意性图解，并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
图1示出了可以应用本公开实施例的一种后端服务器管理方法及装置的示例性应用环境的系统架构的示意图。
如图1所示，系统架构100可以包括终端设备101、102、103中的一个或多个，网络104和服务器105。网络104用以在终端设备101、102、103和服务器105之间提供通信链路的介质。网络104可以包括各种连接类型，例如有线、无线通信链路或者光纤电缆等等。终端设备101、102、103可以是具有显示屏的各种电子设备，包括但不限于台式计算机、便携式计算机、智能手机和平板电脑等等。应该理解，图1中的终端设备、网络和服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的终端设备、网络和服务器。比如服务器105可以是多个服务器组成的服务器集群等。
本公开实施例所提供的后端服务器管理方法可以在服务器105执行，相应的，后端服务器管理装置一般设置于服务器105中。本公开实施例所提供的后端服务器管理方法也可以由终端设备101、102、103执行，相应的，后端服务器管理装置也可以设置于终端设备101、102、103中，本示例性实施例中对此不做特殊限定。
举例而言，在一种示例性实施例中，服务器105可以接收负载均衡服务器发送的第一 监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；监测所述后端服务器中各所述服务器健康状态指标；根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除；上述应用场景仅是用于举例，本示例性实施例中并不以此为限。
以下对本公开实施例的技术方案的实现细节进行详细阐述：
图2示意性示出了根据本公开的一个实施例的后端服务器管理方法的流程图，该后端服务器管理方法适用于前述实施例中所述的电子设备。参照图2所示，该后端服务器管理方法至少包括步骤S210至步骤S240，详细介绍如下：
步骤S210，接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；
步骤S220，监测所述后端服务器中各所述服务器健康状态指标；
步骤S230，根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
步骤S240，在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。
在本示例实施方式所提供的后端服务器管理方法中，一方面，后端服务器检测到部署的服务异常，立即通知负载均衡将自己摘除，后端服务器对自身服务的探测更能真实反映服务的可用性、同时不需要等待探测周期，从而缩短了异常服务器的摘除时间；另一方面，后端服务器对自身服务的探测的方式不受外部因素影响，例如，网络稳定性的影响，减少了服务可用性探测误差，从而提高了模拟探测的准确率。
下面，在另一实施例中，对上述步骤进行更加详细的说明。
在步骤S210中，接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；其中，所述第一监测参数可以用来监测后端服务器的健康情况，举例而言，第一监测参数可以是端口数据，在本实施例中，所述第一监测参数还可以是监测脚本，例如，后端服务器可以依据第一监测脚本中的配置参数，监测指定服务的可用状态，举例而言，可以通过第一监测脚本中的一个或多个服务器健康状态指标以及对应的参考指标值，确定后端服务器的健康情况，其中，服务器健康状态指标可以包括对服务器健康现象的实际测量，用来从某一方面或者某一侧面反映服务器的健康状况，例如，服务器健康状态指标可以是指服务器健康性能指标，也可以是指服务器健康技术指标，在本实施例中，还可以通过参考指标值反映服务器的健康状态指标，即可以理解为，用参数值形式表示服务器的健康状态指标；其中，参考指标值可以是用来衡量服务器是否处于健康状态的标准，参考指标值还可以具有参考指标范围，举例而言，在本实施例中，若所述服务器当前指标值在对应服务器的参考指标值范围内，则确定所述服务器服务健康，可以理解的是，参考指标值是后端服务器健康状态指标所对应的指标值，在本实施例中，负载均衡服务器发送的第一脚本参数可以是一个或多个服务器健康状态指标以及与一个或多 个服务器健康状态指标的参考指标值，本实施例中并不以此为限。
在本申请另一实施例中，所述健康指标也可以包括，若后端服务器可以正确响应探测行为，则确定服务器达到健康指标要求，举例而言，通过健康检查发送一个探测行为，若后端服务器做出正确应答，则确定对应的后端服务器健康；其中，所述后端服务器的应答可以包括针对所述探测行为，例如：可以是发起一个tcp(Transmission Control Protocol，传输控制协议)连接，连接可正常建立就认为探测后端服务器正常；还可以是发起一次http(Hyper Text Transfer Protocol，超文本传输协议)请求，在后端服务器可以正常应答时，则认为后端服务器正常，在本实施例中并不以此为限。
举例而言，在本实施例中，还可以参考图3所示，通过下述步骤S310至步骤S320向所述后端服务器发送第一监测参数：
在步骤S310中，确定所述第一监测参数匹配的后端服务器的服务端口；其中，后端服务器可以包括多个服务端口，通过确定与第一监测参数匹配的服务端口的信息，可以用来比对后端服务器的各项指标值，服务端口的信息可以包括后端服务器的健康状态指标信息，例如，后端服务器健康状态指标的实际指标值和参考指标值，举例而言，在本实施例中，服务端口可以比对各所述服务器健康状态指标的实际指标值和参考指标值，所述服务端口还可以接收第一监测参数；在本申请另一实施例中，所述服务端口可以接收健康检查发送的一个探测行为，并且还可以通过所述服务端口对所述探测行为做出正确的响应，同时可以根据服务端口接收的信息来判断后端服务器的健康状况，例如，可以发起一个tcp连接，根据所述服务端口接收tcp连接，若连接可正常建立，则认为探测后端服务器正常，还可以发起一次http请求，通过所述服务端口接收所述http请求，若后端服务器可正常应答，则认为后端服务器正常，在本申请实施例中并不以此为限。
在步骤S320中，通过所述服务端口接收所述第一监测参数；其中，服务端口可以用来接收第一监测参数，举例而言，在本实施例中，服务端口可以接收一个或多个服务器健康状态指标以及对应的参考指标值，本实施例中并不以此为限。
在步骤S220中，监测所述后端服务器中各所述服务器健康状态指标；其中，所述服务器健康状态指标可以包括服务器健康状态下的实际指标值，在本实施例中，可以通过监测所述后端服务器中各所述服务器健康状态指标的实际指标值和参考指标值，确定后端服务器的状态，所述实际指标值可以是指在实时状态下，后端服务器的健康状态指标对应的指标值，实际指标值可以用来衡量服务器当前后端服务器的服务状态，例如，可以通过对比后端服务器健康指标值的参考指标值和实际指标值，判断当前后端服务器的服务状态，在本实施例中，可以通过监测所述后端服务器的服务端口，并根据所述服务端口信息获取所述健康状态指标的实际指标值。
在步骤S230中，根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；其中，可以根据各所述服务器健康状态指标的实际指标值和参考指标值，确定所述后端服务器的健康情况，例如，可以根据各所述服务器健康状态指标的实际指标值和参考指标值 之间的差异性，也可以根据实际指标值是否达到参考指标值的范围，从而确定所述后端服务器的健康情况，举例而言，在本实施例中，所述参考指标值可以包括参考指标范围；其中，所述参考指标范围是用来衡量服务器是否健康的标准，例如，所述实际指标值在所述参考指标范围内时，则确定后端服务器健康；和/或所述实际指标值不在所述参考指标范围内时，则确定后端服务器不健康。
在本申请另一实施例中，所述服务器健康状态指标还可以包括通过健康检查发送一个探测行为，若后端服务器可以正确应答该探测行为，则确定服务器处于健康状态，例如，可以发起一个tcp连接，若连接可正常建立，则认为探测后端服务器正常，在本申请中并不以此为限。
在步骤S240中，在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除，其中，所述预设条件可以是指预设数量的实际指标值没有达到对应的参考指标值标准，例如，预设数量可以为两项实际指标值，即超过两项实际指标值不达标时，向所述负载均衡服务器发送摘除请求，也可以是预设某一指标值没有达到对应的参考指标值，向所述负载均衡服务器发送摘除请求，举例而言，在本实施例中，还可以包括将实际指标值不在所述参考指标范围内的后端服务器摘除，例如，后端服务器的实际指标值不在所述参考指标范围内时，后端服务器向负载均衡服务器发送摘除请求，本实施例并不以此为限制。
在本实施例中，还提出了另一种后端服务器管理方法，应用于负载均衡服务器，参考图4所示，通过下述步骤S410至S420摘除后端异常服务器：
在步骤S410中，向后端服务器发送第一监测参数，以便于监测所述后端服务器中各所述服务器健康状态指标及根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；其中，所述第一监测参数可以用来监测后端服务器的健康情况，所述第一监测参数可以包括一个或多个服务器健康状态指标，举例而言，在本实施例中，所述第一监测参数可以是第一监测脚本，通过所述负载均衡服务器向后端服务器发送第一监测脚本，并通过所述第一监测脚本确定服务器的健康情况；所述第一监测参数还可以是负载均衡服务器的健康检查发送的探测行为，根据后端服务器能否正确响应所述探测行为，确定服务器的健康情况，本实施例并不以此为限制。
在本实施例中，还可以参考图5所示，通过步骤S510至步骤S520向后端服务器发送第一监测参数：
在步骤S510中，所述负载均衡服务器包括健康检查服务，获取所述健康检查服务对应的健康检查数据；其中，所述健康检查服务可以发送一个探测行为，若后端服务器做出正确的响应，则确定后端服务器状态正常，例如，所述健康检查可以发起一个tcp连接，若连接可正常建立，则认为探测后端服务器正常，还可以发起一次http请求，若后端服务器可正常应答，则认为后端服务器正常；所述健康检查服务还可以用来向后端服务器发送探测报文，根据探测报文可以判断后端服务器的健康情况，在本实施例中，健康检查服 务也可以发送第一监测参数，健康检查服务还可以发送一个或多个服务器健康状态指标以及对应的参考指标值，确定服务器的健康状态，在本实施例中并不以此为限。
在步骤S520中，根据所述健康检查数据向后端服务器发送第一监测参数；其中，所述健康检查还包括健康检查方法、健康检查周期、健康检查协议、健康检查域名、健康检查路径、返回状态码等等，所述健康检查服务可以发送第一监测参数，用来探测后端服务器健康情况，举例而言，在本实施例中，可以通过健康检查服务发送第一监测参数，并根据所述第一监测参数监测后端服务器的健康状态。
在步骤S420中，在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除；其中，预设条件可以是预设时间，例如，在预设时间内，将未能接收到负载均衡发送的第一监测参数的后端服务器摘除，在本实施例中，还可以包括将实际指标值不在所述参考指标范围内的后端服务器摘除，举例而言，后端服务器的实际指标值不在所述参考指标范围内时，后端服务器向负载均衡服务器发送摘除请求，负载均衡服务器将所述后端服务器摘除，在本申请另一实施例中，也可以包括将未能正确响应第一监测参数的后端服务器，确定为异常服务器，并将所述异常服务器摘除，举例而言，可以发起一个tcp连接，若连接不能正常建立，则认为探测后端服务器异常，并将其摘除，本实施例并不以此为限制。
基于前述实施例的技术方案，在本公开的一个实施例中，可以通过接收到用户的第一响应操作，调整所述第一监测参数，所述第一响应操作包括修改所述健康检查数据，还可以通过接收用户的第二响应操作，删除所述第一监测参数，其中，所述第二响应操作包括关闭所述健康检查服务。
综上，在本公开示例实施方式所提供的后端服务器管理方法中，可以接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；监测所述后端服务器中各所述服务器健康状态指标；根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。一方面，后端服务器检测到部署的服务异常，立即通知负载均衡将自己摘除，后端服务器对自身服务的探测更能真实反映服务的可用性、同时不需要等待探测周期，从而缩短了异常服务器的摘除时间；另一方面，后端服务器对自身服务的探测的方式不受外部因素影响，例如，网络稳定性的影响，减少服务可用性探测误差，从而提高了模拟探测的准确率。
在本方案的另一实施例中，可以参考图6对上述后端服务器管理方法进一步说明：在步骤S603中，可以根据负载均衡服务器601向后端服务器602发送健康检查请求，所述健康检查请求连续发送时存在一定时间间隔，所述健康检查请求包括发送第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标以及对应的参考指标值，负载均衡服务器601可以监测所述后端服务器602中各所述服务器健康状态指标的实际指标值；在步骤S604中，根据各所述服务器健康状态指标的实际指标值和参考指标值，确定服务器 部署的服务异常，在步骤S605中，将所述服务器部署的服务异常请求发送至负载均衡服务器601，通过负载均衡服务器601将异常服务器摘除。
图7示意性示出了根据本公开的一个实施例的后端服务器管理装置的框图。
参照图7所示，根据本公开的一个实施例的后端服务器管理装置700，包括接收模块710、监测模块720、确定服务器状态模块730，以及请求发送模块740。
其中接收模块710，用于接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；
监测模块720，用于监测所述后端服务器中各所述服务器健康状态指标；
确定服务器状态模块730，用于根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
请求发送模块740，用于在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。
在本公开的一种示例性实施例中，所述接收模块710包括：
接收单元：确定所述第一监测参数匹配的后端服务器的服务端口，并通过所述服务端口接收所述第一监测参数；
监测单元：监测所述服务端口，并基于所述服务端口获取所述健康状态指标。
在本公开的一种示例性实施例中，所述确定服务器状态模块730包括：
确定服务器状态单元：各所述服务器健康状态指标包括健康状态对应的实际指标值及参考指标值；其中，所述参考指标值包括参考指标范围，所述实际指标值在所述参考指标范围内时，则确定后端服务器健康；和/或
所述实际指标值不在所述参考指标范围内时，则确定后端服务器不健康。
图8示意性示出了根据本公开的另一个实施例的后端服务器管理装置的框图。
参照图8所示，根据本公开的一个实施例的后端服务器管理装置800，包括发送模块810、摘除模块820。
其中发送模块810，用于向后端服务器发送第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标，以便于监测所述后端服务器中各所述服务器健康状态指标，并根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
摘除模块820，用于在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除。
在本公开的一种示例性实施例中，所述发送模块810包括：
发送单元：所述负载均衡服务器包括健康检查，并获取所述健康检查对应的健康检查数据，根据所述健康检查数据向后端服务器发送第一监测参数。
调整参数单元：在接收到用户的第一响应操作时，调整所述第一监测参数；所述第一响应操作包括修改所述健康检查数据；和/或
在接收到用户的第二响应操作时，删除所述第一监测参数；所述第二响应操作包括关 闭所述健康检查。
图9示出了适于用来实现本公开实施例的电子设备的计算机系统的结构示意图。
需要说明的是，图9示出的电子设备的计算机系统900仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图9所示，计算机系统900包括中央处理单元(CPU)901，其可以根据存储在只读存储器(ROM)902中的程序或者从存储部分908加载到随机访问存储器(RAM)903中的程序而执行各种适当的动作和处理。在RAM 903中，还存储有系统操作所需的各种程序和数据。CPU 901、ROM 902以及RAM 903通过总线904彼此相连。输入/输出(I/O)接口905也连接至总线904。
以下部件连接至I/O接口905：包括键盘、鼠标等的输入部分906；包括诸如阴极射线管(CRT)、液晶显示器(LCD)等以及扬声器等的输出部分907；包括硬盘等的存储部分908；以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分909。通信部分909经由诸如因特网的网络执行通信处理。驱动器910也根据需要连接至I/O接口905。可拆卸介质911，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器910上，以便于从其上读出的计算机程序根据需要被安装入存储部分908。
特别地，根据本公开的实施例，下文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分909从网络上被下载和安装，和/或从可拆卸介质911被安装。在该计算机程序被中央处理单元(CPU)901执行时，执行本申请的方法和装置中限定的各种功能。在一些实施例中，计算机系统900还可以包括AI(Artificial Intelligence，人工智能)处理器，该AI处理器用于处理有关机器学习的计算操作。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本公开实施方式的方法。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。本公开的范围仅由所附的权利要求来限制。

Claims (11)

  1. 一种后端服务器管理方法，应用于后端服务器；其中，所述方法包括：
    接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；
    监测所述后端服务器中各所述服务器健康状态指标；
    根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
    在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。
  2. 根据权利要求1所述的后端服务器管理方法，其中，所述接收负载均衡服务器发送的第一监测参数，包括：
    确定所述第一监测参数匹配的后端服务器的服务端口，并通过所述服务端口接收所述第一监测参数。
  3. 根据权利要求2所述的后端服务器管理方法，其中，所述通过所述服务端口接收所述第一监测参数，包括：
    监测所述服务端口，并通过所述服务端口获取所述健康状态指标。
  4. 根据权利要求1所述的后端服务器管理方法，其中，所述根据各所述服务器健康状态指标，确定所述后端服务器的健康情况，包括：
    各所述服务器健康状态指标包括健康状态对应的实际指标值及参考指标值；其中，所述参考指标值包括参考指标范围；
    所述实际指标值在所述参考指标范围内时，则确定后端服务器健康；和/或
    所述实际指标值不在所述参考指标范围内时，则确定后端服务器不健康。
  5. 一种后端服务器管理方法，应用于负载均衡服务器；其中，所述方法包括：
    向后端服务器发送第一监测参数，以便于监测所述后端服务器中各所述服务器健康状态指标及根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
    在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除。
  6. 根据权利要求5所述的后端服务器管理方法，其中，所述向后端服务器发送第一监测参数，包括：
    所述负载均衡服务器包括健康检查服务，并获取所述健康检查服务对应的健康检查数据；
    根据所述健康检查数据向后端服务器发送第一监测参数。
  7. 根据权利要求6所述的后端服务器管理方法，其中，所述方法还包括：
    在接收到用户的第一响应操作时，调整所述第一监测参数；所述第一响应操作包括修改所述健康检查数据；和/或
    在接收到用户的第二响应操作时，删除所述第一监测参数；所述第二响应操作包括关 闭所述健康检查服务。
  8. 一种后端服务器管理装置，应用于后端服务器；其中，包括：
    接收模块，用于接收负载均衡服务器发送的第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标；
    监测模块，用于监测所述后端服务器中各所述服务器健康状态指标；
    确定服务器状态模块，用于根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
    请求发送模块，用于在确定所述后端服务器健康情况不符合预设条件时，向所述负载均衡服务器发送摘除请求，以将所述后端服务器摘除。
  9. 一种后端服务器管理装置，应用于负载均衡服务器；其中，包括：
    发送模块，用于向后端服务器发送第一监测参数，所述第一监测参数包括一个或多个服务器健康状态指标，以便于监测所述后端服务器中各所述服务器健康状态指标及根据各所述服务器健康状态指标，确定所述后端服务器的健康情况；
    摘除模块，用于在接收到后端服务器健康情况不符合预设条件发送的摘除请求时，将所述后端服务器摘除。
  10. 一种计算机可读介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至7中任一项所述的方法。
  11. 一种电子设备，其中，包括：
    处理器；以及
    存储器，用于存储所述处理器的可执行指令；
    其中，所述处理器配置为经由执行所述可执行指令来执行权利要求1-7任一项所述的方法。
PCT/CN2023/074304 2022-04-20 2023-02-02 后端服务器管理方法、装置、可读介质及电子设备 WO2023202182A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210418100.0 2022-04-20
CN202210418100.0A CN114938377B (zh) 2022-04-20 2022-04-20 后端服务器管理方法、装置、可读介质及电子设备

Publications (1)

Publication Number Publication Date
WO2023202182A1 true WO2023202182A1 (zh) 2023-10-26

Family

ID=82862825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/074304 WO2023202182A1 (zh) 2022-04-20 2023-02-02 后端服务器管理方法、装置、可读介质及电子设备

Country Status (2)

Country Link
CN (1) CN114938377B (zh)
WO (1) WO2023202182A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114938377B (zh) * 2022-04-20 2024-05-17 京东科技信息技术有限公司 后端服务器管理方法、装置、可读介质及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170208122A1 (en) * 2016-01-18 2017-07-20 Canon Kabushiki Kaisha Server system, method for controlling server system, and storage medium
CN110602169A (zh) * 2019-08-13 2019-12-20 上海陆家嘴国际金融资产交易市场股份有限公司 服务调用方法、装置、计算机设备和存储介质
CN110912779A (zh) * 2019-12-05 2020-03-24 苏州浪潮智能科技有限公司 一种集群主机健康检测方法，系统，设备及可读存储介质
CN113127201A (zh) * 2021-04-23 2021-07-16 中国工商银行股份有限公司 故障应用服务器隔离方法及装置、电子设备和存储介质
CN114938377A (zh) * 2022-04-20 2022-08-23 京东科技信息技术有限公司 后端服务器管理方法、装置、可读介质及电子设备

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7313735B1 (en) * 2004-04-30 2007-12-25 Sun Microsystems, Inc. In-line server health checking
US8239535B2 (en) * 2005-06-06 2012-08-07 Adobe Systems Incorporated Network architecture with load balancing, fault tolerance and distributed querying
US10505818B1 (en) * 2015-05-05 2019-12-10 F5 Networks. Inc. Methods for analyzing and load balancing based on server health and devices thereof
CN106302595B (zh) * 2015-06-02 2020-03-17 阿里巴巴集团控股有限公司 一种对服务器进行健康检查的方法及设备
WO2018107382A1 (zh) * 2016-12-14 2018-06-21 华为技术有限公司 分布式负载均衡系统、健康检查方法和服务节点
CN110177028B (zh) * 2019-05-30 2021-06-22 北京字节跳动网络技术有限公司 分布式健康检查方法及装置
CN110311988B (zh) * 2019-07-30 2022-01-28 中国工商银行股份有限公司 后端服务器的健康检查方法、负载均衡方法及装置
CN110581855B (zh) * 2019-09-12 2021-11-09 中国工商银行股份有限公司 应用控制方法、装置、电子设备和计算机可读存储介质
CN113051143A (zh) * 2019-12-27 2021-06-29 中国移动通信集团湖南有限公司 服务负载均衡服务器的探测方法、装置、设备和存储介质
CN111556125B (zh) * 2020-04-24 2022-05-17 北京奇艺世纪科技有限公司 一种访问请求分配方法、负载均衡设备及电子设备
CN111813625B (zh) * 2020-06-30 2024-03-08 中国工商银行股份有限公司 分布式服务器集群的健康检查方法及装置
CN112738238A (zh) * 2020-12-29 2021-04-30 北京天融信网络安全技术有限公司 一种负载均衡中健康检查的方法、装置以及系统
CN112882895A (zh) * 2021-02-22 2021-06-01 中国工商银行股份有限公司 健康检查方法、装置、计算机系统及可读存储介质
CN113824768B (zh) * 2021-08-23 2022-11-15 北京天融信网络安全技术有限公司 负载均衡系统中的健康检查方法及装置和流量转发方法
CN115190047B (zh) * 2022-02-10 2023-07-07 统信软件技术有限公司 一种服务器健康监测方法、系统及计算设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170208122A1 (en) * 2016-01-18 2017-07-20 Canon Kabushiki Kaisha Server system, method for controlling server system, and storage medium
CN110602169A (zh) * 2019-08-13 2019-12-20 上海陆家嘴国际金融资产交易市场股份有限公司 服务调用方法、装置、计算机设备和存储介质
CN110912779A (zh) * 2019-12-05 2020-03-24 苏州浪潮智能科技有限公司 一种集群主机健康检测方法，系统，设备及可读存储介质
CN113127201A (zh) * 2021-04-23 2021-07-16 中国工商银行股份有限公司 故障应用服务器隔离方法及装置、电子设备和存储介质
CN114938377A (zh) * 2022-04-20 2022-08-23 京东科技信息技术有限公司 后端服务器管理方法、装置、可读介质及电子设备

Also Published As

Publication number Publication date
CN114938377B (zh) 2024-05-17
CN114938377A (zh) 2022-08-23

Similar Documents

Publication Publication Date Title
KR102158754B1 (ko) 스마트 네트워크 인터페이스 카드의 조작 방법 및 조작 장치
US9384114B2 (en) Group server performance correction via actions to server subset
US10223145B1 (en) System for impairment issues of distributed hosts
US9058229B2 (en) Method and apparatus for maintaining operability with a cloud computing environment
US10204004B1 (en) Custom host errors definition service
US10802847B1 (en) System and method for reproducing and resolving application errors
WO2023202182A1 (zh) 后端服务器管理方法、装置、可读介质及电子设备
US20190121717A1 (en) Dynamic, crowd-sourced error and crash resolution for computer programs
WO2016197737A1 (zh) 自检处理方法、装置及系统
EP3908933A1 (en) Test result triage for a failed code validation
CN109324968B (zh) 一种系统测试方法及装置
CN110647335A (zh) 软件灰度发布方法、装置、电子设备及存储介质
US20150067139A1 (en) Agentless monitoring of computer systems
CN112395194B (zh) 一种接入测试平台的方法和装置
WO2022147563A1 (en) Sender policy framework (spf) configuration validator and security examinator
US10380339B1 (en) Reactively identifying software products exhibiting anomalous behavior
EP4222599A1 (en) Methods and systems for multi-resource outage detection for a system of networked computing devices and root cause identification
US10649869B2 (en) Burn process data retrieval and notification
CN111737129A (zh) 服务控制方法、装置、计算机可读介质及电子设备
CN113434384A (zh) 一种压力测试方法和装置
CN113010365A (zh) 系统运行状态的监控方法、检测方法、装置、电子设备及存储介质
US11579954B2 (en) Data collecting in issue tracking systems
CN112749073B (zh) 业务测试方法、装置、存储介质及电子设备
US20200387436A1 (en) Failure detection system and non-transitory computer-readable recording medium storing failure detection program
CN115686911A (zh) 服务端自检方法、装置、电子设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23790846

Country of ref document: EP

Kind code of ref document: A1