Distributed server service degradation method, device, electronic device and medium

Abstract

The present disclosure provides a method, device, electronic device and readable storage medium for downgrading the service of a distributed server, which can be applied to the financial field or other fields. The method for downgrading the service includes: obtaining the service types of M nodes of the distributed server, the service type has N service attributes, and the N service attributes of each service type have different weights, wherein M and N are positive integers greater than 1; analyzing the service type and the service attribute by a hierarchical analysis method to obtain a first weight ranking of the service type; obtaining the rated load threshold of the data request of the distributed server, comparing the current load threshold with the rated load threshold, and starting the service downgrading when the current load threshold is greater than the rated load threshold; downgrading the server of the node corresponding to the service type according to the first weight ranking to reject the data request received in the current time period.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and more specifically, to a service degradation method, device, electronic device, and computer-readable storage medium of a distributed server. Background Art

[0002] With the development of information technology, the amount of information data that servers need to process is increasing. When the pressure on the server increases dramatically, some services and pages are strategically not processed or processed in a simpler way according to the actual business situation and traffic, thereby releasing server resources to ensure the normal or efficient operation of core transactions. In the related technology, a distributed switch is set in the distributed system to achieve service downgrade. During the downgrade process, the server processes different service types, and because the load pressure of the server corresponding to different service types is different, it is impossible to use effective downgrade methods for different service types. Especially in large promotions or flash sales, the load pressure of the server increases dramatically. When it is impossible to downgrade according to the service type, it is easy to cause the server to crash, reducing the user experience. Summary of the invention

[0003] In view of this, the present disclosure provides a service downgrading method, device, electronic device and computer-readable storage medium for a distributed server, which can downgrade different servers according to service types, effectively reduce the load pressure of the server, and provide users with a better experience when the load pressure is high.

[0004] A first aspect of the present disclosure provides a method for service degradation of a distributed server, comprising: obtaining service types of M nodes of a distributed server, the service type having N service attributes, the N service attributes of each service type having different weights, wherein M and N are positive integers greater than 1; analyzing the service type and the service attributes by a hierarchical analysis method to obtain a first weight ranking of the service type; obtaining a rated load threshold of a data request of the distributed server, comparing a current load threshold with the rated load threshold, and initiating service degradation when the current load threshold is greater than the rated load threshold; and downgrading the server of the node corresponding to the service type according to the first weight ranking to reject the data request received within a current time period.

[0005] In some embodiments of the present disclosure, the service type and the service attribute are analyzed by a hierarchical analysis method to obtain a first weight ranking of the service type, including: establishing a hierarchical analysis model, the hierarchical analysis model includes a highest layer, a middle layer and a lowest layer, the middle layer includes the service attributes, and the lowest layer includes the service type; constructing a comparison matrix and a hierarchical single ranking of the lowest layer and the middle layer, and performing a consistency check on the comparison matrix; constructing a hierarchical total ranking, and performing a consistency check to generate a first weight ranking of the service type.

[0006] In some embodiments of the present disclosure, downgrading the server of the node corresponding to the service type according to the first weight sorting includes: generating a downgrade instruction according to the first weight sorting; receiving the downgrade instruction, checking whether the downgrade status of the target server to be downgraded is turned on; if the downgrade status of the target server is turned on, rejecting the downgrade instruction; if the downgrade status of the target server is turned off, receiving the downgrade instruction, and downgrading the target server.

[0007] In some embodiments of the present disclosure, receiving the downgrade instruction and downgrading the target server includes: receiving the downgrade instruction, the target server executing the downgrade instruction, and counting the time interval between the downgrade start time and the current time interval of the target server; if the time interval is less than the set interval, rejecting the data request from the user; if the time interval is not less than the set interval, sending the time interval to the control center.

[0008] In some embodiments of the present disclosure, after sending the time interval to the control center, the service degradation method also includes: obtaining server attributes of the servers of the M nodes; calculating the current load bearing value of the M nodes based on the server attributes; comparing the current load bearing value with a set threshold; if the load bearing value is greater than the set threshold, rejecting the data request from the user; if the load bearing value is not greater than the set threshold, receiving the data request from the user, and setting the degradation status of the target server to closed.

[0009] In some embodiments of the present disclosure, after the load bearing value is greater than the set threshold and the data request from the user is rejected, it also includes counting the number of rejections of the data request and generating a priority downgrade strategy according to the number of rejections.

[0010] In some embodiments of the present disclosure, the server attributes include CPU usage, storage usage, and memory usage.

[0011] In some embodiments of the present disclosure, the service attributes include: two or more of: critical path degree level, current number of users, network transmission data volume, configured flow limiting level, service usage frequency, and service security level.

[0012] A second aspect of an embodiment of the present disclosure provides a service degradation device for a distributed server, comprising: an acquisition module, configured to acquire service types of M nodes of a distributed server, the service type having N service attributes, the N service attributes of each service type having different weights, wherein M and N are positive integers greater than 1; an analysis module, configured to analyze the service type and the service attributes through a hierarchical analysis method to acquire a first weight ranking of the service type; a processing module, configured to acquire a rated load threshold of a data request of the distributed server, compare a current load threshold with the rated load threshold, and initiate service degradation when the current load threshold is greater than the rated load threshold; a degradation module, configured to downgrade the server of the node corresponding to the service type according to the first weight ranking to reject the data request received within a current time period.

[0013] In some embodiments of the present disclosure, the analysis module includes an analysis submodule, and the analysis submodule is configured to establish a hierarchical analysis model, the hierarchical analysis model includes a highest layer, a middle layer and a lowest layer, the middle layer includes the service attributes, and the lowest layer includes the service type; construct a comparison matrix and a hierarchical single ranking of the lowest layer and the middle layer, and perform a consistency check on the comparison matrix; construct a hierarchical total ranking, and perform a consistency check to generate a first weight ranking of the service type.

[0014] In some embodiments of the present disclosure, the downgrade module includes a downgrade sub-module, and the downgrade sub-module is configured to generate a downgrade instruction according to the first weight ranking; receive the downgrade instruction, and check whether the downgrade status of the target server to be downgraded is turned on; if the downgrade status of the target server is turned on, reject the downgrade instruction; if the downgrade status of the target server is turned off, receive the downgrade instruction and downgrade the target server.

[0015] In some embodiments of the present disclosure, the downgrade submodule also includes a statistical module, which is configured to receive the downgrade instruction, the target server executes the downgrade instruction, and counts the downgrade start time and current time interval of the target server; if the time interval is less than the set interval, reject the data request from the user; if the time interval is not less than the set interval, send the time interval to the control center.

[0016] In some embodiments of the present disclosure, the service degradation device also includes a comparison module, which is configured to obtain server attributes of the servers of the M nodes after sending the time interval to the control center; calculate the current load bearing value of the M nodes based on the server attributes; compare the current load bearing value with a set threshold, and if the load bearing value is greater than the set threshold, reject the data request from the user; if the load bearing value is not greater than the set threshold, receive the data request from the user and set the degradation status of the target server to closed.

[0017] A third aspect of an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; and a storage device for storing executable instructions, wherein when the executable instructions are executed by the processors, the service degradation method described above is implemented.

[0018] A fourth aspect of an embodiment of the present disclosure provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, implements the service degradation method described above.

[0019] A fifth aspect of an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the service degradation method described above when executed by a processor.

[0020] According to the service downgrade method of the embodiment of the present invention, a first weight ranking of service types of different nodes can be obtained by adopting a hierarchical analysis method, and the server of the node can be downgraded according to the first weight ranking, thereby ensuring that when the load pressure is high during the current time period, unimportant services are downgraded first to improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0022] Figure 1 The application scenario of the service degradation method of the distributed server according to the embodiment of the present disclosure is schematically shown;

[0023] Figure 2 A flowchart of a service degradation method according to an embodiment of the present disclosure is schematically shown;

[0024] Figure 3 A flowchart schematically shows a first weight ranking of service types obtained in a service degradation method according to an embodiment of the present disclosure;

[0025] Figure 4A flowchart of downgrading a node server according to a service downgrading method according to an embodiment of the present disclosure is schematically shown;

[0026] Figure 5 A flowchart of downgrading a target server according to a service downgrading method according to an embodiment of the present disclosure is schematically shown;

[0027] Figure 6 Schematically shows a flow chart of the service degradation method according to an embodiment of the present disclosure after the time interval is sent to the control center;

[0028] Figure 7 A block diagram of a service degradation device according to an embodiment of the present disclosure is schematically shown;

[0029] Figure 8 A block diagram of an electronic device suitable for implementing a service degradation method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0030] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0031] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0032] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0033] When using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted according to the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). Those skilled in the art should also understand that any transitional conjunctions and / or phrases that essentially represent two or more optional items, whether in the specification, claims, or drawings, should be understood to give the possibility of including one of these items, either of these items, or both of these items. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B", or "A and B".

[0034] An embodiment of the present disclosure provides a service degradation method for a distributed server, comprising: obtaining service types of M nodes of a distributed server, the service type having N service attributes, the N service attributes of each of the service types having different weights, and M and N being positive integers greater than 1; analyzing the service types and the service attributes by a hierarchical analysis method to obtain a first weight ranking of the service types; obtaining a rated load threshold of a data request of the distributed server, comparing a current load threshold with the rated load threshold, and initiating service degradation when the current load threshold is greater than the rated load threshold; and downgrading the server of the node corresponding to the service type according to the first weight ranking to reject the data request received within the current time period.

[0035] According to an embodiment of the present disclosure, a first weight ranking of service types of different nodes can be obtained by adopting a hierarchical analysis method, and the server of the node can be downgraded according to the first weight ranking, thereby ensuring that when the load pressure is high during the current time period, unimportant services are downgraded first to improve user experience.

[0036] Figure 1 The application scenario of the service degradation method of the distributed server according to the embodiment of the present disclosure is schematically shown. It should be noted that: Figure 1 What is shown are only examples of application scenarios to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios. It should be noted that the service degradation method, device, electronic device and computer-readable storage medium of the distributed server provided in the embodiments of the present disclosure can be used in the fields of Internet technology, big data technology and related aspects of the financial field, and can also be used in other fields outside the financial field. The service degradation method, device, electronic device and storage medium provided in the embodiments of the present disclosure do not limit the application field.

[0037] like Figure 1 As shown, the application scenario 100 according to the embodiment of the present disclosure may include terminal devices 101, 102, 103, a network 104 and a control center 105, and distributed servers 106, 107, 108. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the control center 105 or between the control center 105 and the distributed servers 106, 107, 108. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0038] Users can use terminal devices 101, 102, 103 to interact with the control center 105 through the network 104 to receive or send messages, etc. The control center 105 sends the messages or requests sent by the terminal devices 101, 102, 103 to the distributed servers 106, 107, 108 through the network 104 for processing, or receives instructions or messages returned from the distributed servers 106, 107, 108. Various client applications can be installed on the terminal devices 101, 102, 103, such as input method applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example), and data exchange, data call, data transmission, etc. can be realized between the terminal devices and the load balancing server and the cluster server through the network. The control center 105 is used to control the distributed servers 106, 107, 108 to downgrade, thereby providing users with a better experience.

[0039] The terminal devices 101, 102, and 103 may be various electronic devices that support information acquisition and information transmission, such as web browsing and voice broadcasting, which can be achieved by sending a request instruction to the control center 105, and the control center 105 dispatches the information to the distributed servers 106, 107, and 108 for information acquisition or call, and finally returns the information to the terminal device, and displays it through the information display device of the terminal device, such as displaying pictures or texts on a display screen, or displaying information through voice broadcasting, etc. Among them, electronic devices include but are not limited to smart speakers, smart phones, smart TVs, smart bracelets, tablet computers, laptop computers, desktop computers, etc.

[0040] The distributed servers 106, 107, and 108 may be servers that provide various services, such as background management servers (only as an example) that provide support for instructions sent by users using terminal devices 101, 102, and 103, or information retrieved or websites browsed, or web servers, FTP servers, enterprise core application servers, and other main task servers. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user voice instructions or user requests) to the terminal device. The distributed servers 106, 107, and 108 are used to collaborate with the control center 105 to complete work tasks.

[0041] It should be noted that the service degradation method provided in the embodiment of the present disclosure can generally be executed by the control center 105. Accordingly, the service degradation device provided in the embodiment of the present disclosure can generally be set in the server 105. In an optional embodiment, the service degradation method provided in the embodiment of the present disclosure can generally be executed by the distributed servers 106, 107, 108 and the control center 105 in collaboration. Accordingly, the service degradation device provided in the embodiment of the present disclosure can generally be set in the distributed servers 106, 107, 108 and the control center 105.

[0042] It should be understood that Figure 1 The number of terminal devices, networks, control centers, and distributed servers in the embodiment is only for illustration. Any number of terminal devices, networks, control centers, and distributed servers may be provided according to implementation requirements.

[0043] Figure 2 The flowchart of the service degradation method according to the embodiment of the present disclosure is schematically shown.

[0044] Combine the following Figure 2 The service degradation method of the embodiment of the present disclosure is described in detail.

[0045] like Figure 2 As shown, the service degradation method 200 of the distributed server according to the embodiment of the present disclosure includes operations S201 to S204.

[0046] In operation S201, service types of M nodes of a distributed server are obtained, where a service type has N service attributes, and the N service attributes of each service type have different weights, and M and N are positive integers greater than 1. For example, M is 2, 3, or 4, and N is 3, 4, or 5, and so on.

[0047] According to an embodiment of the present disclosure, a distributed server may be, for example, a server deployed at different locations, and different servers may be used to process different services. A server processing the same type of service may have one node or multiple nodes. Nodes processing the same type of service have a service type, i.e., the type of service corresponding to it. Each service type has multiple service attributes, for example, service attributes include two or more of the critical path degree level, the current number of users, the amount of data transmitted over the network, the configuration flow limiting level, the frequency of service use, and the service security level.

[0048] In an embodiment of the present disclosure, the N service attributes of each service type have different weights. For example, the service types include login service, user information query service, payment service, etc. For the login service, the service attributes included are the critical path degree level, the current number of users, the network transmission data volume, the configuration flow limit level, the service usage frequency, and the service security level. Moreover, each of the service attributes included has a different weight corresponding to the login service. For example, the critical path degree level, the current number of users, etc. in the login service and the user information query service have different weights.

[0049] In operation S202, the service types and service attributes are analyzed by a hierarchical analysis method to obtain a first weight ranking of the service types. Figure 3 Operation S202 is described in detail.

[0050] Figure 3 The flowchart of obtaining the first weight ranking of service types in the service degradation method according to an embodiment of the present disclosure is schematically shown.

[0051] like Figure 3 As shown, in the embodiment of the present disclosure, the process 300 of analyzing the service types and service attributes by the analytic hierarchy process (AHP) to obtain the first weight ranking of the service types includes operations S301 to S303.

[0052] In operation S301, a hierarchical analysis model is established, the hierarchical analysis model includes a highest layer, a middle layer and a lowest layer, the middle layer includes service attributes, and the lowest layer includes service types.

[0053] In the embodiments of the present disclosure, the highest level is the problem to be solved. In this embodiment, the highest level is the first weight ranking of the service type. The middle level includes service attributes, that is, the factors to be considered in obtaining the first weight ranking of the service type, and the analysis is performed according to the different service attributes of each service type. The lowest level includes service types, that is, the service types that need to be downgraded.

[0054] In operation S302, a comparison matrix and a hierarchical single ordering of the lowest layer and the middle layer are constructed, and a consistency check is performed on the comparison matrix.

[0055] In the embodiment of the present disclosure, the pairwise comparison matrix is ​​a comparison of the relative importance of all factors in the current layer to a factor in the previous layer. ij The comparison result of the ith factor relative to the jth factor is given using the 1-9 scaling method in Table 1. For example, all factors in this layer can be service types, and a factor in the upper layer can be a service attribute.

[0056] Table-1

[0057]

[0058]

[0059] Starting from the second level of the hierarchical analysis model, a pairwise comparison matrix is ​​constructed for multiple factors of the same level that are subordinate to each factor of the previous level, until the lowest level.

[0060] For example, a pairwise comparison matrix A is constructed based on multiple service attributes and the importance of the final selected service type. The service attributes include the critical path degree level (A1), the number of current users (A2), the amount of network transmission data (A3), the configuration flow limit level (A4), the service usage frequency (A5) and the service security level (A6). The constructed pairwise comparison matrix A is

[0061]

[0062] After constructing the pairwise comparison matrix A, the hierarchical single ranking (single-layer weight vector) is calculated and the comparison matrix A is checked for consistency to determine the permissible range of inconsistency of the comparison matrix A.

[0063] Specifically, the characteristic weight vector of the pairwise comparison matrix A is calculated. If the pairwise comparison matrix is ​​a consistent matrix, the normalized characteristic weight vector of the corresponding maximum characteristic root is taken. If the first pairwise comparison matrix is ​​not a consistent matrix, the normalized characteristic vector corresponding to the maximum characteristic root is used as the weight vector, that is, the characteristic root method is used to determine the weight vector.

[0064] For example, if the maximum eigenvalue of A is calculated to be λ=6.35, then the characteristic weight vector of the response is determined to be W (2) =(0.16, 0.19, 0.19, 0.05, 0.12, 0.30) T .

[0065] The steps for consistency check of comparison matrix A are:

[0066] First, construct the consistency index CI = (λ-n) / (n-1), where n represents the order of the comparison matrix, and λ represents the maximum characteristic root of the comparison matrix. When CI = 0, it means that the constructed pairwise comparison matrix comparison matrix A is consistent. When CI is close to 0, it means that the constructed pairwise comparison matrix has satisfactory consistency. The larger the CI, the more serious the inconsistency of the constructed pairwise comparison matrix. When judging the consistency of the comparison matrix, there can be differences, but they cannot be too large. That is, if the consistency index is within the set range, it means that the comparison matrix A passes the consistency test, otherwise it fails and the comparison matrix needs to be reconstructed.

[0067] For example, the consistency index CI of the comparison matrix A is calculated to be CI=(6.35-6) / (6-1)=0.07.

[0068] Next, obtain the random consistency index RI. The consistency test is calculated by calculating the consistency ratio CR, and the consistency ratio CR is calculated by the random consistency index RI. The random consistency index RI is a value obtained by statistics. For example, the random consistency index is obtained by looking up the table RI = 1.24.

[0069] Next, the consistency ratio CR is calculated based on the values ​​of RI and CI. Specifically, the consistency ratio CR = CI / RI. When the consistency ratio CR < x, it is considered that the inconsistency of the pairwise comparison matrix A is within the allowable range and has satisfactory consistency, that is, the pairwise comparison matrix A is considered to pass the consistency test. Where x is a set value, which can be adjusted according to different scenarios. If the consistency ratio CR ≥ x, it is considered that the comparison matrix A has not passed the consistency test, and the pairwise comparison matrix A must be reconstructed. For example, CR = 0.07 / 1.24 = 0.0565 < 0.1, which indicates that the pairwise comparison matrix A passes the consistency test.

[0070] In the embodiment of the present disclosure, as described above, the pairwise comparison matrix of the six service attributes for the login service, the payment service, and the user information query service is:

[0071]

[0072] The same method as above is used to compare the pairwise comparison matrix B n (n=1, 2, 3, 4, 5, 6) to perform consistency test and determine the pairwise comparison matrix B n All passed the consistency test.

[0073] According to the above pairwise comparison matrix, the maximum eigenvalue and the corresponding eigenweight vector are calculated as follows:

[0074] λ1=0.302, λ2=3.02, λ3=3.05, λ4=3.05, λ5=3.00, λ6=3.02.

[0075]

[0076] In operation S303, a total hierarchical ordering is constructed and a consistency check is performed to generate a first weighted ordering of the service types.

[0077] Calculate the weight vector of the relative importance of all factors in the lower layer to the highest layer. And use the consistency test described above to test. If it passes, the decision can be made according to the result represented by the total ranking weight vector. Otherwise, it is necessary to reconsider the model or rebuild the pairwise comparison matrix with a larger consistency ratio CR.

[0078] For example, the feature weight vector W = W (3) ×W (2） ,Right now

[0079]

[0080]

[0081] Therefore, the first weight ranking of the service types is determined as:

[0082] Login service > Payment service > User information query service

[0083] That is, in the first weight ranking of the service types, the weight of the login service is greater than the weight of the payment service, which is greater than the weight of the user information query service. The service can be downgraded according to the first weight ranking of each service type. For example, if the weight of the user information query service is the smallest, the user information query service can be downgraded first, that is, the user information query service can be shut down.

[0084] In operation S203, a rated load threshold of a data request of a distributed server is obtained, and the current load threshold is compared with the rated load threshold. When the current load threshold is greater than the rated load threshold, service degradation is initiated.

[0085] In the embodiments of the present disclosure, the data request of the distributed server is a data request from the user, and the entire distributed server system has a rated load threshold. In the actual operation process, due to activities such as promotions or flash sales, the data requests received by the system from users within a certain period of time or within a certain period of time in the future will increase sharply, resulting in exceeding the rated load threshold of the system. Therefore, when the current load threshold of the system is greater than the rated load threshold of the system, the server of the system needs to be downgraded to relieve the processing pressure of the server.

[0086] In operation S204, servers of nodes corresponding to the service type are downgraded according to the first weight ranking to reject data requests received in the current time period.

[0087] In an embodiment of the present disclosure, after receiving an instruction to downgrade the service, the control center needs to downgrade the server of the node corresponding to the service type according to the first weight sorting. For example, as described above, the order of service types obtained by the first weight sorting is login service>payment service>query user information service, that is, the first weight of the query user information service is the smallest. Therefore, the downgrade instruction can be set to prioritize the downgrade of the server of the node corresponding to the query user information service to reject the data requests received in the current time period. For example, the data request for the query user information service received in the current time period is rejected, while the login service data request and the payment service data request are not downgraded.

[0088] In an optional embodiment of the present disclosure, the service downgrade instruction may include instructions for downgrading multiple services, for example, instructions for downgrading the payment service and the user information query service generated according to the first weight sorting. In the process of service downgrading, the user information query service is preferentially downgraded, and when the current load threshold of the system is still greater than the rated load threshold, the payment service continues to be downgraded until the current load threshold is less than or equal to the rated load threshold.

[0089] In this embodiment, the service types include login service, payment service, and user information query service. In other optional embodiments, the service types may also be a larger number of services or other service types other than those in the examples. The present disclosure does not limit the types and quantities of service types.

[0090] According to the service downgrade method of the embodiment of the present invention, a first weight ranking of service types of different nodes can be obtained by adopting a hierarchical analysis method, and the server of the node can be downgraded according to the first weight ranking, thereby ensuring that when the load pressure is high during the current time period, unimportant services are downgraded first to improve user experience.

[0091] Figure 4 The flowchart of downgrading a node server according to the service degradation method of an embodiment of the present disclosure is schematically shown.

[0092] In an embodiment of the present disclosure, a process 400 of downgrading a server of a node corresponding to a service type according to a first weight ranking includes operations S401 to S404.

[0093] In operation S401 , a demotion instruction is generated according to a first weight sorting.

[0094] In an embodiment of the present disclosure, a downgrade instruction is generated according to a first weight sorting, and the downgrade instruction contains a downgrade request for at least one corresponding service type. The downgrade instruction contains a downgrade request queue, and the downgrade request queue in the downgrade instruction is generated according to the first weight sorting. For example, in the first weight sorting, a service type with a small weight can be set in the front row of the downgrade request queue and downgraded first, indicating that unimportant service types are downgraded first. A service type with a large weight can be set in the back row of the downgrade request queue. During the downgrade process, relatively important service types are downgraded last to ensure the user experience.

[0095] The downgrade request queue included in the downgrade instruction. When the control center sends the downgrade instruction to the server of the node, it can select one or more downgrade requests in the downgrade request queue, which is adjusted according to actual needs and the difference between the current load threshold and the rated load threshold of the system.

[0096] In operation S402, a downgrade instruction is received, and it is checked whether the downgrade status of the target server to be downgraded is turned on.

[0097] In an embodiment of the present disclosure, the downgrade request queue in the downgrade instruction includes one or more servers to be downgraded. After receiving the downgrade instruction, the control center sends the downgrade instruction to the target server to be downgraded, and checks the downgrade status of the target server, thereby deciding whether to execute the downgrade instruction based on the current status of the target server.

[0098] In operation S403, if the downgrade state of the target server is on, the downgrade instruction is rejected.

[0099] The downgrade status of the target server is turned on, indicating that the target server has been downgraded and no further downgrade is required. At this time, the downgrade instruction from the control center is rejected.

[0100] In operation S404, if the downgrade state of the target server is closed, a downgrade instruction is received and the target server is downgraded.

[0101] If the downgrade status of the target server is closed, it indicates that the target server can be downgraded, and then a downgrade instruction is received to downgrade the target server to alleviate the current load pressure of the system.

[0102] Figure 5 The flowchart of downgrading a target server according to the service degradation method of an embodiment of the present disclosure is schematically shown.

[0103] like Figure 5 As shown, after receiving the downgrade instruction, the process 500 of downgrading the target server includes operations S501 to S504.

[0104] In operation S501, a downgrade instruction is received, the target server executes the downgrade instruction, and statistics are kept on the time interval between the downgrade start time and the current time of the target server.

[0105] After receiving the downgrade instruction, the target server executes the downgrade instruction. After the target server starts to downgrade, the downgrade start time of the target server is recorded. At the same time, as the downgrade of the target server begins, the duration after the downgrade of the target server is calculated, that is, the time interval between the downgrade start time of the target server and the current time is calculated. In order to perform subsequent control on the target server according to the calculated time interval.

[0106] In operation S502, the time interval counted in operation S501 is compared with the size of the set interval. If the time interval is less than the set interval, operation S503 is performed, and if the time interval is not less than the set interval, operation S504 is performed. In the embodiments disclosed herein, the set interval is adjusted according to actual needs, for example, the set interval is 10s. In other optional embodiments, the set interval may also be other time lengths.

[0107] In the embodiment of the present disclosure, by setting a set interval for server downgrade, it is ensured that the server can achieve the reduction of the current load threshold of the server after downgrade. That is, it is necessary to ensure that the server is in a downgraded state for a certain period of time, rather than shutting down the downgraded state immediately after downgrade.

[0108] In operation S503, the data request from the user is rejected.

[0109] If the time interval is less than the set interval, it indicates that the server of the system has not been degraded to the predetermined load threshold. Therefore, in this case, when there is a data request from the user related to the server type, the data request from the user is directly rejected.

[0110] In operation S504, the time interval is sent to a control center.

[0111] If the time interval is not less than the set interval, it indicates that the system server may have been degraded to the predetermined load threshold, or it may not have been degraded to the predetermined load threshold. Therefore, the statistical time interval is sent to the control center, and further control is performed based on the statistical time interval.

[0112] Figure 6 The flowchart of the service degradation method according to the embodiment of the present disclosure is schematically shown after the time interval is sent to the control center.

[0113] like Figure 6 As shown, the process 600 after sending the time interval to the control center includes operations S601 to S605.

[0114] In operation S601, server attributes of servers of M nodes are obtained.

[0115] After sending the time interval to the control center, the server properties of the M node servers are obtained. The server properties include CPU usage, storage usage, memory usage, etc. For example, the storage usage can be the JVM usage. The server properties of the node server can reflect the operating status of the entire system. For example, when the CPU usage, storage usage, memory usage, etc. are all at a high value, it means that the server load pressure is large. If it is at a low value, it means that the server load pressure is small. Depending on the server load pressure, the server's degraded state can be turned on or off to adjust the server.

[0116] In operation S602, current load bearing values ​​of M nodes are calculated according to server attributes.

[0117] In the embodiment of the present disclosure, the server attributes of the server of each node are different. The server attributes of the server of each node are obtained and the server attributes of each node are counted, so as to calculate the current load bearing values ​​of the M nodes.

[0118] In operation S603, the current load bearing value is compared with a set threshold.

[0119] After the current load bearing values ​​of the M nodes are calculated in operation S602, they are compared with the set thresholds, and subsequent operations are performed according to the comparison results.

[0120] In operation S604, if the load bearing value is greater than the set threshold, the data request from the user is rejected.

[0121] If the calculated load bearing value is greater than the set threshold, it means that the degradation of the current service type has not yet reached a stable and operable state of the system, and it is necessary to continue to maintain the degraded state and reject data requests from users, that is, the degraded service type remains in a degraded state.

[0122] In an optional embodiment, there are still unexecuted queues in the demotion request queue of the demotion instruction. At this time, the demotion instructions in the unexecuted queue can continue to be executed to further reduce the load bearing value.

[0123] In operation S605, if the load bearing value is not greater than the set threshold, a data request from the user is received, and the degradation state of the target server is set to closed.

[0124] If the calculated load bearing value is not greater than the set threshold, it means that the degradation of the current service type has achieved a stable and operational system state, receiving data requests from users and processing data normally. In addition, the degradation state of the target server is set to closed.

[0125] In the embodiment of the present disclosure, after the load bearing value is greater than the set threshold and the data request from the user is rejected, the number of rejected data requests is also counted, and a priority downgrade strategy is generated according to the number of rejected data requests.

[0126] By counting the number of rejections of data requests from users, the unimportance of the data requests can be indicated based on the number of rejections. For example, the more rejections there are, the less important the service type is. When downgrading, a priority downgrade strategy can be generated based on the number of rejections to improve efficiency.

[0127] In an embodiment of the present disclosure, downgrading a service type includes rejecting some or all data requests from users, shutting down faulty services, delaying feedback or suspending use of data requests from users of unimportant service types, and the like.

[0128] Downgrading can be done in the following ways. For example, sacrificing some user experience. Specifically, the product page does not display the special service icon and promotion information; the settlement page does not display the self-collection / 311 / 411 appointment calendar; the order details page does not display the GIS order track or reminder, etc.; the evaluation list is prohibited from turning pages after 10 pages; real-time statistics and reports are disabled; the route or index field in the mandatory query condition is forced; the anti-brushing of bean beans is downgraded to puzzle verification; H5 becomes a PC page; general content is used instead of personalized recommendation content. Another example is to reduce the security level. Specifically, it can be submitting an order or posting a comment or logging in without calling the risk control interface; the front-end order of the settlement page does not enable the verification code; the centralized session is not available, and the cookie decryption is sufficient; the ip limit service, the registration and login times are not limited; the product modification content does not filter sensitive words. Another example is sacrificing some business logic. Specifically, it can be not verifying the number of Jingdou when bidding at an auction; posting a review, no longer verifying whether to return the goods, etc. Another example is to delay task processing, which can be WMS task processing engine, suspending tasks such as allocation and energy-saving subsidies; OFW giving priority to high-priority orders with simpler splitting logic, etc. Another example is to lose data persistence, which can be user address update, writing to redis, not writing back to the database; inventory pre-occupancy, writing to redis, asynchronously writing back to the database; user adding general tickets, writing to redis, not persistent; order secondary splitting task mechanism, from JMQ to redis queue, etc. Another example is to reduce accuracy / real-time performance, which can be real-time price expiration and not returning to the source; dynamic page becomes static bottom page; user nickname interface downgraded, showing user pin; inventory status interface downgraded, showing that there is stock; lottery abnormality, all users are shown as not winning. Another example is to reduce performance, which can be database instead of cache anti-duplication and query; database task queue polling instead of MQ; CDN downgraded to source station; local cache downgraded to RPC. Another example is to reduce disaster recovery capability, which can be automatic scheduling changed to manual scheduling; VIP downgraded to real IP, etc.

[0129] Figure 7 A block diagram of a service degradation device according to an embodiment of the present disclosure is schematically shown.

[0130] like Figure 7 As shown, the service degradation device 700 of this embodiment includes an acquisition module 710 , an analysis module 720 , a processing module 730 and a degradation module 740 .

[0131] The acquisition module 710 is configured to acquire the service types of M nodes of the distributed server, where the service type has N service attributes, and the N service attributes of each service type have different weights, and M and N are positive integers greater than 1. The acquisition module 710 can be used to perform the operation S201 described above, which will not be repeated here.

[0132] The analysis module 720 is configured to analyze the service type and the service attribute by using a hierarchical analysis method to obtain a first weight ranking of the service type. The analysis module 720 can be used to perform the operation S202 described above, which will not be described in detail here.

[0133] The processing module 730 is configured to obtain a rated load threshold of the data request of the distributed server, compare the current load threshold with the rated load threshold, and initiate service degradation when the current load threshold is greater than the rated load threshold. The processing module 730 can be used to perform the operation S203 described above, which will not be repeated here.

[0134] The downgrading module 740 is configured to downgrade the server of the node corresponding to the service type according to the first weight ranking to reject the data request received in the current time period. The downgrading module 740 can be used to perform the operation S204 described above, which will not be described in detail here.

[0135] In an embodiment of the present disclosure, the analysis module includes an analysis sub-module, which is configured to establish a hierarchical analysis model, the hierarchical analysis model includes a highest layer, a middle layer and a lowest layer, the middle layer includes service attributes, and the lowest layer includes service types; construct a comparison matrix and a hierarchical single sorting of the lowest layer and the middle layer, and perform a consistency check on the comparison matrix; construct a hierarchical total sorting, and perform a consistency check to generate a first weight sorting of the service type.

[0136] In an embodiment of the present disclosure, the downgrade module includes a downgrade sub-module, which is configured to generate a downgrade instruction according to a first weight sort; receive the downgrade instruction, check whether the downgrade status of the target server to be downgraded is turned on; if the downgrade status of the target server is turned on, reject the downgrade instruction; if the downgrade status of the target server is turned off, receive the downgrade instruction, and downgrade the target server.

[0137] In an embodiment of the present disclosure, the downgrade submodule also includes a statistical module, which is configured to receive a downgrade instruction, the target server executes the downgrade instruction, and counts the downgrade start time and the current time interval of the target server; if the time interval is less than the set interval, the data request from the user is rejected; if the time interval is not less than the set interval, the time interval is sent to the control center.

[0138] In an embodiment of the present disclosure, the service degradation device also includes a comparison module, which is configured to obtain server attributes of the servers of M nodes after sending the time interval to the control center; calculate the current load bearing value of the M nodes based on the server attributes; compare the current load bearing value with the set threshold, if the load bearing value is greater than the set threshold, reject the data request from the user; if the load bearing value is not greater than the set threshold, receive the data request from the user, and set the degradation status of the target server to closed.

[0139] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0140] For example, any multiple of the acquisition module 710, the analysis module 720, the processing module 730, the degradation module 740, the analysis submodule, the degradation submodule, the statistical module, and the comparison module can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the acquisition module 710, the analysis module 720, the processing module 730, the degradation module 740, the analysis submodule, the degradation submodule, the statistical module, and the comparison module can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware, and firmware or by a suitable combination of any of them. Alternatively, at least one of the acquisition module 710, analysis module 720, processing module 730, degradation module 740, analysis sub-module, degradation sub-module, statistics module and comparison module can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is executed.

[0141] Figure 8 A block diagram of an electronic device suitable for implementing the service degradation method described above according to an embodiment of the present disclosure is schematically shown. Figure 8 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0142] like Figure 8 As shown, the electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include an onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0143] In RAM 803, various programs and data required for the operation of electronic device 800 are stored. Processor 801, ROM 802 and RAM 803 are connected to each other via bus 804. Processor 801 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 802 and / or RAM 803. It should be noted that the program can also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0144] According to an embodiment of the present disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to the bus 804. The electronic device 800 may further include one or more of the following components connected to the I / O interface 805: an input portion 806 including a keyboard, a mouse, etc.; an output portion 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 808 including a hard disk, etc.; and a communication portion 809 including a network interface card such as a LAN card, a modem, etc. The communication portion 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage portion 808 as needed.

[0145] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0146] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.

[0147] An embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains a program code for executing the method provided by the embodiment of the present disclosure. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the service degradation method provided by the embodiment of the present disclosure.

[0148] When the computer program is executed by the processor 801, the above functions defined in the system / device of the embodiment of the present disclosure are executed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0149] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 809, and / or installed from a removable medium 811. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0150] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0151] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0152] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0153] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for downgrading a service of a distributed server, comprising: Obtaining the service types of M nodes of the distributed server, wherein the service type has N service attributes, and each of the N service attributes of the service type has different weights, wherein M and N are positive integers greater than 1, and the service attributes include: the current number of users, the amount of network transmission data, the configuration flow limiting level, the service usage frequency, the critical path degree level, and the service security level; Analyze the service type and the service attribute by using a hierarchical analysis method to obtain a first weight ranking of the service type; Obtaining a rated load threshold of a data request of the distributed server, comparing a current load threshold with the rated load threshold, and initiating service degradation when the current load threshold is greater than the rated load threshold; The server of the node corresponding to the service type is downgraded according to the first weight sorting to reject the data request received in the current time period.

2. The service degradation method according to claim 1, wherein: Analyzing the service type and the service attribute by using a hierarchical analysis method to obtain a first weight ranking of the service type includes: Establishing a hierarchical analysis model, the hierarchical analysis model includes a highest layer, a middle layer and a lowest layer, the middle layer includes the service attributes, and the lowest layer includes the service type; Constructing a comparison matrix and a hierarchical single sorting of the lowest layer and the middle layer, and performing a consistency check on the comparison matrix; A total hierarchical ordering is constructed and a consistency check is performed to generate a first weighted ordering of the service types.

3. The service degradation method according to claim 1, wherein: Degrading the server of the node corresponding to the service type according to the first weight sorting includes: Generating a downgrade instruction according to the first weight sorting; receiving the downgrade instruction, and checking whether the downgrade status of the target server to be downgraded is enabled; If the downgrade state of the target server is on, reject the downgrade instruction; If the downgrade state of the target server is closed, the downgrade instruction is received and the target server is downgraded.

4. The service degradation method according to claim 3, wherein: The receiving the downgrade instruction and downgrading the target server comprises: receiving the downgrade instruction, the target server executing the downgrade instruction, and counting the time interval between the downgrade start time and the current time of the target server; If the time interval is less than the set interval, rejecting the data request from the user; If the time interval is not less than the set interval, the time interval is sent to the control center.

5. The service degradation method according to claim 4, wherein: After sending the time interval to the control center, the service degradation method further includes: Obtain server attributes of the servers of the M nodes; Calculating current load bearing values ​​of the M nodes according to the server attributes; Compare the current load bearing value with the set threshold value, If the load bearing value is greater than the set threshold, rejecting the data request from the user; If the load bearing value is not greater than the set threshold, a data request from the user is received, and the degradation state of the target server is set to closed.

6. The service degradation method according to claim 5, wherein: After the load bearing value is greater than the set threshold and the data request from the user is rejected, the method further includes counting the number of rejections of the data request and generating a priority degradation strategy according to the number of rejections.

7. The service degradation method according to claim 5, wherein: The server attributes include CPU usage, storage usage, and memory usage.

8. A service degradation device for a distributed server, comprising: An acquisition module is configured to acquire service types of M nodes of a distributed server, wherein the service type has N service attributes, and the N service attributes of each service type have different weights, wherein M and N are positive integers greater than 1, and the service attributes include: the number of current users, the amount of network transmission data, the configuration flow limiting level, the service use frequency, the critical path degree level, and the service security level; An analysis module, configured to analyze the service type and the service attribute by using a hierarchical analysis method to obtain a first weight ranking of the service type; a processing module configured to obtain a rated load threshold of a data request of the distributed server, compare a current load threshold with the rated load threshold, and initiate service degradation when the current load threshold is greater than the rated load threshold; A downgrading module is configured to downgrade the server of the node corresponding to the service type according to the first weight ranking to reject the data request received in the current time period.

9. An electronic device, comprising: one or more processors; A storage device, used to store executable instructions, which, when executed by the processor, implement the service degradation method according to any one of claims 1 to 7.

10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, implements the service degradation method according to any one of claims 1 to 7.

Images