CN109739527B - Method, device, server and storage medium for client gray scale release - Google Patents
Method, device, server and storage medium for client gray scale release Download PDFInfo
- Publication number
- CN109739527B CN109739527B CN201811384519.9A CN201811384519A CN109739527B CN 109739527 B CN109739527 B CN 109739527B CN 201811384519 A CN201811384519 A CN 201811384519A CN 109739527 B CN109739527 B CN 109739527B
- Authority
- CN
- China
- Prior art keywords
- service
- node
- nodes
- gray
- release
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention provides a method, a device, a server and a storage medium for client gray scale release, wherein the method comprises the following steps: acquiring a service calling relation between service nodes; acquiring the flow of a service node through a client deployed in the service node; acquiring a service node meeting specified conditions according to the service calling relation and the flow of the service node to serve as a gray level release node; and deploying a new version of client on the gray release node. The invention considers the calling relation among the service nodes and the flow of the service nodes when determining the gray level publishing nodes, thereby reducing the influence of the gray level publishing of the client on the service.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method, a device, a server and a storage medium for client gray scale release.
Background
At present, when a client releases a new version, a node of a service deployment client cannot normally operate due to the defect of the new version, and certain influence is caused on the service. Therefore, the client needs to be grayed out.
At present, the most common gray scale publishing method is to randomly select the clients with the proportion to perform gray scale publishing according to the proportion of the deployed clients. However, by operating in proportion, there is a possibility that a new version of client is released to an important node of an important service, so that when there is a problem with the new version of client, traffic on the important node of the important service is lost.
Disclosure of Invention
In view of the above, embodiments of the present invention are proposed in order to provide a method, an apparatus, a server and a storage medium for client-side gray scale distribution that overcome or at least partially solve the above-mentioned problems.
According to a first aspect of the present invention, there is provided a method for client gray scale publishing, including:
acquiring a service calling relation between service nodes;
acquiring the flow of a service node through a client deployed in the service node;
acquiring a service node meeting specified conditions according to the service calling relation and the flow of the service node to serve as a gray level release node;
and deploying a new version of client on the gray release node.
Optionally, the obtaining of the service invocation relationship between the service nodes includes:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
Optionally, the obtaining the traffic of the service node through the client deployed in the service node includes:
monitoring the traffic of a service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
Optionally, the obtaining, according to the service invocation relationship and the traffic of the service node, the service node that meets the specified condition as a gray release node includes:
establishing a service topological graph among service nodes according to the service calling relation and the flow of the service nodes;
determining the service influence range of each service node according to the service topological graph;
acquiring service nodes meeting specified conditions according to the service influence range and the gray release number of each service node, and taking the service nodes as gray release nodes; or, according to the service influence range and the gray level publishing proportion of each service node, obtaining the service node meeting the specified conditions as the gray level publishing node.
Optionally, the service impact range includes an affected service node and traffic.
Optionally, the obtaining, according to the service influence range and the gray release number of each service node, a service node that meets a specified condition as a gray release node includes:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
Optionally, the obtaining, according to the service influence range and the gray scale publishing proportion of each service node, the service node that meets the specified condition as the gray scale publishing node includes:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the top and meet the gray scale release proportion as gray scale release nodes.
Optionally, after the new version of the client is deployed on the gray release node, the method further includes:
monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node;
monitoring the error log information of the new version of client to obtain error reporting information of the gray level publishing node;
and when the flow and the error report information of the gray release node meet the release conditions, the operations of determining the gray release node and deploying the client of the new version are executed again until the clients in all the service nodes are upgraded.
Optionally, the method further includes:
and when the flow and the error report information of the gray level release node do not meet the release conditions, carrying out version backtracking on the client on the gray level release node.
According to a second aspect of the present invention, there is provided an apparatus for client gray scale publishing, including:
the calling relation acquisition module is used for acquiring service calling relations among the service nodes;
the traffic acquisition module is used for acquiring traffic of the service node through a client deployed in the service node;
the gray level release node determining module is used for acquiring the service nodes meeting the specified conditions according to the service calling relation and the flow of the service nodes to serve as the gray level release nodes;
and the client deployment module is used for deploying a new version of client on the gray release node.
Optionally, the calling relationship obtaining module is specifically configured to:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
Optionally, the traffic acquiring module is specifically configured to:
monitoring the traffic of a service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
Optionally, the gray scale publishing node determining module includes:
a service topological graph establishing unit, configured to establish a service topological graph among service nodes according to the service invocation relationship and the traffic of the service nodes;
a service influence determining unit, configured to determine a service influence range of each service node according to the service topology map;
the gray level publishing node determining unit is used for acquiring the service nodes meeting the specified conditions as gray level publishing nodes according to the service influence range and the gray level publishing number of each service node; or, according to the service influence range and the gray level publishing proportion of each service node, obtaining the service node meeting the specified conditions as the gray level publishing node.
Optionally, the service impact range includes an affected service node and traffic.
Optionally, the gray scale publishing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
Optionally, the gray scale publishing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and obtaining the service nodes which are ranked at the front and meet the gray scale publishing proportion as gray scale publishing nodes.
Optionally, the method further includes:
the flow monitoring module is used for monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node;
the error reporting information monitoring module is used for monitoring the error log information of the new version of client to obtain the error reporting information of the gray level release node;
and the gray release module is used for executing the operations of determining the gray release nodes and deploying the client of the new version again when the flow and the error report information of the gray release nodes meet the release conditions until the clients in all the service nodes are upgraded.
Optionally, the method further includes:
and the degradation module is used for backtracking the versions of the clients on the gray-scale release nodes when the flow and the error report information of the gray-scale release nodes do not meet the release conditions.
According to a third aspect of the present invention, there is provided a server comprising: a processor, a memory and a computer program stored on and executable on the memory, which computer program, when executed by the processor, implements the method of client greyscale publishing as described in the first aspect.
According to a fourth aspect of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of client side greyscale distribution as described in the first aspect.
Aiming at the prior art, the invention has the following advantages:
according to the method, the device, the server and the storage medium for client gray scale release provided by the embodiment, the service call relation among the service nodes is obtained, the flow of the service nodes is obtained through the client deployed in the service nodes, the service nodes meeting the specified conditions are obtained according to the service call relation and the flow of the service nodes to serve as gray scale release nodes, and the new version of the client is deployed on the gray scale release nodes.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention.
Fig. 1 is a flowchart illustrating steps of a method for gray scale publishing at a client according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating steps of a method for client gray release according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating steps of a method for gray scale publishing at a client according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating steps of a method for client gray release according to an embodiment of the present invention;
fig. 5 is an exemplary diagram of a service topology diagram in a method for client gray scale publishing according to an embodiment of the present invention;
fig. 6 is a block diagram of a device for client gray release according to an embodiment of the present invention;
fig. 7 is a block diagram of a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
Fig. 1 is a flowchart of steps of a method for gray-scale publishing by a client according to an embodiment of the present invention, and is applied to a server corresponding to the client, as shown in fig. 1, the method may include:
The service calling relation refers to other service nodes called by one service node. The business nodes may be servers or clusters of servers deployed in various departments in a company to provide services of the department.
Optionally, the obtaining of the service invocation relationship between the service nodes includes:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
The client may be a client used for service in a company, such as a log collection client, and the like, and may also be another client, which is not limited herein. The client may be installed in the service node, and configured to monitor traffic of the service node and a service invocation relationship of the service node.
A link analysis module may be arranged in the client, where the link analysis module is configured to record other service nodes called by the service node where the client is located, send the recorded service calling relationship to a server corresponding to the client (i.e., a server providing service for the client), and send the respective service calling relationship to the server corresponding to the client by the client deployed in each service node.
Before this step, it may also optionally include: and verifying the correctness of the new version of the client by using the test environment.
After the development of the new-version client is completed, the test server with the same configuration as the production environment performs function test and performance test on the new-version client, monitors the flow of the client and reports error information, and enters a gray-scale release process when release conditions are met, that is, steps 101 to 104 in this embodiment.
The traffic of the service node refers to network traffic of a host of the service node.
Optionally, the obtaining the traffic of the service node through the client deployed in the service node includes:
monitoring the traffic of the service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
The client deployed in the service node also needs to monitor network traffic of all hosts corresponding to the service node and send the network traffic to the server corresponding to the client. It should be noted that, when a service node is a server, the traffic of the server is the traffic of the service node, and when the service node is a server cluster, the sum of the traffic of the servers in the server cluster is the traffic of the service node.
And 103, acquiring the service nodes meeting the specified conditions according to the service calling relation and the flow of the service nodes to serve as gray release nodes.
The gray scale publishing refers to a publishing mode capable of smoothly transiting between black and white, and A/B (analog/digital) publishing can be performed on the publishing mode, namely, a part of users continue to use the product characteristics A, a part of users start to use the product characteristics B, and if the users do not have any objection to the product characteristics B, the range is gradually expanded, and all the users are migrated to the product characteristics B. The gray level issuing can ensure the stability of the whole system, and the problems can be found and adjusted when the initial gray level is issued so as to ensure the smaller influence degree. The gray level publishing node is a service node for performing gray level publishing.
The specified conditions need to include both of the following conditions:
firstly, an upstream node of a service node does not contain a user node, and a downstream node of the service node does not contain the user node;
second, the number of affected service nodes is minimal.
The method for obtaining the service node meeting the specified conditions comprises the following steps: and sequencing all the service nodes according to the sequence of the number of the service nodes influenced by the service nodes from small to large, sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow, and selecting the service nodes which are ranked at the front and meet the gray level release number, or selecting the service nodes which are ranked at the front and meet the gray level release proportion.
The gray level publishing number is the number of preset gray level publishing nodes, and the gray level publishing proportion is the proportion of the preset gray level publishing nodes in all the service nodes.
The user is a user outside each department in a company, and may be a consumer, for example. The upstream node of a service node is the other service node calling the service node, and the downstream node of a service node is the other service node called by the service node. The service nodes affected by a service node include upstream and downstream nodes of the service node.
Determining whether an upstream node or a downstream node of each service node contains a user node or not according to the service calling relation and the flow of the service node, when the upstream node and the downstream node do not contain the user node, determining the total flow of the service node influenced by each service node, selecting the service node with the lowest total flow of the influenced service nodes, wherein the number of the selected service nodes is the gray level issuing number or the number of the selected service nodes is determined by the gray level issuing proportion and the total number of the service nodes. If an upstream node or a downstream node of a service node includes a user node, the service node cannot be used as a gray scale publishing node in order not to affect the normal use of the user during gray scale publishing, and therefore the service node is excluded first.
And 104, deploying a new version of client on the gray release node.
After the gray release node is determined, a new version of the client is deployed on the gray release node, namely the client on the gray release node is upgraded. Specifically, the purpose of deploying a new version of the client on the gray level publishing node can be achieved by sending an upgrade instruction to the client on the gray level publishing node to instruct the client to upgrade.
In the method for releasing the gray level of the client, the service call relationship between the service nodes is obtained, the traffic of the service nodes is obtained through the client deployed in the service nodes, the service nodes meeting the specified conditions are obtained as the gray level release nodes according to the service call relationship and the traffic of the service nodes, and the new version of the client is deployed on the gray level release nodes.
Fig. 2 is a flowchart of steps of a method for client gray scale publishing according to an embodiment of the present invention, where on the basis of the foregoing embodiment, when a gray scale publishing node is determined, a service topology graph between service nodes is established according to a service invocation relationship and traffic of the service nodes, and a service node meeting a specified condition is determined and obtained according to the service topology graph to serve as a gray scale publishing node, as shown in fig. 2, the method may include:
The specific content of this step is the same as that of step 101 in the above embodiment, and is not described here again.
The specific content of this step is the same as that of step 102 in the above embodiment, and is not described here again.
Step 203, establishing a service topological graph between service nodes according to the service calling relation and the traffic of the service nodes.
According to the service call relation of each service node, the downstream node of each service node can be determined, and meanwhile, one service node can also be the upstream node of other service nodes, so that starting from one service node, all the upstream nodes and/or the downstream nodes of the service node can be determined, the identifications of the two service nodes of the service call relation can be connected, the service call relations of all the nodes are drawn on a graph, the flow of each service node is marked on the graph, and the service topological graph among the service nodes is formed. In the service topological graph, all service nodes on one link form a calling link.
And 204, determining the service influence range of each service node according to the service topological graph.
The service influence range can optionally comprise influenced service nodes and flow.
According to the service topological graph, all upstream nodes and/or downstream nodes of a service node can be determined, the upstream nodes and/or the downstream nodes are the service nodes influenced by the service node, the sum of the flow of the upstream nodes and/or the downstream nodes is counted and used as the flow influenced by the service node, and therefore the service node influenced by the service node and the flow are the service influence range of the service node. Wherein all upstream nodes of a service node include an immediate upstream node of the service node and an upstream node of the immediate upstream node, and all downstream nodes of a service node include an immediate downstream node of the service node and a downstream node of the immediate downstream node.
According to the service influence range of each service node, whether a service node influenced by one service node comprises a user node or not can be determined, the service node comprising the user node in the influenced service node can be firstly eliminated, the number of other service nodes influenced by each service node is calculated in the rest service nodes, and the service node which has the smallest number of the other influenced service nodes and meets the gray level publishing number is selected, or the service node which has the smallest number of the other influenced service nodes and meets the gray level publishing proportion is selected to be used as the gray level publishing node. If the number of other service nodes influenced by the plurality of service nodes is the same and a part of the service nodes are required to be selected as the gray level publishing node, the service node with the lowest influenced flow can be selected from the plurality of service nodes to be used as the gray level publishing node. For example, when the number of other service nodes affected by the service node 1 is 2, the affected traffic is 1000QPS, the number of other service nodes affected by the service node 2 is 3, the affected traffic is 2000QPS, the number of other service nodes affected by the service node 3 is 3, the affected traffic is 3000QPS, the number of other service nodes affected by the service node 4 is 3, the affected traffic is 4000QPS, the number of other service nodes affected by the service node 5 is 4, and the affected traffic is 5000QPS, and 3 service nodes need to be selected as gray-scale distribution nodes, first, the service node with the smallest affected service node number, i.e., the service node 1, is selected, and the number of other service nodes affected by the service node 2, the service node 3, and the service node 4 is 3, at this time, 2 service nodes need to be selected from the 3 service nodes as gray-scale distribution nodes, then, the service node with the least influence on the flow is selected from the 3 service nodes, so that the service node 2 and the service node 3 are selected, and finally, the service node 1, the service node 2 and the service node 3 are used as gray level publishing nodes.
Optionally, the obtaining, according to the service influence range and the gray release number of each service node, a service node that meets a specified condition as a gray release node includes:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
The business nodes which are ranked in the front and meet the gray level release number are obtained to serve as the gray level release nodes. By sequencing the service nodes from small to large according to the number of the influenced service nodes and the influenced flow, the service node with smaller service influence range can be quickly and accurately determined to be used as the gray release node.
Optionally, the obtaining, according to the service influence range and the gray scale publishing ratio of each service node, a service node that meets a specified condition as a gray scale publishing node includes:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and obtaining the service nodes which are ranked at the front and meet the gray scale publishing proportion as gray scale publishing nodes.
The business nodes which are ranked in the front and meet the gray level distribution proportion are obtained to serve as gray level distribution nodes. By sequencing the service nodes from small to large according to the number of the influenced service nodes and the influenced flow, the service node with smaller service influence range can be quickly and accurately determined to be used as the gray release node.
And step 206, deploying a new version of client on the gray release node.
The specific content of this step is the same as that of step 104 in the above embodiment, and is not described here again.
The method for releasing the gray level of the client according to this embodiment includes obtaining a service call relationship between service nodes, obtaining traffic of the service nodes through the client disposed in the service nodes, establishing a service topology map between the service nodes according to the service call relationship and the traffic of the service nodes, determining a service influence range of each service node according to the service topology map, obtaining the service nodes meeting specified conditions as gray level releasing nodes according to the service influence range and a gray level releasing number or a gray level releasing proportion, deploying a new version of client on the gray level releasing nodes, selecting the service nodes with a small service shadow range as the gray level releasing nodes due to consideration of the service influence range between the service nodes when determining the gray level releasing nodes, thereby reducing the influence of the gray level releasing of the client on the service, and rapidly determining the service influence range of each service node by establishing the service topology map, thereby improving the processing speed of determining the gray scale publishing node.
Fig. 3 is a flowchart of steps of a method for client gray scale publishing according to an embodiment of the present invention, where on the basis of the foregoing embodiment, after a new version of a client is deployed on a gray scale publishing node, the present embodiment may further include: monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node; and when the flow and the error reporting information of the gray level publishing node meet the publishing conditions, the operations of determining the gray level publishing node and deploying the new client are executed again until the clients in all the service nodes are upgraded. As shown in fig. 3, the method may include:
The specific content of this step is the same as that of step 101 in the above embodiment, and is not described again here.
The specific content of this step is the same as that of step 102 in the above embodiment, and is not described here again.
And 303, acquiring the service node meeting the specified conditions according to the service calling relation and the flow of the service node to serve as a gray release node.
The specific content of this step is the same as that of step 103 in the above embodiment, and is not described here again.
And step 304, deploying a new version of client on the gray release node.
The specific content of this step is the same as that of step 104 in the above embodiment, and is not described here again.
And 305, judging whether to upgrade the clients in all the service nodes, if not, executing step 306, and if so, ending.
If the clients in all the service nodes are upgraded, the gray scale release of the clients is completed, and the process is ended, and if the clients in the service nodes are not upgraded, the step 305 is executed to perform the next round of gray scale release process.
And step 306, monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node.
The method comprises the steps of obtaining the flow of the corresponding gray level publishing node through a monitoring module in a new version of client deployed on the gray level publishing node, and sending the flow of the gray level publishing node to a server through communication between the client and the server.
The method comprises the steps that error log information of a new client is monitored through a monitoring module in the new client, the error log information is generated before the new client encounters failure downtime, the monitoring module obtains the error log information and serves as error reporting information of a gray-scale release node, and the error reporting information is sent to a server through communication between the client and the server by the new client.
And 308, judging whether the issuing condition is met or not according to the flow and the error information of the gray level issuing node, if so, executing the step 302, and otherwise, executing the step 309.
The issuing condition may be that no error information exists, and an absolute value of a difference between the flow of the grayscale issuing node and the flow of the client before the upgrade is less than or equal to a preset threshold.
And determining whether a fault exists in the new version of client according to the error reporting information, if so, determining whether the fault exists, if not, comparing whether the absolute value of the difference between the flow of the gray level publishing node and the flow of the client before the node is upgraded is greater than a preset threshold, if not, determining that the publishing condition is met, executing the steps 302 to 307 again, performing the next gray level publishing process, selecting the service nodes meeting the specified conditions from the rest service nodes according to the rules again to serve as the gray level publishing nodes, and upgrading the clients in all the service nodes.
And 309, backtracking the version of the client on the gray release node.
If the flow and the error report information of the gray level release node do not meet the gray level release conditions, determining that the new version of the client has a fault and cannot normally operate, and affecting the service of the service node, notifying a worker to process the fault of the new version of the client, and simultaneously backtracking the version of the client on the gray level release node to restore to the version before upgrading, thereby ensuring the normal operation of the service node.
In the method for releasing the gray scale of the client, after the new version of the client is deployed on the gray scale releasing node, the flow and the error reporting information of the gray scale releasing node are obtained, so that the problem existing in the new version of the client can be found in time, and therefore measures are taken to process the problem, or when the problem does not exist in the new version of the client, if the releasing condition is met, the gray scale releasing operation is continuously executed, namely the gray scale releasing node is determined and the new version of the client is deployed until the clients in all service nodes are upgraded to complete the gray scale releasing.
Fig. 4 is a flowchart of steps of a method for gray-scale publishing by a client according to an embodiment of the present invention, where this embodiment is an optional example based on the foregoing embodiment, and this embodiment takes 9 service nodes as an example for illustration. The 9 service nodes include a service node 1, a service node 2, a service node 3, a service node 4, a service node 5, a service node 6, a service node 7, a service node 8, and a service node 9. As shown in fig. 4, the method may include:
And recording other service nodes called by the service node where the client is located through a link analysis module arranged in the client on the service node as a service calling relation, and sending the service calling relation to the server. After receiving the service calling relationship sent by each service node, the server determines that the service node 1 is a called node of all the service nodes, and the specific service calling relationship is as follows: the service node 2 calls the service node 1, the service node 3 calls the service node 1, the user node calls the service node 3, the service node 4 calls the service node 1, the service node 5 calls the service node 1, the service node 6 calls the service node 1 and the service node 8, the service node 7 calls the service node 2, the service node 8 calls the service node 2 and the service node 5, and the service node 9 calls the service node 3.
The obtained flow of each service node is as follows: the traffic of the service node 1 is 5000QPS, the traffic of the service node 2 is 8000QPS, the traffic of the service node 4 is 8000QPS, the traffic of the service node 5 is 1500QPS, the traffic of the service node 6 is 4500QPS, the traffic of the service node 7 is 10000QPS, the traffic of the service node 8 is 7000QPS, and the traffic of the service node 9 is 10000 QPS.
According to the service call relation of each service node, the downstream node of each service node can be determined, and meanwhile, one service node can also be the upstream node of other service nodes, so that starting from one service node, all the upstream nodes and/or the downstream nodes of the service node can be determined, the identifications of the two service nodes of the service call relation can be connected, the service call relations of all the nodes are drawn on a graph, the flow of each service node is marked on the graph, and the service topological graph among the service nodes is formed. The established service topological graph is shown in fig. 5, in the service topological graph, all service nodes on one link form a call link, for example, a call link is formed by the service node 1, the service node 2 and the service node 7, a call link is formed by the service node 1, the service node 2, the service node 8 and the service node 6, a call link is formed by the service node 1, the service node 3 and the user node, a call link is formed by the service node 1, the service node 3 and the service node 9, a call link is formed by the service node 1 and the service node 4, a call link is formed by the service node 1, the service node 5, the service node 8 and the service node 6, and a call link is formed by the service node 1 and the service node.
And step 404, determining the service influence range of each service node according to the service topological graph.
As shown in fig. 5, in the call link of 'service node 1, service node 3 and user node', the service nodes influenced by the service node 3 are determined to include the service node 1 and the user node; in a call link of 'service node 1, service node 2 and service node 7', determining that the service nodes influenced by the service node 2 include the service node 7 and the service node 1, wherein the total flow of the call link is 18000 QPS; in the call link of the service node 1 and the service node 4', determining that the service node influenced by the service node 4 is the service node 1, and the total flow is 8000 QPS; similarly, the service impact ranges of the service nodes in other invocation links are determined. And counting the quantity and the flow of all service nodes influenced by the same service node in each calling link comprising the service node, and taking the quantity and the flow as the service influence range of the service node.
And 405, sequencing the number of the service nodes influenced by each service node from small to large, sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow, and acquiring the service nodes which are ranked at the front and meet the gray level release number as gray level release nodes, or acquiring the service nodes which are ranked at the front and meet the gray level release proportion as the gray level release nodes.
As shown by the thicker black line in fig. 5, because a user node is involved, none of the service nodes on the calling link can be the first choice of the gray-scale publishing node; the service node 4 may be selected from the original gray-scale distribution node because the service node only affects the service node 1, that is, the number of affected service nodes is 1, while the number of affected service nodes of other service nodes is greater than 1, and the traffic affected by the service node 4 is 13000QPS, which is also relatively low.
And 406, deploying a new version of the client on the gray release node.
And deploying the client of the new version on the determined gray release node, namely the service node 4.
And step 410, backtracking the versions of the clients on the gray release nodes.
In the method for client gray scale publishing provided by this embodiment, 9 service nodes are taken as an example to introduce a gray scale publishing process, and since the calling relationship between the service nodes and the traffic of the service nodes are considered when determining the gray scale publishing node, the influence of the client gray scale publishing on the service can be reduced.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Fig. 6 is a block diagram of a client gray scale distribution apparatus according to an embodiment of the present invention, where the client gray scale distribution apparatus may be applied in a server, and as shown in fig. 6, the client gray scale distribution apparatus 600 may include:
a calling relationship obtaining module 601, configured to obtain a service calling relationship between service nodes;
a traffic obtaining module 602, configured to obtain traffic of a service node through a client deployed in the service node;
a gray release node determining module 603, configured to obtain, according to the service invocation relationship and the traffic of the service node, a service node that meets a specified condition, and use the service node as a gray release node;
and the client deployment module 604 is used for deploying a new version of the client on the gray release node.
Optionally, the calling relationship obtaining module is specifically configured to:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
Optionally, the traffic acquiring module is specifically configured to:
monitoring the traffic of a service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
Optionally, the gray scale publishing node determining module includes:
a service topological graph establishing unit, configured to establish a service topological graph among service nodes according to the service invocation relationship and the traffic of the service nodes;
a service influence determining unit, configured to determine a service influence range of each service node according to the service topology map;
the gray level publishing node determining unit is used for acquiring the service nodes meeting the specified conditions according to the service influence range and the gray level publishing number of each service node to serve as the gray level publishing nodes; or, according to the service influence range and the gray level publishing proportion of each service node, obtaining the service node meeting the specified conditions as the gray level publishing node.
Optionally, the service impact range includes an affected service node and traffic.
Optionally, the gray scale publishing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
Optionally, the gray scale publishing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and obtaining the service nodes which are ranked at the front and meet the gray scale publishing proportion as gray scale publishing nodes.
Optionally, the method further includes:
the flow monitoring module is used for monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node;
the error reporting information monitoring module is used for monitoring the error log information of the new version of client to obtain the error reporting information of the gray level release node;
and the gray release module is used for executing the operations of determining the gray release nodes and deploying the client of the new version again when the flow and the error report information of the gray release nodes meet the release conditions until the clients in all the service nodes are upgraded.
Optionally, the method further includes:
and the degradation module is used for backtracking the versions of the clients on the gray-scale release nodes when the flow and the error report information of the gray-scale release nodes do not meet the release conditions.
The device for releasing the gray scale of the client according to this embodiment acquires a service call relationship between service nodes through a call relationship acquisition module, acquires traffic of the service nodes through the client deployed in the service nodes through a traffic acquisition module, and acquires the service nodes meeting specified conditions as gray scale release nodes according to the service call relationship and the traffic of the service nodes.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
Fig. 7 is a block diagram of a server according to an embodiment of the present invention. As shown in fig. 7, the server 700 may include a processor 701 coupled to one or more data storage facilities, which may include a memory unit 702 and a storage medium 703. The server 700 may also include an input interface 704 and an output interface 705 for communicating with another device or system. Program codes executed by the CPU of the processor 701 may be stored in the memory unit 702 or the storage medium 704.
The processor 701 in the server 700 calls the program code stored in the memory unit 702 or the storage medium 703 to execute the method of the client-side grayscale release in the above embodiment.
The storage medium may be a Read-Only Memory (ROM), or may be a Read-write medium, such as a hard disk or a flash Memory. The Memory unit may be a Random Access Memory (RAM). The memory unit may be physically integrated with the processor or integrated in the memory or implemented as a separate unit.
The processor is the control center of the server and provides a processing device for executing instructions, performing interrupt operations, providing timing functions and various other functions. Optionally, the processor includes one or more Central Processing Units (CPUs), such as CPU 0 and CPU 1 shown in fig. 7. The server includes one or more processors. The processor may be a single core (single CPU) processor or a multi-core (multi-CPU) processor. Unless otherwise stated, a component such as a processor or a memory described as performing a task may be implemented as a general component, which is temporarily used to perform the task at a given time, or as a specific component specially manufactured to perform the task. The term "processor" as used herein refers to one or more devices, circuits and/or processing cores that process data, such as computer program instructions.
The program code executed by the CPU of the processor may be stored in a memory unit or a storage medium. Alternatively, the program code stored in the storage medium may be copied into the memory unitFor execution by the CPU of the processor. The processor may execute at least one kernel (e.g., LINUX)TM、UNIXTM、WINDOWSTM、ANDROIDTM、IOSTM) It is well known for the kernel to control the operation of the servers described above by controlling the execution of other programs or processes, controlling communication with peripheral devices, and controlling the use of computer device resources.
The above elements in the above server may be connected to each other by a bus, such as one of a data bus, an address bus, a control bus, an expansion bus, and a local bus, or any combination thereof.
There is also provided, in accordance with an embodiment of the present invention, a computer-readable storage medium having a computer program stored thereon, where the storage medium may be a Read-Only Memory (ROM) or a Read-write medium, such as a hard disk or a flash Memory. The computer program, when executed by a processor, implements the method of client-side grayscale publication of the foregoing embodiments.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The method, the device, the server and the storage medium for client gray scale publishing provided by the invention are introduced in detail, a specific example is applied in the text to explain the principle and the implementation of the invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (18)
1. A method for client gray scale release is characterized by comprising the following steps:
acquiring a service calling relation between service nodes;
acquiring the flow of a service node through a client deployed in the service node;
acquiring a service node meeting specified conditions according to the service calling relation and the flow of the service node to serve as a gray level release node, wherein the method comprises the following steps: establishing a service topological graph among service nodes according to the service calling relation and the flow of the service nodes; determining an upstream node and/or a downstream node corresponding to each service node according to the service topological graph; determining the flow influenced by each service node according to the sum of the flows of the upstream node and/or the downstream node; determining the service influence range of each service node according to the upstream node and/or the downstream node corresponding to each service node and the flow influenced by each service node; acquiring service nodes meeting specified conditions according to the service influence range and the gray release number of each service node, and taking the service nodes as gray release nodes; or acquiring the service nodes meeting the specified conditions according to the service influence range and the gray level release proportion of each service node to serve as gray level release nodes; wherein the specified conditions include: the upstream node of the service node does not contain a user node, and the downstream node of the service node does not contain the user node, and the number of the affected service nodes is minimum;
and deploying a new version of client on the gray release node.
2. The method of claim 1, wherein obtaining the service invocation relationship between the service nodes comprises:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
3. The method of claim 1, wherein obtaining traffic of the service node through a client deployed in the service node comprises:
monitoring the traffic of a service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
4. The method of claim 1, wherein the service impact area comprises affected service nodes and traffic.
5. The method according to claim 4, wherein the obtaining, as the gray-scale distribution node, the service node satisfying the specified condition according to the service influence range and the gray-scale distribution number of each service node comprises:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
6. The method according to claim 4, wherein the obtaining, as the gray-scale distribution node, the service node satisfying the specified condition according to the service influence range and the gray-scale distribution ratio of each service node comprises:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and obtaining the service nodes which are ranked at the front and meet the gray scale publishing proportion as gray scale publishing nodes.
7. The method of claim 1, wherein after deploying the new version of the client on the gray release node, further comprising:
monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node;
monitoring the error log information of the new version of client to obtain error reporting information of the gray level publishing node;
and when the flow and the error report information of the gray release node meet the release conditions, the operations of determining the gray release node and deploying the client of the new version are executed again until the clients in all the service nodes are upgraded.
8. The method of claim 7, further comprising:
and when the flow and the error report information of the gray level release node do not meet the release conditions, carrying out version backtracking on the client on the gray level release node.
9. An apparatus for client-side grayscale publishing, comprising:
the calling relation acquisition module is used for acquiring service calling relations among the service nodes;
the traffic acquisition module is used for acquiring traffic of the service node through a client deployed in the service node;
the gray release node determining module is used for acquiring the service node meeting the specified conditions according to the service calling relation and the flow of the service node, and the gray release node determining module is used as a gray release node and comprises the following steps: a service topological graph establishing unit, configured to establish a service topological graph among service nodes according to the service invocation relationship and the traffic of the service nodes; a service influence determining unit, configured to determine, according to the service topology map, an upstream node and/or a downstream node corresponding to each service node; determining the flow influenced by each service node according to the sum of the flows of the upstream node and/or the downstream node; determining the service influence range of each service node according to the upstream node and/or the downstream node corresponding to each service node and the flow influenced by each service node; the gray level publishing node determining unit is used for acquiring the service nodes meeting the specified conditions according to the service influence range and the gray level publishing number of each service node to serve as the gray level publishing nodes; or acquiring the service nodes meeting the specified conditions according to the service influence range and the gray level release proportion of each service node to serve as gray level release nodes; wherein the specified conditions include: the upstream node of the service node does not contain a user node, and the downstream node of the service node does not contain the user node, and the number of the affected service nodes is minimum;
and the client deployment module is used for deploying a new version of client on the gray release node.
10. The apparatus of claim 9, wherein the call relation obtaining module is specifically configured to:
and monitoring other service nodes called by the service node through a client deployed in the service node to obtain the service calling relation.
11. The apparatus according to claim 9, wherein the traffic acquisition module is specifically configured to:
monitoring the traffic of a service node by a client deployed in the service node to obtain the traffic of the service node, wherein the traffic of the service node is the sum of network traffic of all hosts corresponding to the service node.
12. The apparatus of claim 9, wherein the service impact area comprises affected service nodes and traffic.
13. The apparatus according to claim 12, wherein the grayscale issuing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and acquiring the service nodes which are ranked at the front and meet the gray release quantity as gray release nodes.
14. The apparatus according to claim 12, wherein the grayscale issuing node determining unit is specifically configured to:
sequencing the number of the service nodes influenced by each service node from small to large, and sequencing the service nodes with the same number of the influenced service nodes from small to large according to the influenced flow;
and obtaining the service nodes which are ranked at the front and meet the gray scale publishing proportion as gray scale publishing nodes.
15. The apparatus of claim 9, further comprising:
the flow monitoring module is used for monitoring the flow of the gray level publishing node to obtain the flow of the gray level publishing node;
the error reporting information monitoring module is used for monitoring the error log information of the new version of client to obtain the error reporting information of the gray level release node;
and the gray release module is used for executing the operations of determining the gray release nodes and deploying the client of the new version again when the flow and the error report information of the gray release nodes meet the release conditions until the clients in all the service nodes are upgraded.
16. The apparatus of claim 15, further comprising:
and the degradation module is used for backtracking the versions of the clients on the gray-scale release nodes when the flow and the error report information of the gray-scale release nodes do not meet the release conditions.
17. A server, comprising: a processor, a memory and a computer program stored on and executable on the memory, the computer program, when executed by the processor, implementing the method of client greyscale publishing as claimed in any of claims 1-8.
18. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, implements the method of client gray scale publishing according to any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811384519.9A CN109739527B (en) | 2018-11-20 | 2018-11-20 | Method, device, server and storage medium for client gray scale release |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811384519.9A CN109739527B (en) | 2018-11-20 | 2018-11-20 | Method, device, server and storage medium for client gray scale release |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109739527A CN109739527A (en) | 2019-05-10 |
| CN109739527B true CN109739527B (en) | 2022-07-08 |
Family
ID=66356970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811384519.9A Active CN109739527B (en) | 2018-11-20 | 2018-11-20 | Method, device, server and storage medium for client gray scale release |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109739527B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110377327A (en) * | 2019-06-19 | 2019-10-25 | 平安普惠企业管理有限公司 | Production environment gray scale issues monitoring method, equipment, storage medium and device |
| CN110489133A (en) * | 2019-08-23 | 2019-11-22 | 亿企赢网络科技有限公司 | A kind of gray scale dissemination method, system and electronic equipment and storage medium |
| CN111290867A (en) * | 2020-02-27 | 2020-06-16 | 北京三快在线科技有限公司 | Traffic scheduling method, service server, storage medium and traffic scheduling system |
| CN112416385A (en) * | 2020-08-13 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Acquisition component management method and system |
| CN112287183A (en) * | 2020-10-30 | 2021-01-29 | 北京字节跳动网络技术有限公司 | Link topology graph display method and device and computer storage medium |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176790A (en) * | 2011-12-26 | 2013-06-26 | 阿里巴巴集团控股有限公司 | Application releasing method and application releasing system |
| WO2014175998A1 (en) * | 2013-04-24 | 2014-10-30 | Linkedin Corporation | Updating a front end client |
| CN105791341A (en) * | 2014-12-22 | 2016-07-20 | 华为软件技术有限公司 | Method, device and system for processing application release |
| CN106257894A (en) * | 2016-08-29 | 2016-12-28 | 北京海誉动想科技股份有限公司 | Gray scale dissemination method based on micro services |
| CN107733710A (en) * | 2017-10-17 | 2018-02-23 | 平安科技（深圳）有限公司 | Construction method, device, computer equipment and the storage medium of link call relation |
| CN108345462A (en) * | 2018-01-11 | 2018-07-31 | 华为技术有限公司 | The method and apparatus of component upgrade |
| CN108376118A (en) * | 2018-02-09 | 2018-08-07 | 腾讯科技（深圳）有限公司 | Service delivery system, method, equipment and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135895B (en) * | 2010-12-29 | 2013-08-28 | 华为软件技术有限公司 | System upgrading method and system |
| US20170139808A1 (en) * | 2015-11-13 | 2017-05-18 | Le Holdings (Beijing) Co., Ltd. | Method and dispatcher node for server processing management |
| US10114665B2 (en) * | 2015-11-18 | 2018-10-30 | Level 3 Communications, Llc | Communication node upgrade system and method for a communication network |
| CN107229487B (en) * | 2016-03-25 | 2020-09-29 | 阿里巴巴集团控股有限公司 | Code processing method and device |
| CN107463390B (en) * | 2016-06-02 | 2020-12-01 | 阿里巴巴集团控股有限公司 | Software upgrading method and upgrading server |
| CN108268271A (en) * | 2016-12-29 | 2018-07-10 | 华为技术服务有限公司 | The upgrade method and update device of micro services |
-
2018
- 2018-11-20 CN CN201811384519.9A patent/CN109739527B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176790A (en) * | 2011-12-26 | 2013-06-26 | 阿里巴巴集团控股有限公司 | Application releasing method and application releasing system |
| WO2014175998A1 (en) * | 2013-04-24 | 2014-10-30 | Linkedin Corporation | Updating a front end client |
| CN105791341A (en) * | 2014-12-22 | 2016-07-20 | 华为软件技术有限公司 | Method, device and system for processing application release |
| CN106257894A (en) * | 2016-08-29 | 2016-12-28 | 北京海誉动想科技股份有限公司 | Gray scale dissemination method based on micro services |
| CN107733710A (en) * | 2017-10-17 | 2018-02-23 | 平安科技（深圳）有限公司 | Construction method, device, computer equipment and the storage medium of link call relation |
| CN108345462A (en) * | 2018-01-11 | 2018-07-31 | 华为技术有限公司 | The method and apparatus of component upgrade |
| CN108376118A (en) * | 2018-02-09 | 2018-08-07 | 腾讯科技（深圳）有限公司 | Service delivery system, method, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| Clustering software artifacts based on frequent;D. Beyer;《https://ieeexplore.ieee.org/abstract/document/1421041》;20050516;全文第1-10页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109739527A (en) | 2019-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109739527B (en) | Method, device, server and storage medium for client gray scale release | |
| CN104834602B (en) | A kind of program dissemination method, device and program delivery system | |
| US9355005B2 (en) | Detection apparatus and detection method | |
| CN114356557B (en) | Cluster capacity expansion method and device | |
| CN112241350B (en) | Micro-service evaluation method and device, computing device and micro-service detection system | |
| US20070168201A1 (en) | Formula for automatic prioritization of the business impact based on a failure on a service in a loosely coupled application | |
| JP2017201470A (en) | Setting support program, setting support method, and setting support device | |
| US11669374B2 (en) | Using machine-learning methods to facilitate experimental evaluation of modifications to a computational environment within a distributed system | |
| EP4122163A1 (en) | Causality determination of upgrade regressions via comparisons of telemetry data | |
| CN109032954B (en) | User selection method and device for A/B test, storage medium and terminal | |
| CN112068935B (en) | Kubernetes program deployment monitoring method, kubernetes program deployment monitoring device and kubernetes program deployment monitoring equipment | |
| CN111562884B (en) | Data storage method and device and electronic equipment | |
| CN113704117A (en) | Algorithm testing system, method and device | |
| CN110737548B (en) | Data request method and server | |
| CN115495142A (en) | Cloud resource arranging method and device, computer equipment and storage medium | |
| CN110096305A (en) | Gray scale dissemination method, device, equipment and storage medium | |
| CN109726124B (en) | Test system, test method, management device, test device and computing equipment | |
| CN116633766A (en) | Fault processing method and device, electronic equipment and storage medium | |
| US20220066917A1 (en) | Candidate program release evaluation | |
| CN114385498A (en) | Performance test method, system, computer equipment and readable storage medium | |
| CN114064343A (en) | Abnormal handling method and device for block chain | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN114065190A (en) | High-availability and high-safety algorithm automatic online test system | |
| CN111884932A (en) | Link determination method, device, equipment and computer readable storage medium | |
| CN111597047A (en) | Service deployment method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |