CN109218041B - Request processing method and device for server system - Google Patents
Request processing method and device for server system Download PDFInfo
- Publication number
- CN109218041B CN109218041B CN201710512695.5A CN201710512695A CN109218041B CN 109218041 B CN109218041 B CN 109218041B CN 201710512695 A CN201710512695 A CN 201710512695A CN 109218041 B CN109218041 B CN 109218041B
- Authority
- CN
- China
- Prior art keywords
- request
- processing
- server
- processing server
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
Abstract
The application discloses a request processing method and device for a server system. One embodiment of the method comprises: receiving a debugging request sent by a processing server, wherein the debugging request is sent to the debugging server by the processing server when a response message is not received, and the debugging request comprises an identifier of a request sent between the processing servers; determining the identifier of the request sent between each processing server according to the debugging request; acquiring request processing logs of each processing server; and determining the identifier of the processing server which does not return the response message according to each request processing log and the identifier. The implementation method can quickly locate and call the identifier of the abnormal processing server in the joint debugging test process, thereby reducing the time of the joint debugging test and improving the efficiency of the joint debugging test.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to the field of internet technologies, and in particular, to a request processing method and apparatus for a server system.
Background
With the development of terminal technology and internet technology, more and more functions of application programs installed on the terminal are provided, and the functions are realized by the coordination of each service module. Each service module may be supported by means of multiple servers. Under the trend of micro-service of the application program, the number of service modules of the application program is increased, and the coupling degree between the service modules is decreased. When joint debugging test of each service module is carried out, mutual calling among a plurality of servers is needed to realize the test.
Under the condition, the problem of how to locate the abnormal call in the joint debugging test process has important significance for improving the efficiency of the joint debugging test.
Disclosure of Invention
The present application aims to provide a request processing method and apparatus for a server system to solve the technical problems mentioned in the above background section.
In a first aspect, an embodiment of the present application provides a request processing method for a server system, where the server system includes a debugging server and multiple processing servers, each processing server sends a request to itself or another processing server according to a preset call relationship, and receives a response message, each processing server interacts with a terminal, and identifiers of the requests sent by the processing servers are the same in an interaction process, and the method includes: receiving a debugging request sent by a processing server, wherein the debugging request is sent to the debugging server by the processing server when a response message is not received, and the debugging request comprises an identifier of a request sent between the processing servers; determining the identifier of the request sent between each processing server according to the debugging request; acquiring request processing logs of each processing server; and determining the identifier of the processing server which does not return the response message according to each request processing log and the identifier.
In some embodiments, the request sent between the processing servers includes an identification of the processing server receiving the request; and the determining, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message includes: determining a first request sent between each processing server according to each request processing log; based on the first request, executing the following determining steps: analyzing the first request, and determining the identifier of a first processing server receiving the first request; determining whether the first processing server sends a second request according to the request processing log of the first processing server; responding to the first processing server to send the second request, and determining whether the first processing server receives a response message; in response to the first processing server not receiving the response message, determining an identifier of the processing server receiving the second request; and responding to the response message received by the first processing server, determining that the second request is the first request, and continuing to execute the determining step.
In some embodiments, the determining, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message further includes: and determining the identification of the first processing server in response to the first processing server not sending the second request.
In some embodiments, the obtaining the request processing log of each processing server includes: and acquiring request processing logs of each processing server at preset intervals.
In some embodiments, determining, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message, further includes: and fusing the request processing logs.
In a second aspect, an embodiment of the present application provides a request processing apparatus for a server system, where the server system includes a debugging server and a plurality of processing servers, each processing server sends a request to itself or another processing server according to a preset call relationship, and receives a response message, each processing server interacts with a terminal, and identifiers of the requests sent between the processing servers are the same in an interaction process, and the apparatus includes: a request receiving unit, configured to receive a debug request sent by a processing server, where the debug request is sent to the debug server by the processing server when a response message is not received, and the debug request includes an identifier of a request sent between the processing servers; a request identifier determining unit, configured to determine, according to the debug request, an identifier of a request sent between the processing servers; a log obtaining unit configured to obtain a request processing log of each processing server; and a server identifier determining unit, configured to determine, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message.
In some embodiments, the request sent between the processing servers includes an identification of the processing server receiving the request; and the server identification determination unit includes: a first request determining module, configured to determine, according to each request processing log, a first request sent between each processing server; a first identifier determining module, configured to perform the following determining steps based on the first request: analyzing the first request, and determining the identifier of a first processing server receiving the first request; determining whether the first processing server sends a second request according to the request processing log of the first processing server; responding to the first processing server to send the second request, and determining whether the first processing server receives a response message; in response to the first processing server not receiving the response message, determining an identifier of the processing server receiving the second request; and the feedback module is used for responding to the response message received by the first processing server, determining that the second request is the first request and feeding back the first request to the first identifier determining module.
In some embodiments, the server identifier determining unit further includes: a second identifier determining module, configured to determine an identifier of the first processing server in response to the first processing server not sending the second request.
In some embodiments, the log obtaining unit is further configured to: and acquiring request processing logs of each processing server at preset intervals.
In some embodiments, the server identification determination unit is further configured to: and fusing the request processing logs.
In a third aspect, an embodiment of the present application provides a server, including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the method described in any of the above embodiments.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method described in any of the above embodiments.
The request processing method and device for the server system provided by the above embodiments of the present application are applicable to a system including a debugging server and a plurality of processing servers, where each processing server may send a request to itself or another processing server according to a preset call relationship, and receive a response message. Meanwhile, each processing server can interact with the terminal so as to receive the request sent by the terminal and return a response message to the terminal after processing the request. In the interaction process, the identifiers of the requests sent by the processing servers are the same. In this embodiment, when each processing server does not receive the response message, a debugging request is sent to the debugging server, where the debugging request includes an identifier of a request sent between the processing servers, and after the identifier of the request is determined, the debugging server obtains a request processing log generated by each processing server in the process of processing the request, and finally determines an identifier of a processing server that does not return the response message according to each request processing log and the identifier of the request.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram for one embodiment of a request processing method for a server system according to the present application;
FIG. 3 is a schematic diagram of an application scenario of a request processing method for a server system according to the present application;
FIG. 4 is a flow diagram for one embodiment of determining the identity of a processing server that does not return a reply message in a request processing method for a server system according to the application;
FIG. 5 is a schematic block diagram illustrating one embodiment of a request processing device for a server system according to the present application;
FIG. 6 is a schematic block diagram of a computer system suitable for implementing a debug server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 shows an exemplary system architecture 100 to which embodiments of the request processing method for a server system or the request processing apparatus for a server system of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include a debug server 101, processing servers 102, 103, 104, a network 105, and terminal devices 106, 107, 108. The network 105 is used to provide a medium for communication links between the processing servers 102, 103, 104 and the terminal devices 106, 107, 108. Network 105 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The debugging server 101 may be a server interacting with each processing server 102, 103, 104, and may locate an abnormal problem that occurs during the calling process of each processing server, such as a network problem, a request that cannot be sent between each processing server, and the like.
The processing servers 102, 103, 104 may be servers that process requests, and may process requests sent by the terminal devices 106, 107, 108, and requests sent by the processing servers, and return response messages after processing each request. In the process of receiving a request sent by a terminal and returning a response message to the terminal, the identifier of the request sent between each processing server is fixed and unique. The identifier may be generated by the processing server that receives the request sent by the terminal and added to the request sent to the other processing server.
The user may use the terminal devices 106, 107, 108 to interact with the processing servers 102, 103, 104 via the network 105 to receive or send messages or the like. The terminal devices 106, 107, 108 may have installed thereon various communication client applications, such as a web browser application, a shopping-like application, a search-like application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
It should be noted that the request processing method for the server system provided by the embodiment of the present application is generally executed by the debugging server 101, and accordingly, the request processing apparatus for the server system is generally disposed in the debugging server 101.
It should be understood that the number of debug servers, processing servers, networks, and terminal devices in fig. 1 are merely illustrative. There may be any number of servers, processing servers, networks, and terminal devices, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a request processing method for a server system according to the present application is shown. In this embodiment, the server system includes a debugging server and a plurality of processing servers, each processing server sends a request to itself or another processing server according to a preset call relationship and receives a response message, each processing server interacts with a terminal, and identifiers of the requests sent by the processing servers are the same in an interaction process.
The request processing method for the server system of the embodiment comprises the following steps:
In this embodiment, the electronic device (for example, the debugging server shown in fig. 1) on which the request processing method for the server system operates may receive the debugging request from the processing server through a wired connection manner or a wireless connection manner. The debugging request is sent to the debugging server by the processing server when the processing server does not receive the response message, namely the debugging request is sent to the debugging server when the debugging result is uncertain. The debugging request comprises the identification of the request sent between each processing server. The identifier may be generated between the processing servers according to a pre-agreed identifier generation rule, and may be a character string. In the process of one interaction with the terminal, the identifier is carried when the request is sent between each processing server.
It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.
Because the debugging request comprises the identifier of the request sent between the processing servers, the debugging server can determine the identifier of the request sent between the processing servers by analyzing the debugging request after receiving the debugging request.
The debugging server can also obtain a request processing log of each processing server, wherein the request processing log can be a record file generated by each processing server in the process of processing a request sent by a terminal or the processing server. The request processing log may be a log file or a data table including information related to the request, such as an identifier of a device that transmits the request, a name of the request, and a transmission time of the request, or may be a file that records interface parameters when the processing servers are called.
In some optional implementations of this embodiment, the debugging server may obtain the request processing logs of the processing servers at intervals of a preset time. Therefore, after the debugging request sent by the processing server is received, the analysis can be quickly and effectively carried out based on the debugging request, and the identification of the server with the abnormal condition can be determined.
The debugging server acquires each request processing log, and determines the identifier of the request sent between each processing server, so as to determine the identifier of the processing server which does not return the response message. Specifically, the debugging server may query, according to the identifier, the identifier of the processing server that sent the request in each request processing log, and then sequentially analyze whether each processing server receives the response message.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the request processing method for the server system according to the present embodiment. In the application scenario of fig. 3, a user browses a web page 311 using a terminal 31, after clicking "mobile phone field" in the web page 311, the terminal 31 sends a page browsing request to a processing server 32, after receiving the request sent by the terminal 31, the processing server 32 sends a mobile phone promotion page request to a processing server 33 for supporting "mobile phone field promotion", but the processing server 32 does not receive a response message returned by the processing server 33, the processing server 32 sends a debugging request to a debugging server 34, and the debugging server finally determines that the processing server 33 does not return a response message. The processing server 32 also returns a response message of request failure to the terminal 31, and the terminal 31 displays the buffering interface 312.
In the request processing method for the server system provided by the above embodiment of the application, when each processing server does not receive the response message, the debugging request is sent to the debugging server, where the debugging request includes an identifier of the request sent between the processing servers, and after the identifier of the request is determined, the debugging server obtains the request processing log generated by each processing server in the process of processing the request, and finally determines the identifier of the processing server that does not return the response message according to each request processing log and the identifier of the request, so that the identifier of the processing server that is abnormal in call can be quickly located in the joint debugging test process, the time of the joint debugging test is reduced, and the efficiency of the joint debugging test is improved.
With continued reference to fig. 4, a flow 400 for determining the identity of a processing server that does not return a reply message in a request processing method for a server system according to the present application is shown. In this embodiment, the request sent between the processing servers may further include an identifier of the processing server that receives the request. As shown in fig. 4, in this embodiment, the identifier of the processing server that does not return the response message may be determined by the following steps:
In this embodiment, the first request is any one of a plurality of requests sent between the processing servers in the process of receiving a request sent by the terminal and returning the request to the terminal response message.
Since the first request includes the identifier of the processing server that received the first request, the debug server may parse the first request to determine the identifier of the first processing server.
After determining the identity of the first processing server, the debug server may then process the log according to the request of the first processing server to determine whether the first processing server issued the second request. It can be understood that, in this embodiment, the second request is a request sent by the first processing server to itself or another processing server according to a preset call relationship after receiving the first request.
And after detecting that the first processing server sends out the second request, detecting whether the first processing server receives the response message. It is to be appreciated that the debug server can determine whether the first processing server receives the response message based on the request processing log of the first server.
After determining that the first processing server does not receive the response message, it may be determined that the processing server receiving the second request does not return the response message to the first processing server, and thus, the identity of the processing server receiving the second request may be determined. The identity of the processing server receiving the second request may be determined by the second request.
After determining that the first processing server receives the response message, it may be determined that the interaction between the first processing server and the processing server receiving the second request is normal, and no abnormal condition occurs. Therefore, the steps 4021 to 4024 can be continuously executed with the second request as the first request.
In some optional implementations of this embodiment, the method may further include the following steps not shown in fig. 4:
in response to the first processing server not issuing the second request, an identification of the first processing server is determined.
If the first processing server is sending the second request, the network of the first processing server is considered to be abnormal, the first processing server does not return a response message, and the identifier of the first processing server is determined.
In some optional implementation manners of this embodiment, the debugging server may further obtain, through an interface with each processing server, an identifier of the processing server that receives the request, and may also obtain, by reading the database, the identifier of the processing server that receives the request.
In some optional implementation manners of this embodiment, after the debugging server obtains the request processing logs of each processing server, the debugging server may merge the request processing logs to facilitate rapid and effective analysis. In particular, the debug server may implement the collection and fusion through some open-source log collection applications. When the debugging server acquires the identifier of the processing server in an interface mode, the collection and fusion can be realized in a Socket/HTTP mode; when the debugging server obtains the identifier of the processing server by reading the database, the collection and fusion can be realized by adopting a database table synchronization mode.
The request processing method for the server system provided by the embodiment of the application can quickly locate the problem and reduce the times of repeated joint debugging tests; meanwhile, maintenance personnel of a plurality of servers are not needed to participate in the process, and human resources are saved.
With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a request processing method apparatus for a server system, where the apparatus embodiment corresponds to the method embodiment shown in fig. 2, and the apparatus may be applied to various electronic devices in particular.
As shown in fig. 5, a request processing method apparatus 500 for a server system of the present embodiment includes: a request receiving unit 501, a request identification determining unit 502, a log obtaining unit 503, and a server identification determining unit 504.
The request receiving unit 501 is configured to receive a debugging request sent by a processing server.
The debugging request is sent to the debugging server by the processing server when the processing server does not receive the response message, and the debugging request comprises the identifier of the request sent between the processing servers.
A request identifier determining unit 502, configured to determine, according to the debug request, an identifier of a request sent between the processing servers.
A log obtaining unit 503, configured to obtain a request processing log of each processing server.
A server identifier determining unit 504, configured to determine, according to each request processing log and identifier, an identifier of a processing server that does not return a response message.
In some optional implementations of this embodiment, the request sent between the processing servers includes an identification of the processing server that received the request. The above-mentioned server identification determination unit 504 may include a first request determination module, a first identification determination module, and a feedback module, which are not shown in fig. 5.
The first request determining module is used for determining a first request sent between the processing servers according to the request processing logs.
A first identity determination module for performing the following determination steps based on the first request: analyzing the first request, and determining the identifier of a first processing server receiving the first request; determining whether the first processing server sends a second request according to the request processing log of the first processing server; responding to the first processing server to send out a second request, and determining whether the first processing server receives a response message; in response to the first processing server not receiving the response message, an identification of the processing server receiving the second request is determined.
And the feedback module is used for responding to the response message received by the first processing server, determining that the second request is the first request and feeding back the first request to the first identifier determining module.
In some optional implementation manners of this embodiment, the server identifier determining unit 504 may include a second identifier determining module, not shown in fig. 5, configured to determine the identifier of the first processing server in response to that the first processing server does not issue the second request.
In some optional implementations of this embodiment, the log obtaining unit 503 may be further configured to: and acquiring request processing logs of each processing server at preset intervals.
In some optional implementations of this embodiment, the server identifier determining unit 504 may be further configured to: and fusing the request processing logs.
The request processing apparatus for a server system according to the foregoing embodiment of the present application, when each processing server does not receive a response message, sends a debug request to the debug server, where the debug request includes an identifier of a request sent between the processing servers, and after determining the identifier of the request, the debug server obtains a request processing log generated by each processing server in a process of processing the request, and finally determines an identifier of a processing server that does not return a response message according to each request processing log and the identifier of the request, so that an identifier of an abnormal processing server that is called in a fast positioning manner in an associated debugging test process can be determined, time of the associated debugging test is reduced, and efficiency of the associated debugging test is improved.
It should be understood that the units 501 to 504 recited in the request processing apparatus 500 for the server system correspond to the respective steps in the method described with reference to fig. 2, respectively. Thus, the operations and features described above for the request processing method for the server system are also applicable to the apparatus 500 and the units included therein, and are not described again here. The corresponding elements of the apparatus 500 may cooperate with elements in a server to implement aspects of embodiments of the present application.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a server according to embodiments of the present application. The server shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a machine-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the method of the present application when executed by a Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a request receiving unit, a request identification determining unit, a log obtaining unit, and a server identification determining unit. Here, the names of these units do not constitute a limitation to the unit itself in some cases, and for example, the request receiving unit may also be described as a "unit that receives a debugging request sent by the processing server".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving a debugging request sent by a processing server, wherein the debugging request is sent to the debugging server by the processing server when a response message is not received, and the debugging request comprises an identifier of a request sent between the processing servers; determining the identifier of the request sent between each processing server according to the debugging request; acquiring request processing logs of each processing server; and determining the identifier of the processing server which does not return the response message according to each request processing log and the identifier.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (12)
1. A request processing method for a server system is characterized in that the server system comprises a debugging server and a plurality of processing servers, each processing server sends a request to itself or other processing servers according to a preset calling relationship and receives a response message, each processing server interacts with a terminal, and in the interaction process, the identifiers of the requests sent by the processing servers are the same, the method comprises the following steps:
receiving a debugging request sent by a processing server, wherein the debugging request is sent to the debugging server by the processing server when a response message is not received, and the debugging request comprises an identifier of a request sent between each processing server;
determining the identifier of the request sent between each processing server according to the debugging request;
acquiring request processing logs of each processing server;
determining the identifier of the processing server which does not return the response message according to each request processing log and the identifier;
the determining, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message includes:
and inquiring the identification of the processing server sending the request of the identification in each request processing log according to the identification, and sequentially analyzing whether each processing server receives a response message.
2. The method of claim 1, wherein the request sent between the processing servers includes an identification of the processing server receiving the request; and
the determining, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message includes:
determining a first request sent between each processing server according to each request processing log;
based on the first request, performing the following determining steps: analyzing the first request, and determining the identifier of a first processing server receiving the first request; determining whether the first processing server sends a second request according to the request processing log of the first processing server; in response to the first processing server issuing the second request, determining whether the first processing server receives a response message; in response to the first processing server not receiving a response message, determining an identity of a processing server receiving the second request;
and responding to the first processing server receiving the response message, determining that the second request is the first request, and continuing to execute the determining step.
3. The method of claim 2, wherein determining an identity of a processing server that did not return the response message based on each of the request processing logs and the identity, further comprises:
in response to the first processing server not issuing the second request, determining an identity of the first processing server.
4. The method according to any one of claims 1 to 3, wherein the obtaining of the request processing log of each processing server comprises:
and acquiring request processing logs of each processing server at preset intervals.
5. The method of claim 4, wherein determining an identity of a processing server that did not return the response message based on each of the request processing logs and the identity, further comprises:
and fusing the request processing logs.
6. A request processing apparatus for a server system, wherein the server system includes a debugging server and a plurality of processing servers, each processing server sends a request to itself or another processing server according to a preset call relationship and receives a response message, each processing server interacts with a terminal, and during the interaction, identifiers of the requests sent between the processing servers are the same, the apparatus comprising:
a request receiving unit, configured to receive a debug request sent by a processing server, where the debug request is sent to the debug server by the processing server when a response message is not received, and the debug request includes an identifier of a request sent between the processing servers;
a request identifier determining unit, configured to determine, according to the debug request, identifiers of requests sent between the processing servers;
a log obtaining unit configured to obtain a request processing log of each processing server;
a server identifier determining unit, configured to determine, according to each request processing log and the identifier, an identifier of a processing server that does not return the response message;
the server identification determination unit is further configured to:
and inquiring the identification of the processing server sending the request of the identification in each request processing log according to the identification, and sequentially analyzing whether each processing server receives a response message.
7. The apparatus of claim 6, wherein the request sent between the processing servers includes an identification of the processing server receiving the request; and
the server identification determination unit includes:
the first request determining module is used for determining a first request sent between each processing server according to each request processing log;
a first identity determination module configured to perform, based on the first request, the following determination steps: analyzing the first request, and determining the identifier of a first processing server receiving the first request; determining whether the first processing server sends a second request according to the request processing log of the first processing server; in response to the first processing server issuing the second request, determining whether the first processing server receives a response message; in response to the first processing server not receiving a response message, determining an identity of a processing server receiving the second request;
and the feedback module is used for responding to the response message received by the first processing server, determining that the second request is the first request and feeding back the first request to the first identifier determining module.
8. The apparatus of claim 7, wherein the server identification determining unit further comprises:
a second identifier determining module, configured to determine an identifier of the first processing server in response to the first processing server not sending the second request.
9. The apparatus according to any one of claims 6 to 8, wherein the log obtaining unit is further configured to:
and acquiring request processing logs of each processing server at preset intervals.
10. The apparatus of claim 9, wherein the server identification determining unit is further configured to:
and fusing the request processing logs.
11. A server, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710512695.5A CN109218041B (en) | 2017-06-29 | 2017-06-29 | Request processing method and device for server system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710512695.5A CN109218041B (en) | 2017-06-29 | 2017-06-29 | Request processing method and device for server system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109218041A CN109218041A (en) | 2019-01-15 |
| CN109218041B true CN109218041B (en) | 2022-03-11 |
Family
ID=64960601
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710512695.5A Active CN109218041B (en) | 2017-06-29 | 2017-06-29 | Request processing method and device for server system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109218041B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110427324B (en) * | 2019-07-30 | 2023-09-08 | 中国工商银行股份有限公司 | Joint debugging system, joint debugging method, computer equipment and storage medium |
| CN110704390A (en) * | 2019-09-17 | 2020-01-17 | 平安科技（深圳）有限公司 | Method, device, electronic equipment and medium for obtaining server maintenance script |
| CN111274150B (en) * | 2020-02-07 | 2023-08-22 | 北京字节跳动网络技术有限公司 | Service instance access method and device and electronic equipment |
| CN111782445B (en) * | 2020-06-28 | 2023-08-15 | 百度在线网络技术（北京）有限公司 | Configuration method and device of equipment debugging environment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106100913A (en) * | 2016-08-25 | 2016-11-09 | 北京票之家科技有限公司 | Error message alignment system and method |
| CN106254145A (en) * | 2016-09-06 | 2016-12-21 | 腾讯科技（深圳）有限公司 | network request tracking processing method and device |
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104268055B (en) * | 2014-09-01 | 2017-07-14 | 腾讯科技（深圳）有限公司 | The monitoring method and device of a kind of program exception |
| CN105207806A (en) * | 2015-08-20 | 2015-12-30 | 百度在线网络技术（北京）有限公司 | Monitoring method and apparatus of distributed service |
| CN106534242B (en) * | 2015-09-14 | 2019-11-29 | 阿里巴巴集团控股有限公司 | The processing method and device requested in a kind of distributed system |
| US10120707B2 (en) * | 2015-12-08 | 2018-11-06 | Paypal, Inc. | Deployment of development environments |
| CN106330576B (en) * | 2016-11-18 | 2019-10-25 | 北京红马传媒文化发展有限公司 | The method of containerization micro services automatic telescopic and migration scheduling, system and equipment |
| CN106850782A (en) * | 2017-01-17 | 2017-06-13 | 泰康保险集团股份有限公司 | For the method and system of log processing |
-
2017
- 2017-06-29 CN CN201710512695.5A patent/CN109218041B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106100913A (en) * | 2016-08-25 | 2016-11-09 | 北京票之家科技有限公司 | Error message alignment system and method |
| CN106254145A (en) * | 2016-09-06 | 2016-12-21 | 腾讯科技（深圳）有限公司 | network request tracking processing method and device |
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109218041A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107622135B (en) | Method and apparatus for displaying information | |
| CN110708346B (en) | Information processing system and method | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| CN107644075B (en) | Method and device for collecting page information | |
| CN111786939B (en) | Method, device and system for testing management platform of Internet of things | |
| CN111125107A (en) | Data processing method, device, electronic equipment and medium | |
| CN108549586B (en) | Information processing method and device | |
| CN110619096A (en) | Method and apparatus for synchronizing data | |
| CN107347093B (en) | Configuration method and device for distributed server system | |
| CN109828830B (en) | Method and apparatus for managing containers | |
| CN111435380B (en) | Page cross-domain interaction method, system, device and storage device | |
| CN107368407B (en) | Information processing method and device | |
| CN111813685B (en) | Automatic test method and device | |
| CN109218338B (en) | Information processing system, method and device | |
| CN110866031B (en) | Database access path optimization method and device, computing equipment and medium | |
| CN110827037A (en) | Data interaction method and device based on block chain | |
| CN111953718A (en) | Page debugging method and device | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN112131095B (en) | Pressure testing method and device | |
| CN109756393B (en) | Information processing method, system, medium, and computing device | |
| CN113378346A (en) | Method and device for model simulation | |
| CN111831530A (en) | Test method and device | |
| CN112559001A (en) | Method and device for updating application | |
| CN110909269B (en) | Log reporting method and device |
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 |