CN113190364A - Remote call management method and device, computer equipment and readable storage medium - Google Patents
Remote call management method and device, computer equipment and readable storage medium Download PDFInfo
- Publication number
- CN113190364A CN113190364A CN202110484348.2A CN202110484348A CN113190364A CN 113190364 A CN113190364 A CN 113190364A CN 202110484348 A CN202110484348 A CN 202110484348A CN 113190364 A CN113190364 A CN 113190364A
- Authority
- CN
- China
- Prior art keywords
- cluster
- service
- abnormal
- task
- information
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 45
- 230000002159 abnormal effect Effects 0.000 claims abstract description 147
- 238000000034 method Methods 0.000 claims abstract description 37
- 238000004590 computer program Methods 0.000 claims description 11
- 230000005856 abnormality Effects 0.000 claims description 10
- 238000012544 monitoring process Methods 0.000 claims description 9
- 230000006854 communication Effects 0.000 claims description 6
- 238000004891 communication Methods 0.000 claims description 6
- 230000000903 blocking effect Effects 0.000 abstract description 5
- 230000008569 process Effects 0.000 description 13
- 238000012545 processing Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000007689 inspection Methods 0.000 description 3
- 230000002547 anomalous effect Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 229940004975 interceptor Drugs 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the field of cloud computing of cloud services, and discloses a remote call management method, a remote call management device, computer equipment and a readable storage medium, wherein the method comprises the following steps: acquiring a service system with at least one service cluster, and establishing connection with the service cluster; identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters; and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information. The invention also relates to a blockchain technique, where information can be stored in blockchain nodes. The method and the device avoid the problem that the task information cannot be processed to cause the thread blocking of the service system due to the fact that the task information is routed to the abnormal cluster, ensure that the task information received by the service system can obtain feedback information, and further ensure the stability of the service system.
Description
Technical Field
The invention relates to the technical field of cloud computing of cloud services, in particular to a remote call management method and device, computer equipment and a readable storage medium.
Background
There are many protocols available in the industry for rpc calls, such as http/https, dubbo, redis, file, etc., and most of the common cases are that one rpc request call normally takes rpc results if there is no exception.
However, the inventor has realized that if in a complex multi-service cluster environment, and the network and data between the service clusters are isolated from each other, once an exception occurs in a certain service cluster, the service system will still continuously route the task information to the exception cluster, which results in the problem that the task information cannot be processed to cause the thread of the service system to be blocked; meanwhile, because the task information in the abnormal cluster cannot be processed, the service system cannot completely process the received task information to obtain feedback information, and the stability of the service system is affected.
Disclosure of Invention
The invention aims to provide a remote call management method, a remote call management device, a computer device and a readable storage medium, which are used for solving the problems that task information cannot be processed due to the fact that the task information is continuously routed to an abnormal cluster and a service system cannot completely process received task information due to the fact that the task information in the abnormal cluster cannot be processed in the prior art.
In order to achieve the above object, the present invention provides a remote call management method, including:
acquiring a service system with at least one service cluster, and establishing connection with the service cluster;
constructing an enhancement module in a task server of the service cluster, wherein the enhancement module is used for generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters;
and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
In the foregoing solution, the step of constructing an enhancement module in the task server of the service cluster includes:
acquiring an enhanced file, and configuring the enhanced file in a task server of the service cluster;
the enhanced file is operated to detect the execution state of the task server;
acquiring the execution state of each task server in the service cluster, summarizing to form an execution set, and judging whether the execution set has an execution state with abnormal content;
if so, generating state information with normal content, and reflecting that the service cluster is in a normal state;
if not, generating state information with abnormal content, reflecting the abnormal state of the service cluster, and recording the server number of the execution state with abnormal content in the state information.
In the foregoing solution, the identifying a service cluster in which an abnormality occurs according to the state information and setting the service cluster as an abnormal cluster includes:
sending a check request to a service cluster, and judging whether the service cluster sends state information according to the check request;
if so, judging the service cluster to be normal;
if not, judging that the service cluster is abnormal, and setting the service cluster as an abnormal cluster.
In the foregoing solution, the identifying a service cluster in which an abnormality occurs according to the state information and setting the service cluster as an abnormal cluster includes:
constructing a monitoring interception module;
and operating the monitoring and intercepting module to filter the state information generated by the service cluster so as to identify the state information with abnormal content, and setting the service cluster corresponding to the state information as an abnormal cluster.
In the foregoing solution, the step of forwarding the task information in the abnormal cluster to other service clusters in the service system includes:
acquiring the task type of the abnormal cluster, identifying a task server with abnormality in the abnormal cluster, setting the task server as an abnormal server, and extracting task information received by the abnormal server;
setting a service cluster with the task type consistent with the abnormal cluster in the service system as an alternative cluster, and setting an alternative cluster with the working state according with a preset calling rule as a forwarding cluster, wherein the working state reflects the running state and the working strength of the service cluster;
and taking a task server corresponding to the abnormal server in the forwarding cluster as a target server, sending the task information to the target server, and calling the task server to execute the task information to obtain feedback information.
In the foregoing solution, the step of setting the candidate cluster whose working state meets the preset invoking rule as the forwarding cluster includes:
acquiring the working state of the alternative cluster, extracting the running state information in the working state, and judging whether the running state information with normal content exists; if so, setting the alternative cluster corresponding to the running state information with normal content as a first cluster;
acquiring the working state of the first cluster, extracting working strength information in the working state, and judging whether the working strength information with idle content exists or not; and if so, setting the first cluster corresponding to the working strength information with the idle content as a forwarding cluster and finishing.
In the foregoing solution, after the task information in the abnormal cluster is forwarded to other service clusters in the service system, the method further includes:
sending the cluster number of the abnormal cluster to a control end;
after the cluster number of the abnormal cluster is sent to the control end, the method further includes:
and uploading the cluster number to a block chain.
In order to achieve the above object, the present invention further provides a remote call management apparatus, including:
the communication module is used for acquiring a service system with at least one service cluster and establishing connection with the service cluster;
the state generating module is used for constructing an enhancement module in the task server of the service cluster and generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
the abnormal identification module is used for identifying the abnormal service cluster according to the state information and setting the abnormal service cluster as an abnormal cluster;
and the forwarding execution module is used for forwarding the task information in the abnormal cluster to other service clusters in the service system and executing the task information to obtain feedback information.
To achieve the above object, the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor of the computer device implements the steps of the remote call management method when executing the computer program.
To achieve the above object, the present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the remote call management method.
According to the remote call management method, the remote call management device, the computer equipment and the readable storage medium, the abnormal part in the service system is accurately identified in a mode of identifying the abnormal service cluster and identifying the service cluster, so that the problem that the task information cannot be processed to cause the thread blocking of the service system due to the fact that the task information is routed to the abnormal cluster is avoided. And forwarding the task information in the abnormal cluster to other service clusters in the service system, so that the other service clusters execute the task information to obtain feedback information, thereby ensuring that the task information received by the service system can obtain the feedback information, and further ensuring the stability of the service system.
Drawings
FIG. 1 is a flowchart of a first embodiment of a remote call management method according to the present invention;
FIG. 2 is a schematic diagram of an environment application of a remote call management method according to a second embodiment of the remote call management method of the present invention;
FIG. 3 is a flowchart of a specific method of remotely invoking a management method according to a second embodiment of the remote invocation management method of the present invention;
FIG. 4 is a schematic diagram of program modules of a remote call management apparatus according to a third embodiment of the present invention;
fig. 5 is a schematic diagram of a hardware structure of a computer device according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a remote call management method, a remote call management device, computer equipment and a readable storage medium, which are suitable for the technical field of cloud computing of cloud services and provide a remote call management method based on a communication module, an abnormality identification module and a forwarding execution module. The method comprises the steps of establishing connection with a service cluster by acquiring the service system at least provided with one service cluster; identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters; and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
The first embodiment is as follows:
referring to fig. 1, a remote call management method of the present embodiment is applied to a server having a program, and includes:
s101: acquiring a service system with at least one service cluster, and establishing connection with the service cluster;
s102: constructing an enhancement module in a task server of the service cluster, wherein the enhancement module is used for generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
s103: identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters;
s104: and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
In an exemplary embodiment, a connection is established between a zookeeper and the service cluster, where the zookeeper is a distributed file system, and is used to register a service of the service cluster on a preset path, and the path rule is { service }/{ version }/{ ip: port }, for example: deploying "HelloWorldService" to two machines, two directories are created on zookeeper: are respectively as
/HelloWorldService/1.0.0/100.19.20.01:16888，/HelloWorldService/1.0.0/100.19.20.02:16888。
Whether each task server in the service cluster is abnormal or not is detected, and whether each task server in the service system can work normally or not is detected accurately; the task server abnormity judgment standard is as follows: the received task information cannot be processed and the task information as input data of the next task server cannot be generated.
By identifying abnormal service clusters and accurately identifying abnormal parts in the service system in a service cluster mode, the problem that task information cannot be processed to cause service system thread blocking due to the fact that the task information is routed to the abnormal clusters is solved.
And forwarding the task information in the abnormal cluster to other service clusters in the service system, so that the other service clusters execute the task information to obtain feedback information, thereby ensuring that the task information received by the service system can obtain the feedback information, and further ensuring the stability of the service system. In this embodiment, the task information is rpc (remote Procedure call), that is, the task information is used to generate specified task information or request information for feeding back a result by calling a task server in a service cluster: remote procedure calls, which express that one node (client/task server) requests another node (task server) to provide a service. Which is a request protocol made based on http/https, or dubbo, or redis, or file communication protocols.
Example two:
the embodiment is a specific application scenario of the first embodiment, and the method provided by the present invention can be more clearly and specifically explained through the embodiment.
The method provided in this embodiment is specifically described below by taking as an example that, in a server running a remote call management method, an abnormal service cluster is identified according to the state information, the service cluster is set as an abnormal cluster, and task information in the abnormal cluster is forwarded to other service clusters in the service system. It should be noted that the present embodiment is only exemplary, and does not limit the protection scope of the embodiments of the present invention.
Fig. 2 schematically shows an environment application diagram of a remote call management method according to the second embodiment of the present application.
In an exemplary embodiment, the calling server 2 where the remote calling management method is located is respectively connected with the service system 3 and the control terminal 4 through a network; the server 2 may provide services through one or more networks, which may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. The network may include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and/or the like. The network may include wireless links, such as cellular links, satellite links, Wi-Fi links, and/or the like; the service system 3 at least has one service cluster 31, and the service cluster 31 at least has one task server 311; the control terminal 4 may be a computer device such as a smart phone, a tablet computer, a notebook computer, and a desktop computer.
Fig. 3 is a flowchart of a specific method of a remote call management method according to an embodiment of the present invention, where the method specifically includes steps S201 to S205.
S201: the method comprises the steps of obtaining a service system with at least one service cluster, and establishing connection with the service cluster.
In this step, a connection is established between a zookeeper and the service cluster, where the zookeeper is a distributed file system, and is used to register a service of the service cluster on a preset path, and the path rule is { service }/{ version }/{ ip: port }, for example: deploying "HelloWorldService" to two machines, two directories are created on zookeeper: are respectively as
/HelloWorldService/1.0.0/100.19.20.01:16888，/HelloWorldService/1.0.0/100.19.20.02:16888。
Illustratively, a service system M is obtained, which includes a service cluster S1, a service cluster S2, a service cluster S3, a service cluster S1 and a service cluster S2, which include a task server a, a task server B, and a task server C, respectively; the service cluster S3 includes a task server a, a task server B, and a task server D.
S202: constructing an enhancement module in a task server of the service cluster, wherein the enhancement module is used for generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset business logic.
In order to accurately detect whether each task server in the service system can work normally, an enhancement module is constructed in the task server of the service cluster to detect whether each task server in the service cluster is abnormal; the task server abnormity judgment standard is as follows: the received task information cannot be processed and the task information as input data of the next task server cannot be generated.
In this embodiment, the enhancement file is configured in the task server of the service cluster, and the technical effect of constructing the enhancement module in the task server is achieved by running the enhancement file.
It should be noted that, an enhance. jar data packet may be used as the enhancement file, which includes detecting a processing procedure and a processing result of the task server on the task information when the task server receives the task information; judging whether the task server operates normally or not; if yes, generating j-state information with normal content; and if not, generating state information with abnormal content, and recording the task server number in the state information.
Illustratively, based on the above example, the business logic of the service clusters S1 and S2 is: the method comprises the steps that after a task server A receives task information p, task information a is generated and sent to a task server B, the task server B processes the task information a to obtain task information B and sends the task information B to a task processor C, and the task processor C processes the task information B to obtain feedback information C; and the business logic of the service cluster S3 is: the method comprises the steps that after receiving task information q, a task server A generates task information a and sends the task information a to a task server B, the task server B processes the task information a to obtain task information B and sends the task information B to a task processor D, and the task processor D processes the task information B to obtain feedback information D.
In a preferred embodiment, the step of building an enhancement module in the task server of the service cluster includes:
s21: and acquiring an enhanced file, and configuring the enhanced file in a task server of the service cluster.
In this step, the enhanced file is loaded into a configuration center of the service cluster and configured on each task server of the service cluster.
S22: and operating the enhancement file to detect the execution state of the task server.
In this step, the technical effect of constructing the enhancement module of each task server is achieved by running the enhancement file in the configuration center, wherein the enhancement module is used for detecting whether the execution state of the task server is abnormal in real time, and the execution state includes normal and abnormal.
S23: and acquiring the execution states of the task servers in the service cluster, summarizing the execution states to form an execution set, and judging whether the execution set has an execution state with abnormal content.
S24: and if so, generating state information with normal content, wherein the state information is used for reflecting that the service cluster is in a normal state.
S25: if not, generating state information with abnormal content, reflecting the abnormal state of the service cluster, and recording the server number of the execution state with abnormal content in the state information.
Illustratively, an enhancement module is built in the task server a, the task server B and the task server C of the service cluster S1, the service cluster S2 and the service cluster S3 respectively, and is used for detecting whether an abnormality occurs in the task server a, the task server B and the task server C, for example: downtime, dropped connection, hang-up, etc. If an exception occurs to task server C in service cluster S1, such as: if the connection is lost, status information indicating that the content is abnormal is generated, and the server number FW-S1-C of the task server C is described in the status information.
S203: and identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters.
In order to avoid the problem that the routing of the task information to the abnormal service cluster causes the excessive task information which cannot be processed in the service system and causes the thread blocking of the service system, the step accurately identifies the abnormal part in the service system by identifying the abnormal service cluster and using the service cluster, so as to avoid the problem that the routing of the task information to the abnormal cluster causes the thread blocking of the service system because the task information cannot be processed.
In a preferred embodiment, the step of identifying a service cluster in which an anomaly occurs according to the state information and setting the service cluster as an anomaly cluster includes:
s3-01: sending a check request to a service cluster, and judging whether the service cluster sends state information according to the check request;
s3-02: if so, judging the service cluster to be normal;
s3-03: if not, judging that the service cluster is abnormal, and setting the service cluster as an abnormal cluster.
Specifically, a zookeeper is called to send a check request to a service cluster, wherein the check request is realized by constructing a Socket long connection between the zookeeper and the service cluster and sending a request signal in real time or continuously in the Socket long connection; the socket refers to a socket and is used for abstracting an endpoint for performing bidirectional communication between application processes on different hosts in a network; the long connection is realized by calling a Socket object in the whole connection process between the zookeeper and the service cluster, so that the technical effect of keeping the Socket connection for a long time is achieved. If the service cluster sends state information through the Socket long connection according to the check request, the service cluster is in a normal working state; if the service cluster does not send state information through the Socket long connection according to the check request, it is indicated that the service cluster is abnormal, and the service cluster is set as an abnormal cluster.
In a preferred embodiment, the step of identifying a service cluster in which an anomaly occurs according to the state information and setting the service cluster as an anomaly cluster includes:
s3-11: and constructing a monitoring interception module.
S3-12: and operating the monitoring and intercepting module to filter the state information generated by the service cluster so as to identify the state information with abnormal content, and setting the service cluster corresponding to the state information as an abnormal cluster.
In this embodiment, the state information with abnormal content in the state information generated by the service cluster can be identified without constructing Socket long connection and by constructing a Spring MVC-interceptor as a monitoring and intercepting module, so that the computational burden of the service system is reduced.
It should be noted that the Interceptor (Interceptor) in Spring MVC is similar to the Filter (Filter) in Servlet, and is mainly used to intercept the user request and perform corresponding processing. For example, the interceptor can perform authorization verification, log the requested information, determine whether the user logs in, and the like.
Illustratively, based on the above example, assume that an exception occurs in the service cluster S1, such as: when the task server B in the service cluster S1 sends the task information B to the task server C, the task server C cannot process the task information B received by the task server C due to the fact that the task server C is disconnected.
S204: and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
In order to ensure that the task information received by the service system can all obtain the feedback information so as to ensure the stability of the service system, the task information in the abnormal cluster is forwarded to other service clusters in the service system, so that the other service clusters execute the task information to obtain the feedback information, thereby ensuring that the task information received by the service system can all obtain the feedback information, and further ensuring the stability of the service system. In this embodiment, the task information is rpc (remote Procedure call), that is, the task information is used to generate specified task information or request information for feeding back a result by calling a task server in a service cluster: remote procedure calls, which express that one node (client/task server) requests another node (task server) to provide a service. Which is a request protocol made based on http/https, or dubbo, or redis, or file communication protocols.
Illustratively, since the task types between the service cluster S1 and the service cluster S2 are consistent, the task information b in the service cluster S1 is forwarded into the service cluster S2, and the service cluster S2 can execute the task information b to obtain the feedback information c.
In a preferred embodiment, the step of forwarding the task information in the abnormal cluster to other service clusters in the service system includes:
s41: and acquiring the task type of the abnormal cluster, identifying the task server with the abnormality in the abnormal cluster, setting the task server as an abnormal server, and extracting the task information received by the abnormal server.
In this step, a task type is obtained from the configuration center of the abnormal cluster, and the task type reflects the type and content of the service provided by the abnormal cluster.
Specifically, the step of identifying a task server in which an exception occurs in the exception cluster and setting the task server as an exception server includes:
and extracting a server number in the state information, and setting a task server corresponding to the server number as an abnormal server, wherein the server number corresponds to the abnormal task server.
Illustratively, based on the above example, when the task server B in the service cluster S1 sends the task information B to the task server C, the task server C cannot process the task information B received by the task server C due to a dropped connection, and obtains the number of the task server C: FW-S1-C.
S42: and setting a service cluster with the task type consistent with the abnormal cluster in the service system as an alternative cluster, and setting an alternative cluster with the working state according with a preset calling rule as a forwarding cluster, wherein the working state reflects the running state and the working strength of the service cluster.
In this step, the operating state includes operating state information and working strength information of the service cluster, where the operating state information includes: normal and abnormal; the working strength information includes: busy, normal, idle. Further, the busy state refers to a case where the data amount of the processing task information is higher than a high intensity threshold, the idle state refers to a case where the data amount of the processing task information is lower than a low intensity threshold, and the normal state refers to a case where the data amount of the processing task information is between the high intensity threshold and the low intensity threshold. The task type describes the task type and content executed by the service cluster.
Since the alternative cluster is used for executing the task information which is not completed by the abnormal cluster, only the service cluster with the task type consistent with the abnormal cluster is qualified as the alternative cluster.
Preferably, the invoking rule is:
selecting a service cluster with normal running state information and idle working strength information as a forwarding cluster;
if the service cluster with the working strength information being idle does not exist, selecting the service cluster with the working strength information being common as a forwarding cluster;
if the service cluster does not have the working strength information which is idle and common, the task information is temporarily stored in a preset cache module.
Further, the step of setting the candidate cluster whose working state meets the preset invoking rule as the forwarding cluster includes:
s42-1: acquiring the working state of the alternative cluster, extracting the running state information in the working state, and judging whether the running state information with normal content exists;
s42-2: if so, setting the alternative cluster corresponding to the running state information with normal content as a first cluster;
s42-3: if not, storing the task information in a preset cache module, and executing S42-1 again after a preset buffer time period;
s42-4: acquiring the working state of the first cluster, extracting working strength information in the working state, and judging whether the working strength information with idle content exists or not;
s42-5: if so, setting the first cluster corresponding to the working strength information with the content being idle as a forwarding cluster and ending;
s42-6: if not, judging whether the content is common work intensity information or not;
s42-7: if so, setting the first cluster corresponding to the working strength information with the common content as a forwarding cluster and finishing;
s42-8: if not, the task information is stored in a preset cache module, and after a preset buffer time period, the step S42-1 is executed again.
S43: and taking a task server corresponding to the abnormal server in the forwarding cluster as a target server, sending the task information to the target server, and calling the task server to execute the task information to obtain feedback information.
Illustratively, based on the above example, assuming that the working state of the service cluster S2 is normal and idle, the service cluster S2 is set as a forwarding cluster, and the task information b is sent to the service cluster S2; and because the task server C of the service cluster S1 is in a dropped state, the task server C of the service cluster S2 is taken as a target server, and the task server C of the service cluster S2 executes the task information b to obtain the feedback information C.
In summary, if the task information received by the abnormal cluster, that is, the task information received by the task server located at the head is forwarded to the forwarding cluster, the forwarding cluster will reprocess the task information, so that the task information generated by the task server that is not abnormal in the abnormal cluster is directly discarded, which results in repeated calculation between the forwarding cluster and the abnormal cluster, thereby increasing the computational power consumption of the service system and reducing the generation efficiency of the feedback information. In the technical scheme, the task information received by the abnormal server is identified and routed to other service clusters, so that the problem of repeated processing of the task information does not occur in the process of obtaining the feedback information, the calculation power of a service system is saved, and the operation efficiency of the feedback information is improved.
S205: and sending the cluster number of the abnormal cluster to a control end.
In order to accurately identify the abnormal service cluster, the cluster number of the abnormal cluster is sent to the control end, so that the control end can conveniently and accurately check the abnormal service cluster in time.
Illustratively, the cluster number FW-S1 of the service cluster S1 is sent to the control end, so that the control end can specifically solve the abnormal service cluster. Further, the server number FW-S1-C of the abnormal server in the service cluster S1 can be sent to the control end, so as to further locate the abnormal server.
Preferably, after the sending the cluster number of the abnormal cluster to the control end, the method further includes:
and uploading the cluster number to a block chain.
It should be noted that the corresponding digest information is obtained based on the cluster number, and specifically, the digest information is obtained by hashing the cluster number, for example, by using the sha256s algorithm. Uploading summary information to the blockchain can ensure the safety and the fair transparency of the user. The user equipment may download the summary information from the blockchain to verify whether the cluster number is tampered. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Example three:
referring to fig. 4, a remote invocation management device 1 of the present embodiment includes:
a communication module 11, configured to acquire a service system having at least one service cluster, and establish a connection with the service cluster;
a state generating module 12, configured to build an enhancement module in a task server of the service cluster, and configured to generate state information reflecting an operating state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
an anomaly identification module 13, configured to identify a service cluster in which an anomaly occurs according to the state information, and set the service cluster as an anomaly cluster;
and a forwarding execution module 14, configured to forward the task information in the abnormal cluster to other service clusters in the service system, and execute the task information to obtain feedback information.
Optionally, the remote call management apparatus 1 further includes:
and the exception output module 15 is configured to send the cluster number of the exception cluster to the control end.
Optionally, the state generating module 12 further includes:
an enhanced configuration unit 121, configured to obtain an enhanced file, and configure the enhanced file in a task server of the service cluster;
a detection operation unit 122, configured to operate the enhanced file, so as to detect an execution state of the task server;
a summary judgment unit 123, configured to obtain execution statuses of the task servers in the service cluster, summarize the execution statuses to form an execution set, and judge whether the execution set has an execution status with abnormal content;
a normal state unit 124, configured to generate state information with normal content, and reflect that the service cluster is in a normal state;
an abnormal state unit 125, configured to generate state information with abnormal content, reflect that the service cluster is in an abnormal state, and record the server number of the execution state with abnormal content in the state information.
Optionally, the anomaly identification module 13 further includes:
the inspection feedback unit 131 is configured to send an inspection request to a service cluster, and determine whether the service cluster sends status information according to the inspection request;
a normality determination unit 132 configured to determine that the service cluster is normal;
an anomaly determination unit 133, configured to determine that the service cluster is anomalous, and set the service cluster as an anomalous cluster.
Optionally, the anomaly identification module 13 further includes:
a module construction unit 134, configured to construct a monitoring interception module;
a filtering and identifying unit 135, configured to operate the monitoring and intercepting module to filter the state information generated by the service cluster, so as to identify state information whose content is abnormal, and set the service cluster corresponding to the state information as an abnormal cluster.
Optionally, the forwarding execution module 14 further includes:
the type identification unit 141 is configured to obtain a task type of the abnormal cluster, identify a task server in which an abnormality occurs in the abnormal cluster, set the task server as an abnormal server, and extract task information received by the abnormal server.
A forwarding identification unit 142, configured to set a service cluster in the service system whose task type is consistent with the abnormal cluster as an alternative cluster, and set an alternative cluster whose working state meets a preset call rule as a forwarding cluster, where the working state reflects an operating state and a working intensity of the service cluster.
And the target identification unit 143 is configured to use a task server corresponding to the abnormal server in the forwarding cluster as a target server, send the task information to the target server, and call the task server to execute the task information to obtain feedback information.
The technical scheme is applied to the field of cloud computing of cloud services, particularly to a cluster computing scene, and establishes connection with a service cluster by acquiring a service system at least with one service cluster; identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters; and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
Example four:
in order to achieve the above object, the present invention further provides a computer device 5, where components of the remote call management apparatus according to the third embodiment may be distributed in different computer devices, and the computer device 5 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster formed by multiple application servers) that executes programs. The computer device of the embodiment at least includes but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in FIG. 5. It should be noted that fig. 5 only shows a computer device with components, but it should be understood that not all of the shown components are required to be implemented, and more or fewer components may be implemented instead.
In this embodiment, the memory 51 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the memory 51 may be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device. Of course, the memory 51 may also include both internal and external storage devices of the computer device. In this embodiment, the memory 51 is generally used for storing an operating system and various application software installed in the computer device, such as program codes of the remote call management apparatus in the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 52 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In this embodiment, the processor 52 is configured to execute the program code stored in the memory 51 or process data, for example, execute the remote call management device, so as to implement the remote call management method of the first embodiment and the second embodiment.
Example five:
to achieve the above objects, the present invention also provides a computer readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, which when executed by a processor 52, implements corresponding functions. The computer-readable storage medium of the present embodiment is used to store a computer program for implementing the remote call management method, and when executed by the processor 52, implements the remote call management method of the first and second embodiments.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A remote call management method, comprising:
acquiring a service system with at least one service cluster, and establishing connection with the service cluster;
constructing an enhancement module in a task server of the service cluster, wherein the enhancement module is used for generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
identifying abnormal service clusters according to the state information, and setting the service clusters as abnormal clusters;
and forwarding the task information in the abnormal cluster to other service clusters in the service system for executing the task information to obtain feedback information.
2. The remote call management method according to claim 1, wherein the step of building an enhancement module in a task server of the service cluster comprises:
acquiring an enhanced file, and configuring the enhanced file in a task server of the service cluster;
the enhanced file is operated to detect the execution state of the task server;
acquiring the execution state of each task server in the service cluster, summarizing to form an execution set, and judging whether the execution set has an execution state with abnormal content;
if so, generating state information with normal content, and reflecting that the service cluster is in a normal state;
if not, generating state information with abnormal content, reflecting the abnormal state of the service cluster, and recording the server number of the execution state with abnormal content in the state information.
3. The remote call management method according to claim 1, wherein the step of identifying a service cluster in which an abnormality occurs according to the state information and setting the service cluster as an abnormal cluster comprises:
sending a check request to a service cluster, and judging whether the service cluster sends state information according to the check request;
if so, judging the service cluster to be normal;
if not, judging that the service cluster is abnormal, and setting the service cluster as an abnormal cluster.
4. The remote call management method according to claim 1, wherein the step of identifying a service cluster in which an abnormality occurs according to the state information and setting the service cluster as an abnormal cluster comprises:
constructing a monitoring interception module;
and operating the monitoring and intercepting module to filter the state information generated by the service cluster so as to identify the state information with abnormal content, and setting the service cluster corresponding to the state information as an abnormal cluster.
5. The remote call management method according to claim 1, wherein the step of forwarding the task information in the exception cluster to other service clusters in the service system comprises:
acquiring the task type of the abnormal cluster, identifying a task server with abnormality in the abnormal cluster, setting the task server as an abnormal server, and extracting task information received by the abnormal server;
setting a service cluster with the task type consistent with the abnormal cluster in the service system as an alternative cluster, and setting an alternative cluster with the working state according with a preset calling rule as a forwarding cluster, wherein the working state reflects the running state and the working strength of the service cluster;
and taking a task server corresponding to the abnormal server in the forwarding cluster as a target server, sending the task information to the target server, and calling the task server to execute the task information to obtain feedback information.
6. The remote call management method according to claim 5, wherein the step of setting the candidate cluster whose operating state meets the preset call rule as the forwarding cluster comprises:
acquiring the working state of the alternative cluster, extracting the running state information in the working state, and judging whether the running state information with normal content exists; if so, setting the alternative cluster corresponding to the running state information with normal content as a first cluster;
acquiring the working state of the first cluster, extracting working strength information in the working state, and judging whether the working strength information with idle content exists or not; and if so, setting the first cluster corresponding to the working strength information with the idle content as a forwarding cluster and finishing.
7. The remote call management method according to claim 1, wherein after forwarding the task information in the exception cluster to other service clusters in the service system, the method further comprises:
sending the cluster number of the abnormal cluster to a control end;
after the cluster number of the abnormal cluster is sent to the control end, the method further includes:
and uploading the cluster number to a block chain.
8. A remote call management apparatus, comprising:
the communication module is used for acquiring a service system with at least one service cluster and establishing connection with the service cluster;
the state generating module is used for constructing an enhancement module in the task server of the service cluster and generating state information reflecting the running state of the task server; the service cluster is constructed by at least one task server according to preset service logic;
the abnormal identification module is used for identifying the abnormal service cluster according to the state information and setting the abnormal service cluster as an abnormal cluster;
and the forwarding execution module is used for forwarding the task information in the abnormal cluster to other service clusters in the service system and executing the task information to obtain feedback information.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the remote call management method according to any of claims 1 to 7 are implemented by the processor of the computer device when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, the computer program stored on the computer-readable storage medium, when being executed by a processor, implementing the steps of the remote call management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110484348.2A CN113190364A (en) | 2021-04-30 | 2021-04-30 | Remote call management method and device, computer equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110484348.2A CN113190364A (en) | 2021-04-30 | 2021-04-30 | Remote call management method and device, computer equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113190364A true CN113190364A (en) | 2021-07-30 |
Family
ID=76983697
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110484348.2A Pending CN113190364A (en) | 2021-04-30 | 2021-04-30 | Remote call management method and device, computer equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113190364A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778695A (en) * | 2021-11-12 | 2021-12-10 | 深圳华锐金融技术股份有限公司 | Memory snapshot management method, device, equipment and medium crossing application life cycle |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103312541A (en) * | 2013-05-28 | 2013-09-18 | 浪潮电子信息产业股份有限公司 | Management method of high-availability mutual backup cluster |
| CN107959705A (en) * | 2016-10-18 | 2018-04-24 | 阿里巴巴集团控股有限公司 | The distribution method and control server of streaming computing task |
| CN110287053A (en) * | 2019-06-27 | 2019-09-27 | 四川新网银行股份有限公司 | The method that distributed system is uniformly processed extremely |
| CN112463535A (en) * | 2020-11-27 | 2021-03-09 | 中国工商银行股份有限公司 | Multi-cluster exception handling method and device |
| CN112463451A (en) * | 2020-12-02 | 2021-03-09 | 中国工商银行股份有限公司 | Cache disaster recovery cluster switching method and soft load balancing cluster device |
-
2021
- 2021-04-30 CN CN202110484348.2A patent/CN113190364A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103312541A (en) * | 2013-05-28 | 2013-09-18 | 浪潮电子信息产业股份有限公司 | Management method of high-availability mutual backup cluster |
| CN107959705A (en) * | 2016-10-18 | 2018-04-24 | 阿里巴巴集团控股有限公司 | The distribution method and control server of streaming computing task |
| CN110287053A (en) * | 2019-06-27 | 2019-09-27 | 四川新网银行股份有限公司 | The method that distributed system is uniformly processed extremely |
| CN112463535A (en) * | 2020-11-27 | 2021-03-09 | 中国工商银行股份有限公司 | Multi-cluster exception handling method and device |
| CN112463451A (en) * | 2020-12-02 | 2021-03-09 | 中国工商银行股份有限公司 | Cache disaster recovery cluster switching method and soft load balancing cluster device |
Non-Patent Citations (1)
| Title |
|---|
| 吕德超: "游戏业务受理系统中定时任务子系统的设计与实现", 《中国优秀博硕士学位论文全文数据库（硕士）信息科技辑（月刊）》士）信息科技辑（月刊）》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778695A (en) * | 2021-11-12 | 2021-12-10 | 深圳华锐金融技术股份有限公司 | Memory snapshot management method, device, equipment and medium crossing application life cycle |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11323471B2 (en) | Advanced cybersecurity threat mitigation using cyberphysical graphs with state changes | |
| US20180295154A1 (en) | Application of advanced cybersecurity threat mitigation to rogue devices, privilege escalation, and risk-based vulnerability and patch management | |
| US20180219894A1 (en) | User and entity behavioral analysis using an advanced cyber decision platform | |
| US11539663B2 (en) | System and method for midserver facilitation of long-haul transport of telemetry for cloud-based services | |
| CN109558366B (en) | Firewall based on multiprocessor architecture | |
| CN106911648B (en) | Environment isolation method and equipment | |
| CN111641563B (en) | Flow self-adaption method and system based on distributed scene | |
| US20200167342A1 (en) | System for Secure Software Defined Networking Based on Block-Chain and Method Thereof | |
| US10924327B2 (en) | Autonomous server agents | |
| WO2020232195A1 (en) | Method for midserver facilitation of long-haul transport of telemetry for cloud-based services | |
| CN112055017B (en) | Single-account multi-application unified login method and device and computer equipment | |
| WO2020224100A1 (en) | Blockchain configuration file processing apparatus, system, and method, and storage medium | |
| CN110661853A (en) | Data proxy method, device, computer equipment and readable storage medium | |
| US20220060510A1 (en) | System and method for aggregating and securing managed detection and response connection interfaces between multiple networked sources | |
| CN111585805B (en) | Smooth release upgrading method and device, computer system and readable storage medium | |
| US20230239293A1 (en) | Probe-based risk analysis for multi-factor authentication | |
| CN110896362B (en) | Fault detection method and device | |
| WO2019018829A1 (en) | Advanced cybersecurity threat mitigation using behavioral and deep analytics | |
| CN112087475B (en) | Message pushing method and device for cloud platform component application and message server | |
| CN111586022A (en) | Firewall opening verification method, electronic device, computer equipment and storage medium | |
| CN113190364A (en) | Remote call management method and device, computer equipment and readable storage medium | |
| US20230168816A1 (en) | Systems, methods and computer readable media for software defined storage security protection | |
| CN114780327A (en) | Server monitoring method, asset management method and PCIE card | |
| US20230328132A1 (en) | System and method for midserver integration and transformation of telemetry for cloud - based services | |
| US11368305B2 (en) | Hardware security module extension |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210730 |