CN109391655B - Service gray level publishing method, device and system and storage medium - Google Patents

Service gray level publishing method, device and system and storage medium Download PDF

Info

Publication number
CN109391655B
CN109391655B CN201710674368.XA CN201710674368A CN109391655B CN 109391655 B CN109391655 B CN 109391655B CN 201710674368 A CN201710674368 A CN 201710674368A CN 109391655 B CN109391655 B CN 109391655B
Authority
CN
China
Prior art keywords
service
server
response result
gray scale
version
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
Application number
CN201710674368.XA
Other languages
Chinese (zh)
Other versions
CN109391655A (en
Inventor
宁海波
李欢
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201710674368.XA priority Critical patent/CN109391655B/en
Publication of CN109391655A publication Critical patent/CN109391655A/en
Application granted granted Critical
Publication of CN109391655B publication Critical patent/CN109391655B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Abstract

The embodiment of the application provides a service gray scale publishing method, a device, a system and a storage medium, wherein the method comprises the following steps: s1', the service gray level issuing device sets the initial value of the gray level issuing percentage; s2', the service gray level issuing device sends the current gray level issuing percentage to a second service system; s3', at least one second server in the second service system determining a service request screening condition, screening a service request satisfying the service request screening condition from the received service requests, responding to the screened service request, and sending the remaining service requests to the first service system; s4', at least one first server in the first service system responding to the rest of the service requests; s5', the service gray level issuing device obtains the first response result from the second service system, and if the first response result is correct and the current gray level issuing percentage is less than 1, the current gray level issuing percentage is increased, and the process returns to S2'.

Description

Service gray level publishing method, device and system and storage medium
Technical Field
The present application relates to the field of server technologies, and in particular, to a service gray scale distribution method, a service gray scale distribution apparatus, a service gray scale distribution system, and a non-volatile computer-readable storage medium.
Background
The current users use various services on the internet, such as a VIP user information query service for Tencent videos, an information sharing service on WeChat videos, and the like, and these services usually need to be continuously updated to better implement their functions and meet the user requirements. Each release of the service version affects hundreds of millions of users, so that the network service provider mostly adopts a gray release method when releasing the new service version.
Disclosure of Invention
The application provides a service gray scale publishing method, which is executed by a service gray scale publishing device, a first service system and a second service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the method comprises the following steps:
s1', the service gray level issuing device sets the initial value of the gray level issuing percentage;
s2', the service gray scale publishing device sends the current gray scale publishing percentage to the second service system;
s3', the at least one second server in the second service system determining a service request screening condition according to the current gray scale issue percentage, screening a service request satisfying the service request screening condition from the received service requests, responding to the screened service request, and sending the remaining service requests to the first service system;
s4', the at least one first server in the first service system responding to the rest of the service requests;
s5', the service gray scale issuing device obtains a first response result from the second service system, if the first response result is correct and the current gray scale issuing percentage is less than 1, the current gray scale issuing percentage is increased, and the operation returns to S2'; wherein the first response result is a response result of the second version of the first service on the at least one second server to the screened service request.
In some examples, the S3' may further include: the at least one second server sends the screened service request to the first service system; and, the S4' further includes: the at least one first server responds to the screened service request; wherein the method for determining whether the first response result is correct in S5' includes: the service gray scale issuing device acquires a second response result from the first service system, and determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result; the second response result is a response result of the first service of the first version on the at least one first server to the screened service request.
In some examples, the S5' may further include: and if the service gray scale issuing device determines that any one of the first response results is wrong, feeding back a second response result corresponding to the wrong first response result to the initiating end of the corresponding service request.
In some examples, the S5' may further include: if the service gray scale issuing device determines that any one of the first response results is wrong, setting the current gray scale issuing percentage as the last gray scale issuing percentage, and sending a message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction; and returns to S2' after receiving the message of completion of correction returned by the monitoring system.
In some examples, the S5' may further include: and if the service gray scale issuing device determines that the first response result is correct and the current gray scale issuing percentage is 1, indicating the second service system to disconnect from the first service system so as to enable the at least one second server to respond to all received service requests.
The embodiment of the application provides a service gray level release method, which is used for releasing a first service of a second version through a first service system and a second service system connected with the first service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the method comprises the following steps:
s1, setting an initial value of the gray level release percentage;
s2, sending the current gray scale distribution percentage to the second service system, so that the at least one second server determines a service request screening condition according to the current gray scale distribution percentage, screens out a service request satisfying the service request screening condition from the received service requests, responds to the screened service request, and sends the remaining service requests to the first service system, so that the at least one first server responds to the remaining service requests;
s3, obtaining a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
and S4, if the first response result is correct and the current gray scale issue percentage is less than 1, increasing the current gray scale issue percentage, and returning to S2.
In some examples, the screened service request is sent by the at least one second server to the first service system to cause the at least one first server to respond to the screened service request; the method for determining whether the first response result is correct comprises the following steps: obtaining a second response result from the first service system, wherein the second response result is a response result of the first service of the first version on the at least one first server to the screened service request; and determining whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
In some examples, the S4 may further include: and if any one of the first response results is wrong, feeding back a second response result corresponding to the wrong first response result to the initiating end corresponding to the service request.
In some examples, the S4 may further include: if any one of the first response results is wrong, setting the current gray scale release percentage as the last gray scale release percentage, and sending a message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction; and returning to the step S2 after receiving the message of finishing the correction returned by the monitoring system.
In some examples, the method further comprises: and if the first response result is correct and the current gray scale release percentage is 1, indicating the second service system to disconnect from the first service system so that the at least one second server responds to all received service requests.
The application example provides a service gray level release device, which is used for releasing a first service of a second version through a first service system and a second service system connected with the first service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the device comprises:
the initialization module is used for setting an initial value of the gray level release percentage;
the request screening module is used for sending the current gray level release percentage to the second service system so that the at least one second server determines a service request screening condition according to the current gray level release percentage, screens out service requests meeting the service request screening condition from the received service requests, responds to the screened service requests and sends the rest of the service requests to the first service system so that the at least one first server responds to the rest of the service requests;
a result obtaining module, configured to obtain a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
and the proportion increasing module is used for increasing the current gray scale release percentage and enabling the first request screening module to execute the processing of sending the current gray scale release percentage to the second service system when the first response result is correct and the current gray scale release percentage is less than 1.
In some examples, the screened service request may be further sent to the first service system by the at least one second server, so that the at least one first server responds to the screened service request; the scale-up module may include a result determination unit to determine whether the first response result is correct; the result determination unit may include: an obtaining subunit, configured to obtain a second response result from the first service system, where the second response result is a response result of the first service of the first version on the at least one first server to the screened service request; and the determining subunit determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
In some examples, the scale-up module may further include: and the feedback unit feeds back a second response result corresponding to the wrong first response result to the initiating end corresponding to the service request when any one of the first response results is wrong.
In some examples, the scale-up module may further include: the error reporting unit is used for setting the current gray scale release percentage as the previous gray scale release percentage when any one of the first response results is wrong, and sending a message that the first response result is wrong to the monitoring system so as to enable the monitoring system to carry out problem positioning and correction; and after receiving a message of finishing correction returned by the monitoring system, enabling the first request screening module to execute the processing of sending the current gray scale release percentage to the second service system.
In some examples, the apparatus may further comprise: and the connection disconnection module is used for indicating the second service system to disconnect from the first service system when the first response result is correct and the current gray scale issue percentage is 1, so that the at least one second server responds to all received service requests.
The application example provides a service gray scale publishing system, which comprises: the system comprises a first service system and a second service system, wherein the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version; the system further comprises: the service gray scale issuing device is used for realizing any one of the methods.
The present examples provide a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps of any of the methods described above.
Based on the above technical solution provided by the example of the present application, although the second version of the first service is already deployed on the second server at the beginning, all the service requests are not responded by the second server, but an initial gray scale distribution percentage is set at the beginning, the service requests of the gray scale distribution percentage are responded by the second server, and meanwhile, the part of the service requests and the rest of the service requests are also responded by the first server, then the response results of the first server and the second server are compared, and whether to increase the gray scale distribution percentage is determined according to the comparison result. Therefore, the gray level issuing percentage is not issued one by one server, the gray level issuing percentage is irrelevant to the number of servers, the initial value and the increasing step length of the gray level issuing percentage do not depend on the number of servers, the gray level issuing percentage can be set independently, and the gray level issuing process with small step length can be realized according to the realization requirement even if the number of servers is small, so that the percentage of affected users can be controlled, and the effect of the gray level issuing of the service version is improved.
Drawings
In order to more clearly illustrate the technical solutions in the examples or prior art of the present application, the drawings used in the descriptions of the examples or prior art will be briefly introduced below, and it is obvious that the drawings in the following descriptions are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without inventive exercise.
FIG. 1 is a model diagram of a service gray publication process in an example of the present application;
FIG. 2 is a system architecture diagram to which an example of the present application relates;
FIG. 3 is a flow chart illustrating a service gray level publishing method according to an embodiment of the present application;
FIG. 4 is a flow chart illustrating a service gray level publishing method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a service gray scale distribution apparatus in an example of the present application;
FIG. 6 is a flow chart illustrating a service gray level publishing method according to an example of the present application;
FIG. 7 is a model diagram of an example of the present application before service gray scale distribution;
FIGS. 8-12 are schematic diagrams of models in a service gray release process according to an embodiment of the present application;
FIG. 13 is a model diagram illustrating a service gray release completion in an example of the present application;
FIG. 14 is a block diagram of a computer device according to an embodiment of the present application.
Detailed Description
In an example of the present application, as shown in fig. 1, assuming that a service needs to be deployed on n servers, that is, to replace a service running version x on n servers with a service running version x +1, the inventor adopts the following method when performing a gray release on a new version of the service: the new version, namely the service of the running version x +1, is released on one server, and then the second server is released according to the running condition of the server until the n servers are all provided with the new versions. Wherein n is the number of servers requiring the gray distribution, and is an integer greater than 1.
During the release process, the inventors found the following problems:
in the process of performing the gray distribution according to the number of servers, the step length of each gray distribution is 1/n, if n is 2, the first gray distribution percentage is 50%, and the step length is too large, so that the gray distribution mode cannot realize the gray distribution with small step length for the case that the number of servers is small, and the percentage of affected users cannot be controlled arbitrarily because the gray distribution percentage is determined by the number of servers.
In view of the above problem, the present embodiment provides a service gray scale publishing method, and a system architecture to which the method can be applied is shown in fig. 2. The system architecture comprises a service request initiating terminal 101, a first service system 102, a second service system 103 and a service gray scale issuing device 104; the hardware devices are connected through the internet 105 to realize information interaction, and the internet 105 can comprise a wired network and a wireless network; wherein:
the service request initiator 101 may be a user terminal, and the service request initiated at this time may be referred to as a user request, or may be a server, or may be sent by other hardware devices, and any hardware device that sends a service request may be referred to as a service request initiator.
The first service system 102 includes at least one first server, and the first server has a first version of the first service deployed thereon.
The second service system 103 includes at least one second server, where a second version of the first service is deployed on the at least one second server, and the second version is higher than the first version.
The first service may be any internet service, such as a VIP user information query service for Tencent videos, an information sharing service on WeChat, a video information search service, and the like. Since the first service is deployed on both the first server and the second server, the version of the first service deployed on the second server is only higher than the version of the first service deployed on the first server. In addition, the number of the first servers in the first service system 102 and the number of the second servers in the second service system 103 may be different or the same.
The service gray-scale distribution apparatus 104, for example, a service gray-scale distribution server, is independent of the first service system 102 and the second service system 103, and is configured to distribute the first service of the second version through the first service system 102 and the second service system 103 connected to the first service system 102.
Before the gray scale issue is not executed, the service request is sent to the second service system 103, and then the second service system 103 transmits the service request to the first service system 102, and the first service system 102 responds to the service request, so as to ensure that the service request can obtain a correct response. It can be seen that the first service system 102 is a system currently responding to a service request, and the second service system 103 is a system that is to replace the first service system 102 to respond to a service request, where the so-called service gray-scale distribution method is a process of gradually replacing the first service system 102 with the second service system 103. The service gray scale distribution method provided by the present embodiment is described below, and the method may be executed by the service gray scale distribution apparatus 104 (for example, the service gray scale distribution server), and specifically, with reference to fig. 3, may include the following steps:
s1, setting an initial value of the gray level release percentage;
in practical application, the initial value of the gray release percentage can be set by the user according to needs, and is not determined by the number of servers. A smaller percentage of greyscale distribution may be set, for example to a smaller value of 1%, 5% etc., so that the percentage of affected users may be reduced in case of a problem with the first service of the second version. When the gray release percentage is 0, the service request is completely responded to by the first server in the first service system 102.
S2, sending the current gray scale distribution percentage to the second service system 103, so that the at least one second server determines a service request screening condition according to the current gray scale distribution percentage, screens out a service request satisfying the service request screening condition from the received service requests, responds to the screened service request, and sends the remaining service requests to the first service system 102, so that the at least one first server responds to the remaining service requests;
the service request is sent to the first service system 102 or the second service system 103, and is responded by the first service, so that the service request corresponds to the first service, because the request responded by the first service is sent to the first service system 102 or the second service system 103, for example, the first service is a VIP user information query service of flight video, the service request is a VIP user information query request of flight video, and other service requests are not sent to the first server and the second server.
In this step, there are various ways to determine the service request screening condition according to the current gray scale distribution percentage, and one of the ways is exemplified by taking a certain query service as a first service: assuming that the current gray release percentage is 1%, the service request is a user request, the identity or login account of the user sending the user request is 5 digits, the range of the last two digits of the identity or login account is 00-99, and the service request screening condition set for the situation is that the last two digits of the identity are 00, that is, if the user request received by the second service system 103 corresponds to the identity of the user or the mantissa of the login account is 00, the user request with the identity or login account mantissa of 01-99 is screened out for response, and is sent to the first service system 102 and responded by the first service system 102. Similarly, if the gray release percentage is 5%, the user requests with the ID or login account mantissas of 00-04 are screened out.
In this step, the first version is lower than the second version, and the service of the first version is stable and can perform a correct response, compared to the case where the first version is an old version, and the second version is a new version and cannot determine whether it can perform a correct response. The rest of the service requests are sent to the first service system 102 by the second service system 103, that is, the rest of the service requests are responded by the first service of the first version, so as to ensure that the rest of the service requests can be correctly responded. As for the screened service request, the service request is equivalent to the service request for test, and the second service system 103 responds, that is, the first service of the second version responds, so as to determine whether the first service of the second version responds correctly.
S3, obtaining a first response result from the second service system 103, where the first response result is a response result of the second version of the first service on the at least one second server to the screened service request;
and S4, if the first response result is correct and the current gray scale issue percentage is less than 1, increasing the current gray scale issue percentage, and returning to S2.
In this step, if the first response result is correct, that is, the second version of the first service can respond correctly to the screened service request, and the percentage of the grayness issue at this time has not reached 100%, the percentage of the grayness issue is increased, and then the process returns to step S2 to continue to participate in the loop.
For example, assuming that the initial value of the gray scale distribution percentage is 1%, the service gray scale distribution device 104 sends the ratio to the second service system 103, so that each second server in the second service system 103 determines the service request screening condition according to the ratio, then screens the received service requests to screen the service requests meeting the service request screening condition, then responds to the screened service requests, and sends the remaining service requests to the first service system 102, so that the first service system 102 responds to the remaining service requests to ensure that the remaining service requests can obtain the contended responses. The service gray scale issuing device 104 confirms the response result of the second service system 103 to the screened service request, that is, the first response result, and if the response result is correct, increases the gray scale issuing percentage to 5%, and then sends the proportion to the second service system 103, and the second service system 103 sets the processes of the service request screening condition according to 5%, and so on, until the gray scale issuing percentage is 100% when the first response result is confirmed to be correct.
Based on the above analysis, in the service gray scale distribution method provided in the embodiment of the present application, the gray scale distribution percentage is not determined by the number of servers, and can be set arbitrarily, and even if the number of servers is small, the gray scale distribution process with a small step size can be implemented, so that the percentage of affected users can be controlled.
In some examples, there are multiple ways to determine whether the first response result is correct, where one way is comparison, in order to compare the response result of the second version of the first service to the service request with the response result of the first version of the first service to the service request, the second service system 103 may send the screened service request to the first service system 102, so that the at least one first server responds to the screened service request. That is, the screened service request is responded to by both the first service of the second version in the second service system 103 and the first service of the first version in the first service system 102. The method of thus determining whether the first response result is correct comprises:
obtaining a second response result from the first service system 102, where the second response result is a response result of the first service of the first version on the at least one first server to the screened service request; and determining whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
Because the response accuracy of the first service version of the first version to the service request is higher, if the comparison result of the first response result and the second response result is consistent, the first response result is correct, and if the comparison result is inconsistent, the first response result is incorrect, so that the judgment of the first response result is realized.
It can be understood that the first response result and the second response result of the comparison are for the same service request, and the first response result and the second response result of each service request that is screened out are compared and consistent to each other, so that the comparison result is considered to be consistent, and if the first response result and the second response result of one of the service requests are not consistent, the comparison result is not considered to be consistent, and therefore, the operations of increasing the gray scale issue percentage and returning to step S2 cannot be performed. In addition, the running condition of the first service of the second version can be observed in real time through a comparison mode.
In some examples, if any one of the first response results is wrong, a second response result corresponding to the wrong first response result may be fed back to the originating terminal 101 of the corresponding service request. That is, the first response result of at least one of the service requests is inconsistent with the corresponding second response result, and the second response result corresponding to the wrong first response result is sent to the sending end of the service request, so as to ensure that the sending end of the service request can obtain a correct response.
In some examples, if any one of the first response results is wrong, the current gray scale issue percentage may be set as the last gray scale issue percentage, and a message that the first response result is wrong is sent to the monitoring system, so that the monitoring system performs problem location and correction; and returning to the step S2 after receiving the message of finishing the correction returned by the monitoring system.
For example, if the current gray scale issuance percentage is 5%, it is determined that at least one of the first response results is inconsistent with the corresponding second response result, the gray scale issuance percentage is rolled back to 1% of the previous gray scale issuance percentage, and the error information is reported to the monitoring system, the monitoring system performs problem location by searching a log or other methods, performs error correction after the problem location, returns a message of completion of correction to the service gray scale issuance device 104 after the correction is completed, and returns to S2 after the service gray scale issuance device 104 receives the message, and continues to participate in the cycle. The mode of sending the wrong message to the monitoring system for problem positioning and repairing is an active mode, the problem can be positioned and solved without waiting for the user to feed back the problem, and the problem can be found and corrected more timely.
In some examples, if the current gray scale distribution percentage is 1 and the first response result at the gray scale distribution percentage is correct, it indicates that the first service of the first version can be replaced by the first service of the second version to respond to the service request, and the first service of the first version is not used to respond, at this time, the second service system may be instructed to disconnect from the first service system, so that the at least one second server responds to all received service requests, thereby implementing the distribution work of the first service of the second version.
The service gray scale publishing method provided by the embodiment of the application is exemplified by referring to fig. 4;
s401, setting an initial value of the gray level release percentage;
s402, sending the current gray level release percentage to the second service system so that the at least one second server determines a service request screening condition according to the current gray level release percentage, screens out service requests meeting the service request screening condition from the received service requests, responds to the screened service requests and sends the rest of the service requests to the first service system so that the at least one first server responds to the rest of the service requests;
s403, obtaining a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
s404, obtaining a second response result from the first service system, wherein the second response result is a response result of the first service of the first version on the at least one first server to the screened service request;
s405, judging whether each first response result is consistent with the corresponding second response result; if so, executing S406, otherwise, setting the current gray scale release percentage as the last gray scale release percentage, and sending the message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction; after receiving the message of completing the correction returned by the monitoring system, returning to S402;
s406, judging whether the current gray level release percentage is 100%; if yes, executing S407; otherwise, increasing the current gray level release percentage and returning to S402;
s407, disconnecting the first service system from the second service system, namely removing the first service system, and ending the gray scale publishing process.
It can be understood that the main executing body of the steps S401 to 407 is a service gray scale distribution device, such as a service gray scale distribution server. Where there is no necessarily a sequential relationship between steps S403 and S404, step S403 may be performed prior to, simultaneously with, or after step S404.
In the above process, the control of the gray distribution percentage can be realized by setting the initial value and the increasing step length of the gray distribution percentage, rather than determining the step length of the gray distribution percentage by the number of servers. And moreover, when a problem occurs, the problem is reported to the monitoring system in time so that the monitoring system can locate and repair the problem in time, the problem can be found in time, the problem is solved in an active mode, and the problem is not solved until the user feeds back the problem. And moreover, the gray level publishing percentage is rolled back to the last gray level publishing percentage, so that the influence on the service is reduced as much as possible.
One example of the application provides a service gray scale publishing device, which is used for publishing a first service of a second version through a first service system and a second service system connected with the first service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
as shown in fig. 5, the apparatus 500 includes:
an initialization module 501, which sets an initial value of the gray release percentage;
a request screening module 502, configured to send the current gray scale issue percentage to the second service system, so that the at least one second server determines a service request screening condition according to the current gray scale issue percentage, screens out a service request meeting the service request screening condition from the received service requests, responds to the screened service request, and sends the remaining service requests to the first service system, so that the at least one first server responds to the remaining service requests;
a result obtaining module 503, configured to obtain a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
a proportion increasing module 504, configured to increase the current gray scale distribution percentage when the first response result is correct and the current gray scale distribution percentage is smaller than 1, and enable the first request screening module 502 to execute the processing of sending the current gray scale distribution percentage to the second service system.
In some examples, the screened service request may be further sent to the first service system by the at least one second server, so that the at least one first server responds to the screened service request; the scale-up module 504 may include a result determination unit to determine whether the first response result is correct; the result determination unit may include:
an obtaining subunit, configured to obtain a second response result from the first service system, where the second response result is a response result of the first service of the first version on the at least one first server to the screened service request;
and the determining subunit determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
In some examples, the proportion increase module 504 may further include:
and the feedback unit feeds back a second response result corresponding to the wrong first response result to the initiating end corresponding to the service request when any one of the first response results is wrong.
In some examples, the proportion increase module 504 may further include:
the error reporting unit is used for setting the current gray scale release percentage as the previous gray scale release percentage when any one of the first response results is wrong, and sending a message that the first response result is wrong to the monitoring system so as to enable the monitoring system to carry out problem positioning and correction; after receiving the message of completing the correction returned by the monitoring system, the first request screening module 502 is made to execute the processing of sending the current gray scale issue percentage to the second service system.
In some examples, the apparatus 500 may further include:
and the connection disconnection module is used for indicating the second service system to disconnect from the first service system when the first response result is correct and the current gray scale issue percentage is 1, so that the at least one second server responds to all received service requests.
It can be understood that, the service gray level publishing device provided in the embodiment of the present application is a functional architecture module of the service gray level publishing method, and the explanation, example, beneficial effects and the like of relevant contents thereof may refer to corresponding contents in the service gray level publishing method, and are not described herein again.
An example of the application provides a service gray scale distribution system which comprises a first service system, a second service system and a service gray scale distribution device. Wherein:
the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version; the service gray level issuing device is a hardware device for executing the service gray level issuing method.
It can be understood that the service gray scale publishing system provided by the embodiment of the present application includes the service gray scale publishing device, and the explanation, example, beneficial effect and the like of the relevant contents may refer to the corresponding contents above, and are not described herein again.
An example of the present application provides a service gray scale distribution method based on the service gray scale distribution system, as shown in fig. 6, the method generally includes:
s1', the service gray level issuing device sets the initial value of the gray level issuing percentage;
s2', the service gray scale publishing device sends the current gray scale publishing percentage to the second service system;
s3', the at least one second server in the second service system determining a service request screening condition according to the current gray scale issue percentage, screening a service request satisfying the service request screening condition from the received service requests, responding to the screened service request, and sending the remaining service requests to the first service system;
s4', the at least one first server in the first service system responding to the rest of the service requests;
s5', the service gray scale issuing device obtains a first response result from the second service system, if the first response result is correct and the current gray scale issuing percentage is less than 1, the current gray scale issuing percentage is increased, and the operation returns to S2'; wherein the first response result is a response result of the second version of the first service on the at least one second server to the screened service request.
It is understood that, in the present embodiment, for the explanation, examples, and beneficial effects of the steps S1 'to S5', reference may be made to the corresponding parts in the foregoing, and details are not described herein again.
In some examples, the S3' may further include: the at least one second server sends the screened service request to the first service system; and, the S4' may further include: the at least one first server responds to the screened service request;
thus, the method for determining whether the first response result is correct in S5' includes:
the service gray scale issuing device acquires a second response result from the first service system, and determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result; the second response result is a response result of the first service of the first version on the at least one first server to the screened service request.
In some examples, the S5' may further include: and if the service gray scale issuing device determines that any one of the first response results is wrong, feeding back a second response result corresponding to the wrong first response result to the initiating end of the corresponding service request.
In some examples, the S5' may further include: if the service gray scale issuing device determines that any one of the first response results is wrong, setting the current gray scale issuing percentage as the last gray scale issuing percentage, and sending a message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction; and returns to S2' after receiving the message of completion of correction returned by the monitoring system.
In some examples, the S5' may further include: and if the service gray scale issuing device determines that the first response result is correct and the current gray scale issuing percentage is 1, indicating the second service system to disconnect from the first service system so as to enable the at least one second server to respond to all received service requests.
In addition, in some examples, the first service system and the second service system may include, but are not limited to, only servers, and may also include, for example, a load balancing fault tolerance device, which may also be referred to as L5, and mainly functions to perform load balancing and fault tolerance, specifically: it collects the idle state of background server group, provides load balancing access to the request sent to the background server, to avoid some servers in overload state and some servers in idle state; the system also provides overload protection, and judges whether to continuously send requests to the background server according to the packet returning state of the background server, so as to prevent the background server from generating faults due to overlarge pressure caused by excessive requests to be processed, and prevent a certain server from continuously sending requests to the server after the server breaks down to cause avalanche. Therefore, a load balancing fault-tolerant device is arranged between the sending end of the service request and the background server, and the background server can be protected to a certain extent.
Here, the load balancing fault tolerant apparatus provided in the first service system may be referred to as a first load balancing fault tolerant apparatus, and the load balancing fault tolerant apparatus provided in the second service system may be referred to as a second load balancing fault tolerant apparatus. The mapping port of the first load balancing fault-tolerant device comprises a first port, and the first port corresponds to the first service of the first version; the mapping port of the second load balancing fault-tolerant device comprises a second port, and the second port corresponds to the first service of the second version. Therefore, when a service request is sent to the second service system to send the service request, the second load balancing fault-tolerant device can be mapped to the second port of the second server, so that the sent service request can be sent to the second port of the second server, and the first service of the second version on the second server responds. When a service request is sent to the first service system, the first load balancing fault-tolerant device may send the sent service request to the first port of the first server, and the first service of the first version on the first server responds.
In an actual scene, before service gray scale distribution, a first service system responds to a service request, a second service system does not exist in the whole model, when the service gray scale distribution is needed, the second service system needs to be added into the model, the service request needs to be sent to the second service system firstly, then the second service system is transmitted to the first service system, the first service system responds to the service request, then the service gray scale distribution device is used for performing the service gray scale distribution, the second service system gradually replaces the first service system, and after the service gray scale distribution is completed, the first service system is removed from the model, and the second service system completely replaces the first service system.
The following describes in detail the service gray level distribution process of the service gray level distribution system by taking the VIP user information query service of the Tencent video as an example and combining fig. 7 to 13:
the VIP user information inquiry service of the Tencent video is a service which is specially used for terminal users to inquire whether the user is a VIP user, if the inquired user is the VIP user, the server returns core sensitive information related to the member, such as the grade of the user, the member starting time, the member ending time, whether the member is an annual fee member, the member points and the like. The VIP user information query service of the first version (for example, the old version) takes Vipid as a keyword of the system, and after the member background pipelining system is newly modified, the VIP user information query service of the second version (for example, the new version) takes vuserid as the keyword of the system.
Referring to table 1 below, assuming that a port of the first version of the VIP user information query service spp _ server _ OLD on the server is 13149, the port 13149 may be referred to as a first port, the first version of the VIP user information query service spp _ server _ OLD is deployed on 13 first servers (for example, OLD servers), a load balancing fault tolerance device is disposed between the user terminal and the 13 first servers, and is denoted as a first load balancing fault tolerance device OLD _ L5, a data set configured on the OLD _ L5 may be mapped to an IP address and a port 13149 of the 13 first servers, and the 13 first servers and the first load balancing fault tolerance device OLD _ L5 form a first service system. The query request sent by the user through the terminal reaches the port 13149 of the first server through the first load balancing fault tolerant device OLD _ L5, and the query request is responded by the VIP user information query service spp _ server _ OLD of the first version.
Table 1 relevant data table corresponding to OLD _ L5
Figure BDA0001373895750000181
Referring to table 2 below, a port on the server corresponding to the second version of VIP user information query service spp _ server _ new is 20048, the port 20048 may be referred to as a second port, the second version of VIP user information query service spp _ server _ new is deployed on 4 second servers (e.g., new servers), a load balancing fault tolerant device is deployed between the user terminal and the 4 second servers, the load balancing fault-tolerant device is denoted as a second load balancing fault-tolerant device NEW _ L5, and a data group configured on NEW _ L5 may be mapped to the IP addresses and ports 13149 of 13 first servers, or may be mapped to the IP addresses and ports 20048 of 4 second servers, therefore, the query request sent by the user through the terminal thereof can reach the port 13149 of the first server through the second load balancing fault-tolerant device NEW _ L5, and the VIP user information query service spp _ server _ old of the first version responds to the query request. The query request sent by the user through the terminal thereof can also reach the port 20048 of the second server through the second load balancing fault tolerance device NEW _ L5, and the VIP user information query service spp _ server _ NEW of the second version responds to the query request.
TABLE 2NEW _ L corresponding associated data sheet
Figure BDA0001373895750000191
As shown in fig. 7, a model for operating a first version of VIP user information query service in a current operating environment is that a user terminal accesses a first version of VIP user information query service (for example, an operating version X) on a first server through OLD _ L5, the number of servers in the model is 13, the 13 first servers perform load balancing through OLD _ L5, and a corresponding service port is a first port, that is, a port 13149.
Step S701, as shown in fig. 8, a second load balancing fault-tolerant apparatus NEW _ L5 is newly built, and ports that can be mapped by the NEW _ L5 include a first port, i.e., port 13149, and a second port, i.e., port 20048. The second load balancing fault tolerant device NEW _ L5 replaces the first load balancing fault tolerant device OLD _ L5, and the terminal can access the first port of the first server through NEW _ L5 at this time, and the query request of the user is responded by the first version of VIP user information query service because the first server is running or the first version of VIP user information query service at this time.
Step S702, as shown in fig. 9, provides four second servers, deploys the VIP user information query service of the first version to the four second servers, and adds all the four second servers to the current model, specifically, adds the mapping data set to the second load balancing fault-tolerant apparatus NEW _ L5, and adds the IP addresses and the first ports of the four second servers to the second load balancing fault-tolerant apparatus NEW _ L5, so that a total of 17 servers in the model are provided. The terminal can access the first port of the 17 servers through the second load balancing fault tolerance device NEW _ L5, and the first version of VIP user information query service on the 17 servers responds to the service request. At this time, the first version of VIP user information query service provides services for the user, so that the online operation service is not affected.
Step S703, as shown in fig. 10, removes all 13 first servers mapped by the second load balancing fault tolerance device NEW _ L5, and provides services only by 4 second servers. Because the second server is running the first version of VIP user information query service, the user terminal accesses the first port of the 4 second servers through the second load balancing fault tolerant device NEW _ L5, and the VIP user information query service of the first version responds to the service request, which does not affect the service running on the line.
Step S704, as shown in fig. 11, adding the removed 13 first servers and the first load balancing fault-tolerant device OLD _ L5 as the first service system to the model again, deploying the second version of VIP user information query service to the 4 second servers, sending the service request sent by the user terminal to the second port of the second server through the NEW _ L5, but at this time, the second server has a pass-through function, and can pass through all the service requests to the first load balancing fault-tolerant device OLD _ L5, and sending the service request to the first port of the 13 first servers by the first load balancing fault-tolerant device OLD _ L5, so that at this time, the VIP user information query service of the first version on the first server still responds to the service request. Since the service is actually provided by the first version of the VIP user information query service at this time, the traffic running on the line is still not affected.
Step S705, as shown in fig. 12, adds a service gray scale distribution server to the model, connects the service gray scale distribution server to both the first service system and the second service system, and controls the gray scale distribution percentage of the second service system by the service gray scale distribution server, regardless of how small the step size is. For example, the initial value of the gray scale publishing percentage of the service gray scale publishing server is controlled to be 1%, then the gray scale publishing percentage is sent to the second service system, the second service system determines that the service request screening condition is that the last two digits of the Vuserid are 00 according to the gray scale publishing percentage, further sends the service request with the last two digits of the Vuserid being 01-99 to the first load balancing fault-tolerant device OLD _ L5, responds by the VIP user information query service of the first version on the first server, responds by the VIP user information query service of the second version on the second server with the service request with the last two digits of the Vuserid being 00, and simultaneously sends the 1% service request to the first load balancing fault-tolerant device OLD _ L5, and responds by the VIP user information query service of the first version on the first server. That is, each second server will respond to 1% of the service requests, and will also send the 1% and the remaining 99% of the service requests to the first service system, which will be responded to by the first service system. Then, the service gray scale issuing server obtains a first response result of the second service system to 1% of the service requests from the second service system, then obtains a second response result of the first service system to the same service requests from the first service system, and then compares and analyzes the first response result and the second response result to obtain whether the response result of the VIP user information inquiry service of the second version, namely the first response result, is correct. Judging whether the gray level release percentage is enlarged according to the comparison analysis result: and if the comparison and analysis result is that the response result of the VIP user information inquiry service of the second version is incorrect and abnormal, immediately controlling the gray scale release percentage of the second service system to roll back to 0 percent, namely, the state of all transparent transmission, reporting error information to a monitoring system, performing problem location by the monitoring system in a log searching mode and the like, repairing, then adjusting the gray scale release percentage to be 1 percent, and continuously controlling the gray scale release process. And if the comparison analysis result is that the response result of the VIP user information inquiry service of the second version is correct and no problem exists, expanding the gray release percentage to 5%, for example, and continuing the comparison analysis. In this way, the percentage of the gray-scale distribution is expanded to 100%, that is, 100% of the service requests are responded by both the VIP user information query service of the first version and the VIP user information query service of the second version, if the response results of the two are compared and analyzed to be normal, the 13 first servers and the first load balancing fault-tolerant device OLD _ L5 are removed, and the VIP user information query service of the second version on the second server is used to provide the service, so that the obtained model is as shown in fig. 13.
The service request in each step is necessarily a request for inquiring the VIP user information, that is, a request corresponding to the VIP user information inquiry service.
In the above example, in order to ensure the smooth transition from fig. 7 to fig. 12 and reduce the impact on the user caused by the NEW service release, a second load balancing fault tolerance device NEW _ L5 capable of mapping the first port and the second port is adopted to replace the first load balancing fault tolerance device OLD _ L5 (see fig. 8), then the second server is added in the model (see fig. 9), of course, the first version of service (for example, the service of the running version X) is still deployed on the second server at this time, then all the first servers are removed (see fig. 10), and only the second server responds, so far, although the load balancing fault tolerance device and the server are replaced, the first version of service still responds, and therefore, the online traffic of the user is still not affected at this time. Then, the removed first server and the first load balancing fault-tolerant device OLD _ L5 are added into the model, and a second version of the service is deployed on the second server, where the second server has a transparent transmission function and can transmit the received service request to the first service system (see fig. 11), and the online service of the user is still unaffected. Then, a service gray scale release server is added, a second version of service is deployed on a second server, then the gray scale release percentage of the second server is controlled by the service gray scale release server, comparison and analysis are carried out according to the operation results of the second server and the first server, then whether the gray scale release percentage is increased or not is determined (see fig. 12), in the process, abnormality or error is likely to occur, the online service cannot be influenced in the previous transition process (fig. 7 to fig. 11), and the influence of the service release process on the service can be reduced as much as possible by the smooth transition mode.
The present example also provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the above-described video-speech processing method (e.g., the above-described steps S1 to S4, and the above-described steps S401 to S407).
The storage medium may be various media such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, which can store program codes.
The present example also provides a computer device, which may be a service gray publication server, as shown in fig. 14, comprising one or more processors (CPUs) 1402, a communication module 1404, a memory 1406, a user interface 1410, and a communication bus 1408 for interconnecting these components, wherein:
the processor 1402 can receive and transmit data via the communication module 1404 to enable network communication and/or local communication.
User interface 1410 includes one or more output devices 1412 including one or more speakers and/or one or more visual displays. User interface 1410 also includes one or more input devices 1414, including, for example, a keyboard, a mouse, a voice command input unit or microphone, a touch screen display, a touch-sensitive input pad, a gesture-capture camera or other input buttons or controls, and the like.
Memory 1406 may be high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; or non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
Memory 1406 stores sets of instructions executable by processor 1402, including:
an operating system 1416, including programs for handling various basic system services and for performing hardware related tasks;
the application 1418 includes various application programs for gray scale distribution, which can implement the processing flow in the above examples, such as a part or all of the instruction modules or units in the service gray scale distribution apparatus 500. The processor 1402, by executing the machine-executable instructions in at least one of the units in the memory 1406, is able to implement the functionality of at least one of the units or modules described above.
It should be noted that not all steps and modules in the above flows and structures are necessary, and some steps or modules may be omitted according to actual needs. The execution order of the steps is not fixed and can be adjusted as required. The division of each module is only for convenience of describing adopted functional division, and in actual implementation, one module may be divided into multiple modules, and the functions of multiple modules may also be implemented by the same module, and these modules may be located in the same device or in different devices.
The hardware modules in the embodiments may be implemented in hardware or a hardware platform plus software. The software includes machine-readable instructions stored on a non-volatile storage medium. Thus, embodiments may also be embodied as software products.
In various examples, the hardware may be implemented by specialized hardware or hardware executing machine-readable instructions. For example, the hardware may be specially designed permanent circuits or logic devices (e.g., special purpose processors, such as FPGAs or ASICs) for performing the specified operations. Hardware may also include programmable logic devices or circuits temporarily configured by software (e.g., including a general purpose processor or other programmable processor) to perform certain operations.
In addition, each example of the present application can be realized by a data processing program executed by a data processing apparatus such as a computer. It is clear that a data processing program constitutes the present application. Further, the data processing program, which is generally stored in one storage medium, is executed by directly reading the program out of the storage medium or by installing or copying the program into a storage device (such as a hard disk and/or a memory) of the data processing device. Such a storage medium therefore also constitutes the present application, which also provides a non-volatile storage medium in which a data processing program is stored, which data processing program can be used to carry out any one of the above-mentioned method examples of the present application.
The corresponding machine-readable instructions of the modules of fig. 14 may cause an operating system or the like operating on the computer to perform some or all of the operations described herein. The nonvolatile computer-readable storage medium may be a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer. A CPU or the like mounted on the expansion board or the expansion unit may perform part or all of the actual operations according to the instructions.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (16)

1. A service gray scale publishing method is characterized by being executed by a service gray scale publishing device, a first service system and a second service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the method comprises the following steps:
s1', the service gray level issuing device sets the initial value of the gray level issuing percentage;
s2', the service gray scale publishing device sends the current gray scale publishing percentage to the second service system;
s3', the at least one second server in the second service system determining a service request screening condition according to the current gray scale issue percentage, screening a service request satisfying the service request screening condition from the received service requests, responding to the screened service request, and sending the remaining service requests to the first service system;
s4', the at least one first server in the first service system responding to the rest of the service requests;
s5', the service gray scale issuing device acquires a first response result from the second service system, if the first response result is correct and the current gray scale issuing percentage is less than 1, the current gray scale issuing percentage is increased based on the screened service request, and the S2' is returned; wherein the first response result is a response result of the second version of the first service on the at least one second server to the screened service request.
2. The method according to claim 1, wherein the S3' further comprises: the at least one second server sends the screened service request to the first service system; and, the S4' further includes: the at least one first server responds to the screened service request;
wherein the method for determining whether the first response result is correct in S5' includes:
the service gray scale issuing device acquires a second response result from the first service system, and determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result; the second response result is a response result of the first service of the first version on the at least one first server to the screened service request.
3. The method according to claim 2, wherein the S5' further comprises:
and if the service gray scale issuing device determines that any one of the first response results is wrong, feeding back a second response result corresponding to the wrong first response result to the initiating end of the corresponding service request.
4. The method of claim 3, wherein the S5' further comprises:
if the service gray scale issuing device determines that any one of the first response results is wrong, setting the current gray scale issuing percentage as the last gray scale issuing percentage, and sending a message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction; and returns to S2' after receiving the message of completion of correction returned by the monitoring system.
5. The method according to any one of claims 1 to 4, wherein the step S5' further comprises:
and if the service gray scale issuing device determines that the first response result is correct and the current gray scale issuing percentage is 1, indicating the second service system to disconnect from the first service system so as to enable the at least one second server to respond to all received service requests.
6. A service gray scale release method is characterized in that the method is used for releasing a second version of a first service through a first service system and a second service system connected with the first service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the method comprises the following steps:
s1, setting an initial value of the gray level release percentage;
s2, sending the current gray scale distribution percentage to the second service system, so that the at least one second server determines a service request screening condition according to the current gray scale distribution percentage, screens out a service request satisfying the service request screening condition from the received service requests, and responds to the screened service request, and sends the remaining service requests to the first service system, so that the at least one first server responds to the remaining service requests;
s3, obtaining a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
and S4, if the first response result is correct and the current gray scale release percentage is less than 1, increasing the current gray scale release percentage based on the screened service request, and returning to S2.
7. The method of claim 6, wherein the screened service request is sent by the at least one second server to the first service system to cause the at least one first server to respond to the screened service request;
the method for determining whether the first response result is correct comprises the following steps:
obtaining a second response result from the first service system, wherein the second response result is a response result of the first service of the first version on the at least one first server to the screened service request;
and determining whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
8. The method according to claim 7, wherein the S4 further comprises:
and if any one of the first response results is wrong, feeding back a second response result corresponding to the wrong first response result to the initiating end corresponding to the service request.
9. The method according to claim 8, wherein the S4 includes:
if any one of the first response results is wrong, setting the current gray scale release percentage as the last gray scale release percentage, and sending a message that the first response result is wrong to a monitoring system so as to enable the monitoring system to perform problem positioning and correction;
and returning to the step S2 after receiving the message of finishing the correction returned by the monitoring system.
10. The method of any one of claims 6 to 9, further comprising:
and if the first response result is correct and the current gray scale release percentage is 1, indicating the second service system to disconnect from the first service system so that the at least one second server responds to all received service requests.
11. A service gray scale distribution device is characterized in that the device is used for distributing a second version of a first service through a first service system and a second service system connected with the first service system; the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version;
the device comprises:
the initialization module is used for setting an initial value of the gray level release percentage;
the request screening module is used for sending the current gray level release percentage to the second service system so that the at least one second server determines a service request screening condition according to the current gray level release percentage, screening service requests meeting the service request screening condition from the received service requests, responding to the screened service requests, and sending the rest of the service requests to the first service system so that the at least one first server responds to the rest of the service requests;
a result obtaining module, configured to obtain a first response result from the second service system, where the first response result is a response result of the first service of the second version on the at least one second server to the screened service request;
and the proportion increasing module is used for increasing the current gray scale issuing percentage based on the screened service request and enabling the request screening module to execute the processing of sending the current gray scale issuing percentage to the second service system when the first response result is correct and the current gray scale issuing percentage is less than 1.
12. The apparatus of claim 11, wherein the screened service request is sent by the at least one second server to the first service system to cause the at least one first server to respond to the screened service request;
the proportion increase module comprises a result determination unit to determine whether the first response result is correct;
the result determination unit includes:
an obtaining subunit, configured to obtain a second response result from the first service system, where the second response result is a response result of the first service of the first version on the at least one first server to the screened service request;
and the determining subunit determines whether the first response result is correct or not according to a comparison result of the first response result and the second response result.
13. The apparatus of claim 12, wherein the scale-up module further comprises:
and the feedback unit feeds back a second response result corresponding to the wrong first response result to the initiating end corresponding to the service request when any one of the first response results is wrong.
14. A service gray scale distribution system, comprising: the system comprises a first service system and a second service system, wherein the first service system comprises at least one first server, and a first version of first service is deployed on the at least one first server; the second service system comprises at least one second server, and the first service of the second version is deployed on the at least one second server; the second version is higher than the first version; the system further comprises: a service gray scale distribution apparatus for implementing the method of any one of claims 6 to 10.
15. A non-transitory computer-readable storage medium, having stored thereon a computer program, wherein the program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.
16. A computer device comprising a memory and a processor, the memory having stored therein computer-readable instructions which, when executed by the processor, implement the method of any one of claims 1 to 10.
CN201710674368.XA 2017-08-09 2017-08-09 Service gray level publishing method, device and system and storage medium Active CN109391655B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710674368.XA CN109391655B (en) 2017-08-09 2017-08-09 Service gray level publishing method, device and system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710674368.XA CN109391655B (en) 2017-08-09 2017-08-09 Service gray level publishing method, device and system and storage medium

Publications (2)

Publication Number Publication Date
CN109391655A CN109391655A (en) 2019-02-26
CN109391655B true CN109391655B (en) 2021-09-24

Family

ID=65414687

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710674368.XA Active CN109391655B (en) 2017-08-09 2017-08-09 Service gray level publishing method, device and system and storage medium

Country Status (1)

Country Link
CN (1) CN109391655B (en)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120971B (en) * 2019-04-17 2022-12-06 北京奇艺世纪科技有限公司 Gray scale publishing method and device and electronic equipment
CN112181443B (en) * 2019-07-01 2023-04-07 中国移动通信集团浙江有限公司 Automatic service deployment method and device and electronic equipment
CN110647335A (en) * 2019-07-26 2020-01-03 平安科技（深圳）有限公司 Software gray level release method and device, electronic equipment and storage medium
CN110515675A (en) * 2019-08-30 2019-11-29 中国工商银行股份有限公司 Using online method, apparatus, system and readable storage medium storing program for executing
CN110737548B (en) * 2019-10-28 2022-06-10 聚好看科技股份有限公司 Data request method and server
CN111078468A (en) * 2019-11-21 2020-04-28 贝壳技术有限公司 Service rollback method and device under micro-service architecture
CN111399875B (en) * 2020-03-06 2023-09-05 咪咕文化科技有限公司 Gray scale upgrading control method and device, electronic equipment and storage medium
CN111488170A (en) * 2020-04-07 2020-08-04 支付宝(杭州)信息技术有限公司 Method, device and equipment for updating business processing model
CN112685287B (en) * 2020-11-30 2023-11-28 青岛海尔科技有限公司 Product data testing method and device, storage medium and electronic device
CN112202929B (en) * 2020-12-01 2021-03-26 湖南新云网科技有限公司 Service access method, device and equipment in micro-service architecture
CN113051182B (en) * 2021-04-30 2024-02-09 中国工商银行股份有限公司 Gray level publishing method, device and equipment based on distributed transaction
CN113542387B (en) * 2021-07-09 2023-07-04 平安银行股份有限公司 System release method and device, electronic equipment and storage medium

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020098468A1 (en) * 2001-01-23 2002-07-25 Avatar Technology, Inc. Method for constructing and teaching a curriculum
CN103176790B (en) * 2011-12-26 2016-04-20 阿里巴巴集团控股有限公司 Application dissemination method and system
CN103577660B (en) * 2012-07-19 2017-05-31 腾讯科技（深圳）有限公司 Gray scale experiment system and method
CN104102576A (en) * 2013-04-12 2014-10-15 阿里巴巴集团控股有限公司 Multi-version test method and device
CN104780057A (en) * 2014-01-13 2015-07-15 中兴通讯股份有限公司 Version upgrade processing method and device
US20160103758A1 (en) * 2014-10-08 2016-04-14 Yahoo! Inc. Online product testing using bucket tests
CN106066791A (en) * 2016-05-25 2016-11-02 合网络技术（北京）有限公司 The gray scale dissemination method of application and device

Also Published As

Publication number Publication date
CN109391655A (en) 2019-02-26

Similar Documents

Publication Publication Date Title
CN109391655B (en) Service gray level publishing method, device and system and storage medium
US10983880B2 (en) Role designation in a high availability node
CN104615455B (en) A kind of the IPMC program remote upgrading methods and device of ATCA frameworks
JP6431197B2 (en) Snapshot processing methods and associated devices
CN104301140A (en) Service request responding method, device and system
JP6120971B2 (en) How to establish a network socket with a data server
CN107948063B (en) Method for establishing aggregation link and access equipment
CN101262479B (en) A network file share method, server and network file share system
CN109120680B (en) Control system, method and related equipment
US10698642B2 (en) Remote management system and information processing method
CN111416851A (en) Method for session synchronization among multiple load balancers and load balancer
CN108595297B (en) UPI speed detection method and device
CN113626139B (en) High-availability virtual machine storage method and device
CN111800337B (en) Data center-based method and device, electronic equipment and storage medium
US7788379B2 (en) Network system and information processing method
CN103997422A (en) Fault processing method and device for IP interface board
CN112367386A (en) Ignite-based automatic operation and maintenance method, apparatus and computer equipment
CN104683153A (en) Cluster-based router host and spare MPU control method and system thereof
CN111416852A (en) Method for session synchronization among multiple load balancers and load balancer
JP6576556B2 (en) Communication device, communication processing method, communication processing apparatus, and communication system
JPWO2007096987A1 (en) Error control device
US11947431B1 (en) Replication data facility failure detection and failover automation
CN113098972B (en) Method and device for connecting with equipment, electronic equipment and storage medium
CN107426005B (en) Control method and system for restarting nodes in cloud platform
CN108108243B (en) Resource sharing system and method

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