CN110113189B - Method and device for positioning error node of release system - Google Patents

Abstract

The embodiment of the present invention discloses a method and device for locating an error node in a publishing system, wherein the method includes the following steps: generating a unique publishing id corresponding to the relevant data of the system to be published; During the project, output the release start information; when the first release project is called and ended, determine whether there is release end information generated for the end of the call, and locate the system to be released in the release process according to the generation of the release start information and release end information. The node on which the publishing error occurred. By adopting the present invention, the unique id of this release is generated before the release, and then the release system calls each sub-module or associated system, and the data is reported twice before the call and before the result is returned, and the error node is processed according to the data report. Locate, you can quickly locate the faulty node without traversing all the query logs when the system is released.

Description

Method and device for locating error node in publishing system

technical field

The invention relates to the field of Internet technologies, and in particular, to a method and device for locating an error node in a publishing system.

Background technique

The publishing system is a system used by the company to push the code and resources written by the developers to the live network server to provide services. Since the publishing system involves multiple system docking, multiple sub-module processing, and cross-domain and cross-machine room network transmission, when publishing errors occur in the publishing system, it is necessary to query the log files layer by layer and locate the problem step by step, which is extremely time-consuming and labor-intensive. This affects the timeliness of system release.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method and device for locating an error node in a publishing system. Before publishing, a unique id for the current publishing is generated. After that, the publishing system calls each sub-module or associated system. Two steps are performed before calling and before returning the result. Secondary data reporting, the faulty node is located according to the data reporting situation, and the faulty node can be quickly located without traversing all the query logs when the system is released.

A first aspect of the embodiments of the present invention provides a method for locating an error node in a publishing system, which may include:

Generate a unique release id corresponding to the relevant data of the system to be released;

When retrieving the first release project indicated by the system to be released, the release start information is output, and the release start information includes the unique release id, the project id of the first release project, and the initial invocation state information;

When the first release project is called and ended, it is judged whether there is release end information generated for the end of the call, and the release end information includes the unique release id and the project id and the calling result of calling the first release project;

According to the generation of the release start information and the release end information, locate the node where the release error occurred in the release process of the system to be released.

Further, the above method also includes:

When a release operation for the system to be released is detected, relevant data of the system to be released is obtained, and the relevant data at least includes the project id of the released project in the release system, the id of the publisher, and the release version number.

Further, according to the generation of the release start information and the release end information, locate the node of the release error that occurs in the release process of the system to be released, including:

When the first release project is called and finished, the release end information generated for the end of the call is not detected, and it is determined that the node that publishes the error is located in the call of the first release project;

When the release end information is detected, but the release start information for the second release project is not detected, it is determined that the node that releases the error is located in the invocation of the second release project.

Further, the above method also includes:

According to the system log of the system to be released and the second release project, determine the target node where the network problem occurs, and the target node is the node end where the system to be released and/or the node end where the second release project is located.

Further, the above method also includes:

When it is determined that the system to be released has an error node in the process of calling the release project, search for the corresponding unique release id according to the project id;

According to the unique publishing id, confirm the link that publishes the error, and trace the node that publishes the error.

Further, the above-mentioned first release project and second release project both include an associated system of the release system and/or a release module inside the release system.

A second aspect of the embodiments of the present invention provides a device for locating an error node in a publishing system, which may include:

The unique id generation unit is used to generate a unique release id corresponding to the relevant data of the system to be released;

The start information reporting unit is used to output the release start information when retrieving the first release project indicated by the system to be released, and the release start information includes the unique release id, the project id of the first release project and the initial invocation state information;

The end information reporting unit is used to judge whether there is release end information generated for the end of the call when the first release project is called and ended, and the release end information includes the unique release id and the project id and the calling result of calling the first release project;

The error node locating unit is used for locating the node of the publishing error that occurs in the publishing process of the system to be published according to the generation of the publishing start information and the publishing end information.

Further, the above-mentioned device also includes:

The relevant data acquisition unit is used to acquire relevant data of the system to be released when a release operation for the system to be released is detected, and the relevant data at least includes the project id, publisher id and release version number of the released project in the release system.

Further, the above-mentioned error node location unit includes:

The first node locating subunit is used for, after the first publishing project is called and finished, the publishing end information generated for the end of the calling is not detected, and it is determined that the node with the publishing error is located in the calling of the first publishing project;

The second node locating subunit is configured to determine that the node that publishes the error is located in the calling of the second publishing project when the publishing end information is detected but the publishing start information for the second publishing project is not detected.

Further, the above-mentioned second node locating subunit is specifically used to determine the target node with a problem in the network according to the system log of the system to be released and the second release project, and the target node is the node where the system to be released is located and/or the second node. Publish the node where the project is located.

Further, the above-mentioned device also includes:

The id search unit is used to find the corresponding unique release id according to the project id when it is determined that the system to be released has an error node in the process of calling the release project;

The node source tracing unit is used to confirm the link that publishes the error according to the unique publishing id, and trace the node that publishes the error.

Further, the above-mentioned first release project and second release project both include an associated system of the release system and/or a release module inside the release system.

In the embodiment of the present invention, the unique id of this release is generated before the system release, and then the release system calls each sub-module or associated system, and the data is reported twice before the call and before the result is returned. According to the situation of the data report The faulty node is located. When the faulty node occurs, there is no need to traverse all the query logs when the system is released, which achieves the purpose of quickly locating the faulty node and improves the timeliness of the system's release.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that are required in the description of the embodiments or the prior art.

1 is a schematic flowchart of a method for locating an error node in a publishing system according to an embodiment of the present invention;

2 is a schematic flowchart of a system release provided by an embodiment of the present invention;

3 is a schematic structural diagram of a device for locating an error node in a publishing system according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an error node location unit provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

The method for locating an error node in a publishing system provided by the embodiment of the present invention can be applied to an application scenario of quickly locating a node with a publishing error during system publishing.

It should be noted that the terms "first", "second", etc. in the description and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances for the embodiments of the application described herein.

A method for locating an error node in a publishing system provided by an embodiment of the present invention will be described in detail below with reference to FIG. 1 .

Please refer to FIG. 1 , which is a schematic flowchart of a method for locating an error node in a publishing system according to an embodiment of the present invention. As shown in FIG. 1 , the method in this embodiment of the present invention may include the following steps S101 to S104.

S101 , according to the relevant data of the system to be released, a unique release id corresponding to the system is generated.

It can be understood that after the release approval of a system to be released is approved, the user can click the release button of the corresponding project of the system to start the system release, and when the above device detects the release operation for the system to be released, it can obtain the system to be released. Relevant data, the data may at least include the project id, publisher id and release version number of the project to be released in the system to be released, and the above-mentioned project to be released may be a release module within the system to be released or an associated system of the system to be released.

Further, the above-mentioned device can generate a unique release id corresponding to the above-mentioned relevant data, and this id can be bound with the current release, so that the node can be traced through the id later.

S102, when retrieving the first release project indicated by the system to be released, output release start information.

Specifically, when retrieving the first release project indicated by the system to be released, the above-mentioned device may generate and output start release information, and the information may include the above-mentioned unique release id, the project id of the first release project, and the initial release of the first release project. Call status information.

S103 , when the first release project is called to end, determine whether there is release end information generated for the end of the call.

Specifically, when the first release project is called and finished, the above-mentioned apparatus may generate release end information. If an error occurs in the system call, the release end information will fail to be generated. Therefore, the above-mentioned apparatus may, when the first release project is called, It is detected whether the above-mentioned release end information is generated, so as to locate the error node occurring in the system release according to the information subsequently.

S104, according to the generation of the release start information and the release end information, locate the node where the release error occurs in the release process of the system to be released.

Specifically, the above-mentioned device can locate the node where the publishing error occurs in the publishing process of the system to be published according to the generation of the publishing start information and the publishing end information. For example, when the first publishing project is called and finished, the above publishing is not detected. end information, it can be determined that the node that publishes the error is located in the call of the first publishing project; when the publishing end information is detected, but the publishing start information for the second publishing project is not detected, it can be determined that the node that publishes the error is located in the second publishing project. In the call to publish the project. It can be understood that the above-mentioned second release project may be a release project that is sequentially invoked after the first release project is successfully released.

It should be noted that, after the above-mentioned device determines that the node that publishes the error is located in the call of the second publishing project, it can determine the target node with a problem in the network according to the system log of the system to be published and the second publishing project, and the target node can be The node end where the system to be published is located or the node end where the second publishing project is located, or both node ends are target nodes.

It can be understood that, both the above-mentioned first release project and the second release project may include an associated system of the release system and/or a release module inside the release system. For example, in a certain release, in the associated system A, only the data that starts to call the system is reported once, and there is no data to report the processing result of the system for the second time, then it can be confirmed that the error occurred in the invocation of the associated system A. If the initial and end data of the associated system A are reported twice after the associated system A is processed, but are not transferred to the associated system B in the next step, it can be confirmed that the network between the publishing system and the associated system B has been disconnected. Then, according to the logs of the publishing system and the associated system B, it can be determined that there is a problem with the publishing system (local) or the associated system B (peer) network. For the problems that occur in each sub-module within the publishing system, it is similar to the related system troubleshooting. If the same publishing module has only one data report in the current publishing, there is an error in calling the publishing module; if the same publishing module has data in the current publishing If the data is reported twice, but the next publishing module does not report, it is necessary to check the logic of the call between the two publishing modules. There may be an error in the call returning or the program is abnormal. In this case, only the errors in the publishing system log need to be queried. information to locate the problem.

It can be understood that, when it is determined that the system to be released has an error node in the process of invoking the release project, the above-mentioned device can search for the corresponding unique release id according to the above project id, and then confirm the link with the release error according to the unique release id, and trace the release to the source. Bad target node.

In the embodiment of the present invention, the unique id of this release is generated before the system release, and then the release system calls each sub-module or associated system, and the data is reported twice before the call and before the result is returned. According to the situation of the data report The faulty node is located. When the faulty node occurs, there is no need to traverse all the query logs when the system is released, which achieves the purpose of quickly locating the faulty node and improves the timeliness of the system's release.

In a specific implementation manner of the embodiment of the present invention, the publishing process of the system may be as shown in FIG. 2, which mainly includes: S201, the publishing system preparation process; S202, the publishing system docking code push; S203, generating a unique publishing id, storing The result of two calls for each associated system or internal module.

S201, the release system preparation process may include three modules: connecting to a code server to obtain newly added codes. Modify code packaging. Write the publisher ip and corresponding path. It can be understood that the above-mentioned code server may be a server of an external system, and the above-mentioned newly added code may be newly added code that needs to be released.

S202, the release system docking code push may include four modules: connect to the corresponding server according to the ip, and upload the code to the specified ip device through the code push system. Execute the pre-script to suspend existing services. Post updated code. Execute the post script and restart the publish. It can be understood that when the above-mentioned corresponding server, that is, the designated ip device, needs to suspend other existing services to receive the above-mentioned system data when it receives the released system data, after successful reception, the device can be restarted and the system can be executed on the device side. release.

S203, a unique release id is generated, and the result of two calls of each associated system or internal module is stored. It is understandable that the generation of the unique release id is performed after the approval and before the system release preparation process, and the two invocation results of each associated system or internal module are stored in each system release preparation process, and each release system. It needs to be executed during the process of docking code push.

It should be noted that the purpose of storing two invocation results of each associated system or internal module is to locate the faulty node when the system issues an error according to the invocation results. Specifically, for the method for locating the faulty node, reference may be made to the specific descriptions in the foregoing method embodiments, and details are not described herein again.

It should be noted that the steps shown in the flowcharts of the accompanying drawings may be executed in a computer system, such as a set of computer-executable instructions, and, although a logical sequence is shown in the flowcharts, in some cases, Steps shown or described may be performed in an order different from that herein.

The following will describe in detail the device for locating an error node in a publishing system provided by an embodiment of the present invention with reference to FIG. 3 and FIG. 4 . It should be noted that the device for locating an error node in the publishing system shown in FIG. 3 and FIG. 4 is used to execute the method of the embodiment shown in FIG. 1 and FIG. 2 of the present invention. For the part related to the embodiment, the specific technical details are not disclosed, please refer to the embodiment shown in FIG. 1 and FIG. 2 of the present invention.

Please refer to FIG. 3 , which is a schematic structural diagram of an apparatus for locating an error node in a publishing system according to an embodiment of the present invention. As shown in FIG. 3 , the device 10 for locating an error node according to the embodiment of the present invention may include: a unique id generating unit 101, a start information reporting unit 102, an end information reporting unit 103, an error node locating unit 104, a related data obtaining unit 105, id search unit 106 and node traceability unit 107 . The faulty node location unit 104, as shown in FIG. 4, includes a first node location subunit 1041 and a second node location subunit 1042.

The unique id generating unit 101 is configured to generate a unique publishing id corresponding to the relevant data of the system to be published.

It can be understood that, after the release approval of a system to be released is approved, the user can click the release button of the corresponding project of the system to start the system release. Relevant data of the publishing system, the data may at least include the project id, publisher id, and publishing version number of the publishing project in the system to be published. The publishing project may be a publishing module within the system to be published or an associated system of the system to be published.

Further, the unique id generating unit 101 can generate a unique release id corresponding to the above-mentioned relevant data, and this id can be bound with the current release, so that the node can be traced through the id later.

The start information reporting unit 102 is configured to output the release start information when retrieving the first release project indicated by the system to be released.

In a specific implementation, when retrieving the first release project indicated by the system to be released, the start information reporting unit 102 may generate and output start release information, and the information may include the above-mentioned unique release id, the project id of the first release project, and the first release project. Publish the initial invocation status information of the project.

The end information reporting unit 103 is configured to determine whether there is release end information generated for the end of the call when the first release project is called and ended.

In a specific implementation, when the first release project is called and ended, the end information reporting unit 103 can generate release end information, and if an error occurs in the system call, the release end information will fail to be generated. Therefore, the end information reporting unit 103 can generate the release end information in the first When the invocation of a release project ends, it is detected whether the above-mentioned release end information is generated, so as to locate an error node occurring in the system release according to the information subsequently.

The error node locating unit 104 is configured to locate, according to the generation of the release start information and the release end information, a node with a release error that occurs in the release process of the system to be released.

In a specific implementation, the error node locating unit 104 can locate the node with the publishing error that occurs in the publishing process of the system to be published according to the generation of the publishing start information and the publishing end information. For example, when the first publishing project is called and finished, no Detecting the above-mentioned release end information, the first node positioning subunit 1041 can determine that the node with the error release is located in the call of the first release project; when the release end information is detected, but the release start information for the second release project is not detected , the second node locating subunit 1042 may determine that the node that publishes the error is located in the calling of the second publishing project. It can be understood that the above-mentioned second release project may be a release project that is sequentially invoked after the first release project is successfully released.

It should be noted that, after the above device determines that the node that publishes the error is located in the call of the second publishing project, the second node positioning sub-unit 1042 can determine the target of the network problem according to the system log of the system to be published and the second publishing project. node, the target node may be the node end where the system to be published is located or the node end where the second publishing project is located, or both node ends are target nodes.

It can be understood that, both the above-mentioned first release project and the second release project may include an associated system of the release system and/or a release module inside the release system. For example, in a certain release, in the associated system A, only the data that starts to call the system is reported once, and there is no data to report the processing result of the system for the second time, then it can be confirmed that the error occurred in the invocation of the associated system A. If the initial and end data of the associated system A are reported twice after the associated system A is processed, but are not transferred to the associated system B in the next step, it can be confirmed that the network between the publishing system and the associated system B has been disconnected. Then, according to the logs of the publishing system and the associated system B, it can be determined that there is a problem with the publishing system (local) or the associated system B (peer) network. For the problems that occur in each sub-module within the publishing system, it is similar to the related system troubleshooting. If the same publishing module has only one data report in the current publishing, there is an error in calling the publishing module; if the same publishing module has data in the current publishing If the data is reported twice, but the next publishing module does not report, it is necessary to check the logic of the call between the two publishing modules. There may be an error in the call returning or the program is abnormal. In this case, only the errors in the publishing system log need to be queried. information to locate the problem.

It can be understood that when it is determined that the system to be released has an error node in the process of calling the release project, the id search unit 106 can search for the corresponding unique release id according to the above-mentioned project id, and the node traceability unit 107 confirms the release error according to the unique release id. link, and trace the target node that publishes the error.

In the embodiment of the present invention, the unique id of this release is generated before the system release, and then the release system calls each sub-module or associated system, and the data is reported twice before the call and before the result is returned. According to the situation of the data report The faulty node is located. When the faulty node occurs, there is no need to traverse all the query logs when the system is released, which achieves the purpose of quickly locating the faulty node and improves the timeliness of the system's release.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and the program is During execution, it may include the processes of the embodiments of the above-mentioned methods. The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like.

The above disclosures are only preferred embodiments of the present invention, and of course, the scope of the rights of the present invention cannot be limited by this. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims (2)

1. a kind of positioning method of publishing system error node, is characterized in that, comprises: Generate a unique release id corresponding to the relevant data of the system to be released, When retrieving the first release project indicated by the system to be released, output release start information, where the release start information includes the unique release id, the project id of the first release project, and initial invocation state information, When the first release project is called and ended, it is judged whether there is release end information generated for the end of the call, where the release end information includes the unique release id and the project id and calls the first release project the result of the call, According to the generation of the release start information and the release end information, locate the node where the release error occurred in the release process of the system to be released, When a publishing operation for the system to be published is detected, relevant data of the system to be published is obtained, where the relevant data at least includes the project id, publisher id and published version number of the published project in the publishing system; According to the generation of the release start information and the release end information, locating the node where the release error occurs during the release process of the system to be released includes: After the first publishing project is called and finished, the publishing end information generated for the end of the calling is not detected, and it is determined that the node with the publishing error is located in the calling of the first publishing project, When the release end information is detected, but the release start information for the second release project is not detected, it is determined that the node where the release error is located is in the call of the second release project, and the second release project is in the first release process. The release project that is called sequentially after the release project is successfully released; After it is determined that the node that publishes the error is in the call of the second publishing project, according to the system log of the system to be published and the system log of the second publishing project, determine the target node with a problem in the network, and the target node is the to-be-published project The node where the system is located and/or the node where the second release project is located; Both the first release project and the second release project include an associated system of the release system and/or a release module inside the release system. 2. A positioning device for publishing system error nodes, characterized in that, comprising: The unique id generation unit is used to generate the corresponding unique release id according to the relevant data of the system to be released, A start information reporting unit, configured to output release start information when retrieving the first release project indicated by the system to be released, the release start information including the unique release id and the project id of the first release project and initial call status information, An end information reporting unit, configured to determine whether there is release end information generated for the end of the call when the first release project is called and ended, the release end information including the unique release id and the project id and invoking the invocation result of the first release project, an error node locating unit, configured to locate a node with a publishing error that occurs during the publishing process of the system to be published according to the generation of the publishing start information and the publishing end information, The relevant data acquisition unit is used to acquire relevant data of the system to be released when a release operation for the system to be released is detected, and the relevant data at least includes the project id, the publisher id and the release version of the released project in the release system No; The error node location unit includes: The first node positioning subunit is used for, after the first release project is called and finished, the release end information generated for the end of the invocation is not detected, and it is determined that the node with the release error is located in the invocation of the first release project , The second node positioning subunit is configured to determine that the node that publishes the error is located in the invocation of the second publishing project when the publishing end information is detected, but the publishing start information for the second publishing project is not detected. The second release project is a release project that is sequentially invoked after the first release project is successfully released; The second node locating subunit is specifically configured to, after it is determined that the node that publishes the error is located in the call of the second publishing project, according to the system log of the system to be published and the second publishing project, determine the problem with the network. A target node, where the target node is the node end where the system to be released is located and/or the node end where the second release project is located; Both the first release project and the second release project include an associated system of the release system and/or a release module inside the release system.

Images