CN109614209B - A task processing method, application server and system - Google Patents

Abstract

The embodiment of this specification provides a task processing method. When a task is created, the corresponding task information includes the identification of the server that created the task. When performing task processing, based on the user identification in each task information, the task processing device converts the task The information is distributed to the first application server. Based on the task information, the first application server generates a list of tasks to be processed, broadcasts the list of tasks to be processed to all application servers, and controls each application server to process the tasks identified in the list of tasks to be processed. Consistent pending tasks. In this way, the task list that needs to be processed can be broadcast to all application servers, and the application server that receives the task list only processes the tasks created by itself and discards other tasks, thereby ensuring logical consistency and the success rate of task processing.

Description

A task processing method, application server and system

technical field

The embodiments of this specification relate to the field of Internet technologies, and in particular, to a task processing method, application server and system.

Background technique

With the rapid development of the Internet, the continuous improvement and development of Internet business systems have been promoted, bringing great convenience to people's lives. However, with the increase of business, in the development environment, in order to verify their respective business, a variety of servers with different code logic are deployed offline, and the code deployed by each server may be inconsistent. Many tasks are easily dispatched to other business servers during task processing, and the assigned server does not have the code logic to process the assigned tasks, resulting in task processing failure.

Contents of the invention

The embodiment of this specification provides a task processing method, application server and system.

In the first aspect, the embodiment of this specification provides a task processing method, which is applied to a task processing system, where the task processing system includes a task processing device and multiple application servers, and the task processing method includes:

The task processing device acquires task information of a task to be processed, and distributes the task information to a first application server corresponding to the user identifier based on a user identifier in the task information, wherein the first application The server belongs to the plurality of application servers, the task information includes the server identification of the second application server that creates the task to be processed and the user identification corresponding to the task to be processed, and the second application server is configured to a processing module for processing the task to be processed;

The first application server receives the task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to the multiple application servers, and the list of tasks to be processed carries all the server ID;

Each application server in the multiple application servers receives the pending task list, and processes the pending task after confirming that the server ID in the pending task list is consistent with its own server ID .

In the second aspect, the embodiment of this specification provides a task processing system, including a task processing device and multiple application servers, wherein:

The task processing device is configured to acquire task information of a task to be processed, and distribute the task information to a first application server corresponding to the user identifier based on a user identifier in the task information, wherein the second An application server belongs to the plurality of application servers, and the task information includes the server identifier of the second application server that creates the task to be processed and the user identifier corresponding to the task to be processed, and the second application server sets There is a processing module for processing said pending tasks;

The first application server receives the task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to the multiple application servers, and the list of tasks to be processed carries all the server ID;

Each application server in the multiple application servers receives the pending task list, and processes the pending task after confirming that the server ID in the pending task list is consistent with its own server ID .

In a third aspect, the embodiment of this specification provides an application server, the method includes:

Create a target to-be-processed task, and add the server identifier of the application server to the task information of the target to-be-processed task;

receiving a pending task list, the task information of each pending task is stored in the pending task list;

Traverse the task information of each pending task in the pending task list, and determine the target pending task whose server identifier in the task information is consistent with the server identifier of the application server;

Process the target pending task.

In a fourth aspect, the embodiment of this specification provides an application server, including:

A creating unit, configured to create a target pending task, and add the server identifier of the application server to the task information of the target pending task;

a receiving unit, configured to receive a list of tasks to be processed, wherein task information of each task to be processed is stored in the list of tasks to be processed;

A determining unit, configured to traverse the task information of each pending task in the pending task list, and determine the target pending task whose server identifier in the task information is consistent with the server identifier of the application server;

A processing unit, configured to process the target task to be processed.

In the fifth aspect, the embodiment of this specification provides an application server, including a memory, a processor, and a computer program stored in the memory and operable on the processor. When the processor executes the program, the above-mentioned tasks in the third aspect are realized. The steps of the processing method.

In a sixth aspect, the embodiment of this specification provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the above-mentioned task processing method in the third aspect are implemented.

The beneficial effects of the embodiments of this specification are as follows:

In the task processing method applied to the task processing system provided by the embodiment of this specification, when the application server creates a task, the corresponding task information includes the server ID that created the task, and records which server the task was created by, and then, in When performing task processing, the task processing device acquires task information of tasks to be processed, and based on the user identification in the task information, distributes the task information to a first application server corresponding to the user identification, wherein the first application server belongs to multiple application server, the task information includes the server ID of the second application server that creates the task to be processed and the user ID corresponding to the task to be processed, the second application server is provided with a processing module for processing the task to be processed, and then the first application server receives Task information, generate a pending task list based on the task information, and broadcast the pending task list to multiple application servers, the pending task list carries the server identifier, and finally, each application server in the multiple application servers receives the pending task list, and after confirming that the server ID in the pending task list is consistent with its own server ID, the pending task is processed. In this way, the task list that needs to be processed can be broadcast to all application servers, and the application server that receives the task list only processes the tasks created by itself and discards other tasks, thereby ensuring logical consistency and the success rate of task processing.

Description of drawings

Fig. 1 is a schematic diagram of the task processing system provided by the first aspect of the embodiment of this specification;

FIG. 2 is a schematic diagram of the application of the task processing system provided in the first aspect of the embodiment of this specification to an account opening scenario;

FIG. 3 is a schematic diagram of an existing distribution method in the task processing system provided by the first aspect of the embodiment of this specification;

Fig. 4 is a schematic diagram of a task processing method in the task processing system provided by the first aspect of the embodiment of the present specification;

Fig. 5 is a system flow chart of the application of the task processing system provided in the first aspect of the embodiment of this specification to a specific example;

FIG. 6 is a specific example of converting parameter information in an asynchronous task into JSON format in the task processing system provided by the first aspect of the embodiment of this specification;

Fig. 7 is an example diagram of specific asynchronous task scheduling in the task processing system provided by the first aspect of the embodiment of this specification;

FIG. 8 is a flow chart of a task processing method applied to a task processing system provided by the second aspect of the embodiment of this specification;

FIG. 9 is a flowchart of a task processing method applied to an application server provided by the third aspect of the embodiment of this specification;

FIG. 10 is a schematic structural diagram of the application server provided by the fourth aspect of the embodiment of this specification;

Fig. 11 is a schematic structural diagram of the application server provided by the fifth aspect of the embodiment of this specification.

Detailed ways

In order to better understand the above technical solutions, the technical solutions of the embodiments of this specification will be described in detail below through the drawings and specific examples. It should be understood that the embodiments of this specification and the specific features in the embodiments are the technical solutions of the embodiments of this specification. It is a detailed description, rather than a limitation to the technical solutions of this specification. In the case of no conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

In the first aspect, the embodiment of this specification provides a task processing system, please refer to FIG. 1 , which includes a task processing device 101 and multiple application servers 102, wherein:

The task processing device 101 is configured to acquire task information of a task to be processed, and distribute the task information to a first application server corresponding to the user identification based on the user identification in the task information, wherein the first application server belongs to multiple application servers, The task information includes the server identification of the second application server that creates the task to be processed and the user identification corresponding to the task to be processed, and the second application server is provided with a processing module for processing the task to be processed;

The first application server receives task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to multiple application servers, and the list of tasks to be processed carries a server identifier;

Each application server among the plurality of application servers receives the list of tasks to be processed, and processes the tasks to be processed after confirming that the server identification in the list of tasks to be processed is consistent with its own server identification.

Wherein, the task processing system further includes a scheduling center 103, and the scheduling center 103 is used to periodically trigger asynchronous tasks, and notify the task processing device 101 to process pending tasks in the preset task list, so that the task processing device 101 starts from the preset task list Get the task information of the pending task.

The task processing system also includes a communication device, which is used to receive the service request sent by the user terminal before the task processing device obtains the task information of the task to be processed, and notify the second application server corresponding to the service request to create a service request corresponding to the service request. pending tasks.

Wherein, after receiving the notification from the communication device, the second application server creates a task to be processed corresponding to the service request, and adds the server identifier to the task information of the task to be processed.

Specifically, in this embodiment, the service request sent by the user terminal is first received through the communication device, and the corresponding second application server is notified to create a task to be processed corresponding to the service request. Specifically, the user terminal sends some service requests, and the system Assign it to the corresponding second application server. The second application server creates tasks to be processed for the user's business request. In order to solve the problem that the logic inconsistency of each application server code leads to the failure of task processing, the second application server creates a task corresponding to the business request. When a task is to be processed, the second server has a processing module (code logic) for processing the task to be processed, adds its own server identification to the task information of the task to be processed, and stores the task to be processed and the task information to the preset task table.

Then, the scheduling center 103 periodically triggers the asynchronous tasks, and notifies the task processing device 103 to process the preset number of pending tasks in the preset task list. For example: schedule 1000 pending tasks each time. The task processing unit 103 is notified to process the preset number of pending tasks specified in the preset task table.

Furthermore, after receiving the task information of the task to be processed sent by the dispatching center 103, the task processing device 103 performs three-tier distribution of tasks. First, the first layer of distribution is performed, and based on the user identifier in the task information, the task information is distributed to the first application server corresponding to the user identifier. Then, the second layer of distribution is performed. Based on the assigned task information, the first application server reads the corresponding tasks to be processed according to the preset strategy, generates a list of tasks to be processed, and broadcasts the list of tasks to be processed to all application servers. Finally, the third layer of distribution is carried out, each application server in the system processes the pending tasks in the pending task list consistent with its own server ID, and discards the pending tasks inconsistent with its own server ID. In this way, the task list that needs to be processed can be broadcast to all application servers, and the application server that receives the task list only processes the tasks created by itself and discards other tasks, thereby ensuring logical consistency and the success rate of task processing.

The task processing system in this embodiment may be an account opening service system, and the task to be processed is an account opening task. Specifically, this embodiment mainly describes the task processing process of the task processing system in this embodiment in detail based on an account opening scenario.

Please refer to FIG. 2 , which is a schematic diagram of a scenario where the task processing system of this embodiment is applied to an account opening. User terminals 1, 2...n on the user side, when initiating account opening requests, send them to the task processing system (namely: account opening service system), which converts them into asynchronous tasks through the account opening service system, controls the number of concurrent tasks, and reports to financial institutions The server initiates an account opening request service. The number of user terminals 1, 2...n may be the centralized account opening requests of a large number of users in the same time period, which may be received by the account opening service system synchronously or in real time all the time. The account opening service system mainly includes a dispatch center 103 and a task processing device, which are used to process the account opening requests of these user terminals 1, 2...n, and store the account opening requests of each user terminal 1, 2...n in the preset task through an asynchronous thread table. Then, according to the time period configured by the dispatching center 103, asynchronous tasks are periodically triggered to retrieve the account opening requests stored in the preset task table, and the task processing device distributes them layer by layer to the application servers in the platform, so that the task can be Balanced distribution to all application servers in the platform for execution significantly improves the overall processing capability of the system. On the other hand, it controls the number of tasks for initiating account opening business to financial institution servers and eases the processing burden on financial institution servers.

First, the communication device receives account opening request information sent by the user terminal.

Among them, the number of user terminals that initiate an account opening request may be tens of thousands, or even hundreds of millions of massive users. At the same time, the time for a user terminal to initiate an account opening request cannot be accurately estimated. Account opening requests sent by each user terminal respectively, specifically, a large amount of account opening request information can be received at the same time, or can be received collectively within a time period. Or due to factors such as network instability, multiple account opening request messages are repeatedly initiated. Such a situation naturally brings about the simultaneous acceptance and high-concurrency processing of massive account opening requests.

At this time, you can set the resend limit on the user terminal side through the payment APP. When it is detected that the user initiates multiple account opening requests within a short period of time (such as: repeatedly initiating multiple account opening requests), the account opening request information is restricted from being sent out, and the page Prompt the user to operate too frequently, and suspend the attempt to open an account. This can also reduce the request burden of the financial institution server and the account opening service system applying the method, and also prevent some criminals or malicious users from causing request congestion and paralysis to the system or damage to the system through traffic storms.

Then, assign the account opening request to the corresponding second application server, the second application server creates an account opening task for the account opening request, adds its own server identification to the task information of the account opening task, and saves the account opening task in the preset task table .

Wherein, the received account opening request information may be verified first, the validity of the transaction parameters in the account opening request is verified, and the account opening task corresponding to the verified account opening request information is saved in the preset task table.

Further, verification may include identity verification of account opening request information, such as: user ID number, ID card photo, passport number, passport photo, user's recent photo, bank card number, and/or date of birth and other information. Basic checksum check. Specific examples: ID card number digits/rules, passport number digits/rules, date of birth and ID number matching degree, the authenticity of ID card photos/passport photos through image recognition methods, whether the user's recent photo is a face Frontal pictures etc. In this way, the risk of system funds caused by false users opening financial accounts can be guaranteed, and the flood of false account opening request information sent to financial institution servers can also be prevented.

Furthermore, the verification can also include security verification, such as: perform necessary data security detection on the account opening request information to prevent tampering through special fields or reserved extension fields in the information, resulting in malicious codes, which is harmful to system security. cause great danger.

Wherein, the preset task table only stores the account opening task corresponding to the account opening request information that passes the verification. Further, the account opening request information that fails the verification is discarded, and the corresponding user terminal is notified that the account opening request verification fails, and the user is asked to re-verify whether the information filled in for account opening is accurate.

In addition, the account opening request information that fails repeated verification can be blacklisted, and the UID corresponding to the failed account opening request information and the account opening filling information can be extracted and stored in the blacklist log information. At the same time, the system sends a control message to restrict the user terminal. Pay for the use of the APP.

Further, after the account opening task corresponding to the verified account opening request information is stored in the preset task table, the communication device returns a message notification that the account opening request of the user terminal has been successfully accepted. In this way, the user can promptly know whether the account opening request is successfully accepted, and the user experience will not be degraded due to the uncertain processing time of the financial institution server.

Still further, the account opening task corresponding to the account opening request information is saved in the preset task table through the asynchronous thread. In this way, a large number of account opening requests from user terminals that may be sent synchronously are converted into asynchronous tasks, and processed after waiting for subsequent triggers, so that the account opening business applications with relatively concentrated time points are processed in batches in an orderly and periodic manner, ensuring the entire system tasks The processing load is balanced and stable, and the impact on the business burden of financial institutions' servers will not be aggravated.

Then, the scheduling center 103 periodically triggers an asynchronous task to extract the account opening task in the preset task list.

Among them, the scheduling center 103 is responsible for periodically triggering the asynchronous tasks, which are used to process the account opening tasks stored in the preset task table, so as to realize the synchronous acceptance and asynchronous processing of the account opening request.

Further, according to the CRON expression configured by the dispatching center 103, the asynchronous task is triggered periodically. Specifically, for example, a configuration file is stored in the dispatching center 103, and based on the CRON expression in the configuration file, the sending of the asynchronous task trigger message is executed according to the agreed time period. The asynchronous task trigger message is sent to the task processing device 103, corresponding to the account opening task in the preset task list.

Still further, the scheduling center 103 sets the number of asynchronous tasks sent periodically each time according to the configuration file. The asynchronous task can correspond to the processing of one account opening request information, or can correspond to the processing of multiple account opening request information. The number of asynchronous tasks sent each time can also be set to one piece or a specific number of multiple pieces. According to the configuration requirements in the asynchronous task, a corresponding number of account opening requests in the preset task table are extracted and delivered to the task processing device 103 for distribution processing.

Wherein, the task processing device 103 includes a receiving unit, a first sub-unit, a second distribution unit, and a third distribution unit. Further, according to considerations such as the expansion of business scale and the expansion of more diverse business models, the task processing device 103 can be extended to the fourth, fifth or more layers of processing units, so that each application server in the task processing device 103 is in the task distribution Balanced, load stable state. Further, the task processing device 103 may be a multi-tier application server cluster.

Taking the above-mentioned three-layer distribution unit as an example, the first layer is that the task processing device 101 divides the 100 account opening tasks instructed by the dispatch center 103 according to user identifiers. Specifically, the account opening request information is split according to the numerical range of the UID in the account opening task information, and the split account opening request information is distributed to multiple application servers according to the UID.

For example: the user's account opening data is stored in 100 tables of 100 databases according to the dimension of the user identification UID, the last two and three digits respectively. Suppose the system provides a total of 100 databases finauth_rz_00~finauth_rz_99, corresponding to a total of 100 task tables fa_task_00~fa_task_99. If the user ID of the current user is 208800000190, since the last two or three digits are 19, the relevant data of the account opening task corresponding to this user is stored in the fa_task_19 table of the finauth_rz_19 database. The user identifiers UID=2088000001 to 2088000991 corresponding to the 100 account opening tasks dispatched by the dispatching center 103 can be divided into 100 parts according to the last two or three digits of the UID.

Specifically, the account opening task information of the account opening task may be distributed to the specified first application server according to the value matching method. The range of users that each application server can handle is controlled by a unit configuration center. If the processing range of application server A is 00, then the account opening task information with the last two or three digits of the user ID UID being 00 is assigned to server A .

Of course, random distribution can also be used. For example: 200 application servers are included, 100 first application servers are randomly selected, and a number from 00-99 is randomly assigned to each first application server, and the first application server receiving the number can process the matching user ID corresponding Account opening task. If the application server B is assigned the number 01, it means that the application server B can read the account opening task data whose user ID is UID=2088000011 from the fa_task_01 table of the finauth_rz_01 database, and perform task processing.

Then do the second layer distribution. Each first application server reads the user ID assigned to the account opening task information, and determines the database for task retrieval according to the last two or three digits of the user ID, assuming that the account opening task information has the last two or three user IDs The two digits are 03, and the application server can retrieve account opening tasks from the fa_task_03 table of the finauth_rz_03 database, and can read a preset number of account opening tasks (such as: 5, 10, etc.) each time. Based on the read account opening tasks, an account opening task list is generated and broadcast to all application servers in the entire network. In a specific implementation process, the preset number can be set according to actual needs, which is not limited in this application.

Before broadcasting, the first application server needs to judge the current environment. If the current environment is an offline development environment, since in the offline development environment, developers can deploy application servers according to business needs, the processing functions of each application server are not correct. wait. As shown in Diagram 3, if the three business branch codes are deployed on three application servers A, B, and C respectively, and the second-class account of bank A with task ID 1 is created on the three servers A, B, and C respectively, Query the second-class account of bank A with task ID 2, and open an account for the second-class account of bank B with task ID 3. When the third-tier task is dispatched, the obtained tasks will be randomly assigned. If task ID2 is assigned to application server C, task ID3 will be assigned To application server A, because the account opening logic of bank A and bank B is inconsistent, the processors of application server A and application server C are also different, which will result in that application server A and application server C receiving the task do not have suitable processors To process the task, because the application server that creates the task deploys a handler to process the task. Therefore, in the offline development environment, the task needs to be assigned to the application server that creates the task. In this embodiment, a distributed broadcast method may be used to send the task list to multiple master nodes, and each master node broadcasts it to multiple application servers. If the current environment is an offline development environment, the first application server sends the read task list corresponding to the account opening task to all application servers in the entire network.

Finally, the third layer of distribution is carried out. In an offline development environment, after each application server receives the task list, it loops through each task in the task list to determine whether the task is created by itself, that is, if the pending task list The server ID in the task information of the task to be processed is consistent with its own server ID, indicating that the task is created by itself, and the task data corresponding to the task is obtained for processing. If the task is not created by itself, it will be discarded. Through this broadcast method, various created tasks can be processed separately.

For the example in Figure 3 mentioned above, after adopting the system in this embodiment, please refer to Figure 4. On the basis of the original task model, a Host field is added to record the server identification. This field records which server the current task is assigned to. When the server is created, the previous three tasks will be packaged into a task list and sent to the main node application server, and then the main node application server will implement the broadcast of the application servers within the corresponding range, so that each application server can obtain the full amount of 1, 2, 3Three tasks, each server judges whether the host of the task is consistent with the host of the current server, if it is consistent, it will be processed, if it is inconsistent, it will be discarded, so that the server that created the task can execute the task. Solved the problem that the code flow of different servers is inconsistent, the received task cannot be processed or the processing logic is incorrect.

If the current environment is not an offline development environment, the read tasks can be randomly dispatched to the application server through remote method calls again. The application server assembles different messages according to different task types, and sends the account opening or account opening results through the gateway The query task goes to the financial institution server.

Furthermore, the account opening result may also be returned to the user terminal. Wherein, the account opening result information may be actively pushed to the corresponding user terminal, or the account opening result may be returned to the user terminal after the user terminal initiates an account opening result query request. This effectively avoids the unbalanced load of system data traffic.

Fig. 5 is a system flow chart of this application to a specific example. As shown in the figure, finsignweb is the payment APP of the user terminal, and finauth is the application server in the account opening service system in the second embodiment above, and its main responsibilities include: organization-oriented signing; customer-oriented authentication, authentication and signing request The arrangement of process services related to institutional capabilities, including: institutional four-factor authentication, three-element authentication, institutional multi-certificate verification capabilities, institutional SMS verification, and institutional visa-free capacity arrangement and matching, etc. The account opening service system consists of a finauth device cluster with a three-tier distribution mechanism. The user first sends the request information for filling in bank card information, identity information, etc. to apply for account opening through finsignweb to the account opening service system of the finauth application server cluster with a three-tier distribution mechanism. The legality of the information is verified by the system, and the account opening request information that passes the verification is saved in the preset task table through an asynchronous thread. In the system, the scheduling center 103 triggers the asynchronous task regularly, and the task processing device 103 processes the asynchronous account opening task, and invokes the three-layer distribution mechanism to process the asynchronous task. The account opening request is encapsulated into a message and sent to the bank through the gateway, and the bank will feedback the acceptance result.

Furthermore, when the account opening service system receives an account opening request, it will convert the account opening request information into an asynchronous task through an asynchronous thread. The asynchronous task includes task type, business ID, business type, task status, task priority, trigger time, At the same time, the parameter information in the asynchronous task is converted into JSON format and stored in the extended information (as shown in Figure 6), so this task scheduling model can be abstracted into a general asynchronous task, and There is no need to care about the specific business meaning. When the dispatch center 103 triggers the processing of the three-tier task, the retrieved task will find a suitable task processor to process the business according to the task type. There is already a Account opening application, account opening inquiry tasks. In the future, more other asynchronous task processors can be expanded according to the needs of the business. The task processors are isolated from each other, and the new business will not affect the original business. Make asynchronous tasks have good scalability.

As shown in FIG. 7 , it is an example diagram of a specific asynchronous task scheduling in the solution of this specification. The scheduling center 103 periodically sends messages to the message center according to the configured CRON expression, and the message center delivers the messages to the finauth application server cluster. In the first layer of distribution, the task processing device 101 processes the scope according to the UID of the current application deployment unit The account opening request information is split, and the split account opening request information is dispatched to other finauth application servers of the application deployment unit through remote method calls. Set some devices in the cluster to only serve user terminals within a certain range, for example: user terminal UID = 2088000001 to 2088000991, according to the last two or three digits of UID, it can be divided into 100 parts, each device can handle users The range is controlled by a unit configuration center. If the processing range of the current finauth application server A is 00-19, then the condition is satisfied means that the last two or three digits of the user UID meet the range of 00-19.

In the second layer of distribution, the finauth application server that receives the account opening request information sent by the task processing device extracts tasks that meet the conditions from the corresponding database according to the UID and status information in the account opening request information, generates a task list, and broadcasts the task list to each application server.

In the third-tier distribution, each application server processes the tasks created by itself extracted from the task list. Specifically, the application server assembles the message according to the task, and sends the account opening or account opening result query task to the financial institution server through the gateway.

For the task of successfully accepting the account opening, the system will execute the query request of the account opening result in the next task scheduling, update the task status after obtaining the clear account opening result, and write back the account opening result information to the business table. Specifically, you can Stored in a table of a database, this table is used as a business table and can be used to store the result information of the user's application to the server of the banking institution to open an account, for example, to store the account number after the account is successfully opened.

Through the system in this embodiment, when performing three-tier task distribution, the task list that needs to be processed can be broadcast to all application servers, and the application server that receives the task list only processes the tasks created by itself, and discards other tasks, thereby ensuring logic Consistency to ensure the success rate of task processing.

In the second aspect, based on the same inventive concept, the embodiment of this specification provides a task processing method, which is applied to a task processing system. The task processing system includes a task processing device and multiple application servers. Please refer to FIG. 8, the task The processing method includes the following steps:

S801: The task processing device acquires task information of a task to be processed, and based on a user identifier in the task information, distributes the task information to a first application server corresponding to the user identifier, wherein the second An application server belongs to the plurality of application servers, and the task information includes the server identifier of the second application server that creates the task to be processed and the user identifier corresponding to the task to be processed, and the second application server sets There is a processing module for processing said pending tasks;

S802: The first application server receives the task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to the multiple application servers, and the list of tasks to be processed carries have said server ID;

S803: Each application server in the plurality of application servers receives the list of tasks to be processed, and after confirming that the server ID in the list of tasks to be processed is consistent with its own server ID, executes the task list to be processed to process.

In an optional manner, the task processing system further includes a dispatch center, and the method further includes:

The dispatching center periodically triggers asynchronous tasks, and notifies the task processing device to process the pending tasks in the preset task list, so that the task processing device obtains the task information of the pending tasks from the preset task list .

In an optional manner, the task processing system further includes a communication device, and before the task processing device acquires task information of tasks to be processed, the method further includes:

The communication device receives the service request sent by the user terminal, and notifies the second application server corresponding to the service request to create a pending task corresponding to the service request;

The second application server creates a task to be processed corresponding to the service request, and adds the server identifier to task information of the task to be processed.

In an optional manner, the dispatching center periodically triggering the asynchronous task includes: the dispatching center periodically triggering the asynchronous task according to a configured CRON expression.

In an optional manner, the task processing device distributes the task information to the first application server corresponding to the user identifier based on the user identifier in the task information, including:

The task processing device splits the task information according to the numerical range of the user identifier, and distributes the split task information to the corresponding first application server.

In an optional manner, the first application server receives the task information, and generates a pending task list based on the task information, including:

The first application server reads the pending tasks from the database indicated by the task information, and generates a list of pending tasks based on the read pending tasks.

In an optional manner, the first application server broadcasts the pending task list to the multiple application servers, including:

The first application server determines the current environment, judges whether the current environment is an offline development environment, and if so, broadcasts the pending task list to the plurality of application servers.

In an optional manner, after the first application server determines whether the current environment is an offline development environment, the method further includes:

If the first application server determines that the current environment is not an offline development environment, it randomly distributes the read tasks to be processed to the plurality of application servers.

In an optional manner, the task to be processed is an account opening task.

The detailed process of task processing in this embodiment has been described in detail in the above-mentioned embodiment of the first aspect. For details, reference may be made to the corresponding content in the embodiment of the first aspect, which will not be repeated in this application.

In the second aspect, based on the same inventive concept, the embodiment of this specification provides a task processing method, please refer to FIG. 8, including the following steps:

S801: Receive the task information of the task to be processed sent by the dispatching center, each task information includes creating a server ID corresponding to the task to be processed;

S802: Based on the user identifier in each task information, distribute the task information to multiple application servers;

S803: Control each application server in the plurality of application servers to read the corresponding task to be processed according to the second preset strategy based on the assigned task information, generate a list of tasks to be processed, and broadcast the list of tasks to be processed to all application servers;

S804: Control each of the application servers to process pending tasks in the list of pending tasks that are consistent with their own server identifiers.

In an optional manner, the distributing the task information to multiple application servers based on the user identifier in each task information includes:

Splitting the task information according to the numerical range of the user identifier;

Distribute the split task information to corresponding application servers.

In an optional manner, the controlling each application server in the plurality of application servers to read the corresponding task to be processed according to the second preset strategy based on the assigned task information includes:

Controlling each of the plurality of application servers to read a preset number of tasks to be processed from a database indicated by the allocated task information.

In an optional manner, the broadcasting the pending task list to all application servers includes:

determine the current environment;

Judging whether the current environment is an offline development environment;

If yes, broadcast the pending task list to all application servers.

In an optional manner, after the judging whether the current environment is an offline development environment, the method further includes:

If the current environment is not an offline development environment, each application server in the multiple application servers randomly distributes the read tasks to be processed to multiple application servers.

In an optional manner, the task to be processed is an account opening task, and the account opening task is stored in a preset task table, and the dispatch center periodically triggers an asynchronous task to extract the account opening task in the preset task table Task information in the task.

The detailed process of task processing in this embodiment has been described in detail in the above-mentioned embodiment of the first aspect. For details, reference may be made to the corresponding content in the embodiment of the first aspect, which will not be repeated in this application.

In the third aspect, based on the same inventive concept, the embodiment of this specification provides a task processing method, which is applied to an application server, please refer to FIG. 9, including the following steps:

S901: Create a target pending task, and add the server identifier of the application server to the task information of the target pending task;

S902: Receive a to-be-processed task list, where task information of each to-be-processed task is stored;

S903: traverse the task information of each pending task in the pending task list, and determine the target pending task whose server ID in the task information is consistent with the server ID of the application server;

S904: Process the target pending task.

Specifically, as described in the aforementioned first embodiment, the application server needs to add the server identifier of the application server to the task of the target pending task after receiving the assigned service request after creating the target pending task In the information, it indicates that the target pending task is created for itself. The target to-be-processed task will be distributed to a first application server for task retrieval. When the task retrieved by the first application server includes the target to-be-processed task, a pending task list is generated, and the pending task list carries Once the task information of the target pending task is obtained, the task information includes the server identifier of the application server that created the target pending task, and the first application server will broadcast the list of pending tasks to all application servers. Furthermore, after the current application server receives the pending task list containing the target pending task, it can extract the task information of each pending task in the task list to match the target pending task consistent with its own server ID, Process pending tasks for this target. Discard other tasks that are not created by yourself, so as to ensure the consistency of logic and the success rate of task processing.

Further, if the application server in this embodiment is selected as the first server for task retrieval, it will receive task information distributed by the task processing device, and generate a pending task list based on the task information. Specifically, a preset number of pending tasks can be retrieved from the database indicated by the task information to generate a list of pending tasks. Each pending task in the list of pending tasks carries task information, and the task information includes information about creating the task. The server ID of the application server. Then, the application server will broadcast the pending task list to all application servers in the whole network, and each application server can process the pending tasks in the pending task list that are consistent with its own server ID, and discard the pending tasks that are inconsistent with its own server ID. Handle tasks.

In the fourth aspect, based on the same inventive concept, the embodiment of this specification provides an application server, please refer to FIG. 10 , which includes the following units:

The creating unit 1001 is configured to create a target pending task, and add the server identifier of the application server to the task information of the target pending task;

The receiving unit 1002 is configured to receive a list of tasks to be processed, and task information of each task to be processed is stored in the list of tasks to be processed;

A determining unit 1003, configured to traverse the task information of each pending task in the pending task list, and determine the target pending task whose server identifier in the task information is consistent with the server identifier of the application server;

The processing unit 1004 is configured to process the target pending task.

The detailed process of task processing performed by the application server in this embodiment has been introduced in detail in the aforementioned embodiment of the third aspect, and will not be repeated in this application.

In the fifth aspect, based on the same inventive concept as the task processing method in the foregoing embodiments, the present invention also provides a task processing device, as shown in FIG. A computer program running on the processor 1102, when the processor 1102 executes the program, implements the steps of any one of the aforementioned task processing methods.

Wherein, in FIG. 11, the bus architecture (represented by bus 1100), bus 1100 may include any number of interconnected buses and bridges, and bus 1100 will include one or more processors represented by processor 1102 and memory 1104 represented The various circuits of the memory are linked together. The bus 1100 can also link together various other circuits such as peripheral devices, voltage regulators and power management circuits, etc., which are well known in the art, therefore, the method in this embodiment will not discuss them described further. The bus interface 1106 provides an interface between the bus 1100 and the receiver 1101 and the transmitter 1103 . Receiver 1101 and transmitter 1103 may be the same element, a transceiver, providing means for communicating with various other devices over a transmission medium. Processor 1102 is responsible for managing bus 1100 and general processing, while memory 1104 may be used to store data used by processor 1102 in performing operations.

In the sixth aspect, based on the inventive concept of the task processing method in the foregoing embodiments, the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, any of the above task processing methods can be implemented. the steps of a method.

The specification is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the specification. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a A device for realizing the functions specified in one or more steps of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

While the preferred embodiments of the present specification have been described, additional changes and modifications can be made to these embodiments by those skilled in the art once the basic inventive concept is appreciated. Therefore, it is intended that the appended claims be interpreted to cover the preferred embodiment as well as all changes and modifications that fall within the scope of this specification.

Obviously, those skilled in the art can make various changes and modifications to this description without departing from the spirit and scope of this description. In this way, if these modifications and variations of this specification fall within the scope of the claims of this specification and their equivalent technologies, this specification also intends to include these modifications and variations.

Claims (22)

1. A task processing method, applied in a task processing system, said task processing system comprising a task processing device and a plurality of application servers, said task processing method comprising: The task processing device acquires task information of a task to be processed, and distributes the task information to a first application server corresponding to the user identifier based on a user identifier in the task information, wherein the first application The server belongs to the plurality of application servers, and the task information includes the server identifier of the second application server that creates the task to be processed and the user identifier corresponding to the task to be processed, and the second application server is configured with a a processing module for processing the task to be processed; The first application server receives the task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to the multiple application servers, and the list of tasks to be processed carries all the server ID; Each application server in the multiple application servers receives the pending task list, and processes the pending task after confirming that the server ID in the pending task list is consistent with its own server ID ; The second application server only processes tasks created by itself and discards other tasks. 2. The method according to claim 1, the task processing system further comprising a dispatch center, the method further comprising: The dispatching center periodically triggers asynchronous tasks, and notifies the task processing device to process the pending tasks in the preset task list, so that the task processing device obtains the task information of the pending tasks from the preset task list . 3. The method according to claim 2, wherein the task processing system further comprises a communication device, and before the task processing device acquires task information of tasks to be processed, the method further comprises: The communication device receives the service request sent by the user terminal, and notifies the second application server corresponding to the service request to create a pending task corresponding to the service request; The second application server creates a task to be processed corresponding to the service request, and adds the server identifier to task information of the task to be processed. 4. The method according to claim 2, wherein the dispatching center periodically triggers the asynchronous task, comprising: the dispatching center periodically triggering the asynchronous task according to a configured CRON expression. 5. The method according to claim 1, wherein the task processing device distributes the task information to the first application server corresponding to the user identifier based on the user identifier in the task information, comprising: The task processing device splits the task information according to the numerical range of the user identifier, and distributes the split task information to the corresponding first application server. 6. The method according to claim 1, wherein the first application server receives the task information, and generates a pending task list based on the task information, comprising: The first application server reads the pending tasks from the database indicated by the task information, and generates a list of pending tasks based on the read pending tasks. 7. The method according to claim 1, wherein the first application server broadcasts the pending task list to the plurality of application servers, comprising: The first application server determines the current environment, judges whether the current environment is an offline development environment, and if so, broadcasts the pending task list to the plurality of application servers. 8. The method according to claim 7, after the first application server determines whether the current environment is an offline development environment, the method further comprises: If the first application server determines that the current environment is not an offline development environment, it randomly distributes the read tasks to be processed to the plurality of application servers. 9. The method according to any one of claims 1-8, wherein the task to be processed is an account opening task. 10. A task processing system, comprising a task processing device and a plurality of application servers, wherein: The task processing device is configured to acquire task information of a task to be processed, and distribute the task information to a first application server corresponding to the user identifier based on a user identifier in the task information, wherein the second An application server belongs to the plurality of application servers, and the task information includes the server identifier of the second application server that creates the task to be processed and the user identifier corresponding to the task to be processed, and the second application server sets There is a processing module for processing said pending tasks; The first application server receives the task information, generates a list of tasks to be processed based on the task information, and broadcasts the list of tasks to be processed to the multiple application servers, and the list of tasks to be processed carries all the server ID; Each application server in the multiple application servers receives the pending task list, and processes the pending task after confirming that the server ID in the pending task list is consistent with its own server ID ; Make the second application server only process the tasks created by itself, and discard other tasks. 11. The system according to claim 10, the task processing system further comprising a scheduling center, the scheduling center is used to periodically trigger asynchronous tasks, and notify the task processing device to process pending tasks in a preset task list , so that the task processing device acquires task information of tasks to be processed from the preset task list. 12. The system according to claim 11, the task processing system further comprising a communication device, the communication device is configured to receive a service request sent by a user terminal before the task processing device acquires task information of a task to be processed, And notify the second application server corresponding to the service request to create a pending task corresponding to the service request. 13. The system according to claim 12, after receiving the notification from the communication device, the second application server creates a pending task corresponding to the service request, and adds the server identifier to the pending task. In the task information of the task. 14. The system according to claim 11, wherein the scheduling center is configured to periodically trigger the asynchronous task according to a configured CRON expression. 15. The system according to claim 10, wherein the task processing device splits the task information according to the numerical range of the user identifier, and distributes the split task information to the corresponding first application server. 16. The system according to claim 10, wherein the first application server reads the to-be-processed tasks from the database indicated by the task information, and generates a list of to-be-processed tasks based on the read to-be-processed tasks. 17. The system according to claim 10, the first application server determines the current environment, judges whether the current environment is an offline development environment, and if so, broadcasts the pending task list to the multiple applications server. 18. The system according to claim 17, after the first application server determines whether the current environment is an offline development environment after determining whether the current environment is an offline development environment, it will read the The tasks to be processed are randomly distributed to the multiple application servers. 19. A task processing method applied to an application server, the method comprising: Create a target to-be-processed task, and add the server identifier of the application server to the task information of the target to-be-processed task; receiving a pending task list, the task information of each pending task is stored in the pending task list; Traverse the task information of each pending task in the pending task list, and determine the target pending task whose server identifier in the task information is consistent with the server identifier of the application server; Processing the target pending task; The application server only processes tasks created by itself and discards other tasks. 20. An application server comprising: A creating unit, configured to create a target pending task, and add the server identifier of the application server to the task information of the target pending task; a receiving unit, configured to receive a list of tasks to be processed, wherein task information of each task to be processed is stored in the list of tasks to be processed; A determining unit, configured to traverse the task information of each pending task in the pending task list, and determine the target pending task whose server identifier in the task information is consistent with the server identifier of the application server; a processing unit, configured to process the target pending task; The application server only processes tasks created by itself and discards other tasks. 21. An application server comprising a processor and memory: The memory is used to store a program for executing the method of claim 19; The processor is configured to execute programs stored in the memory. 22. A computer-readable storage medium storing a computer program, characterized in that, when the program is executed by a processor, the steps of the method according to claim 19 are implemented.