CN113723061A

CN113723061A - Data processing method and device based on multi-person collaboration framework

Info

Publication number: CN113723061A
Application number: CN202111007719.4A
Authority: CN
Inventors: 杨旭东; 牛福振; 何天玉; 鄢彪
Original assignee: Shanghai Hode Information Technology Co Ltd
Current assignee: Shanghai Hode Information Technology Co Ltd
Priority date: 2021-08-30
Filing date: 2021-08-30
Publication date: 2021-11-30

Abstract

The application provides a data processing method and device based on a multi-person collaboration framework, which are applied to a main node, wherein the data processing method based on the multi-person collaboration framework comprises the following steps: forwarding the received target service request to a target child node, and determining a request response state of the target service request; under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database; obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data; continuing to perform the step of forwarding the retry target request to the target child node. According to the method and the device, the target request data of the target service request which fails to be processed are stored in the cache database, and the retry target request is generated, so that the probability of successful request response is improved, and the user experience is improved.

Description

Data processing method and device based on multi-person collaboration framework

Technical Field

The application relates to the technical field of internet, in particular to a data processing method based on a multi-person collaboration framework. The application also relates to a data processing device based on the multi-person collaboration framework, a computing device and a computer readable storage medium.

Background

With the continuous development of internet technology, wiki is used as a hypertext system for multi-person collaborative creation, and is convenient for realizing knowledge information sharing. People can optionally choose to edit or add content anonymously or by real name. The Wiki system is a hypertext system, people can browse, create and modify Wiki texts on the basis of Web, and the creation, modification and release costs of the Wiki texts are far less than that of HTML texts; when the wiki framework receives more requests for editing information, adding information and the like, the problem of request failure is easy to occur, and at the moment, the user is prompted to retry, so that the user experience is seriously influenced.

Therefore, how to improve the success rate of wiki framework request message processing becomes a problem to be solved urgently by technical personnel at present.

Disclosure of Invention

In view of this, the embodiment of the present application provides a data processing method based on a multi-user collaboration framework. The application also relates to a data processing device based on the multi-user collaboration framework, a computing device and a computer readable storage medium, which are used for solving the technical problems that the plug-in of the wiki framework in the prior art has poor stability in responding to the request and lacks a request retry mechanism.

According to a first aspect of the embodiments of the present application, there is provided a data processing method based on a multi-user collaboration framework, applied to a master node, including:

forwarding the received target service request to a target child node, and determining a request response state of the target service request;

under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database;

obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data;

continuing to perform the step of forwarding the retry target request to the target child node.

According to a second aspect of the embodiments of the present application, there is provided a data processing apparatus based on a multi-person collaboration framework, including:

the determining module is configured to forward the received target service request to a target child node and determine a request response state of the target service request;

the adding module is configured to add target request data of the target service request to a cache database under the condition that the request response state is a failure state;

the generating module is configured to obtain the target request data in the cache database based on a preset time period, and generate a retry target request corresponding to the target request data;

an execution module configured to continue to perform the step of forwarding the retry target request to the target child node.

According to a third aspect of embodiments of the present application, there is provided a computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, the processor implementing the steps of the multi-person collaboration framework based data processing method when executing the computer instructions.

According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the data processing method based on a multi-person collaboration framework.

The data processing method based on the multi-user collaboration framework provided by the application forwards the received target service request to a target child node, and determines the request response state of the target service request; under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database; obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data; continuing to perform the step of forwarding the retry target request to the target child node. According to the method and the device, the target service request data of the target service request which is not successfully responded are stored in the cache database, and the retry target request is generated based on the target service request data in the cache database, so that the retry target request is responded, the automatic retry processing of the failed target service request is realized, the user is prevented from inputting the request by himself to retry, and the user experience is improved.

Drawings

Fig. 1 is a flowchart of a data processing method based on a multi-user collaboration framework according to an embodiment of the present application;

FIG. 2a is a flowchart illustrating a data processing method based on a multi-user collaboration framework for image processing requests according to an embodiment of the present disclosure;

fig. 2b is a flowchart illustrating a data processing method based on a multi-user collaboration framework for picture processing request according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a data processing apparatus based on a multi-user collaboration framework according to an embodiment of the present application;

fig. 4 is a block diagram of a computing device according to an embodiment of the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.

The terminology used in the one or more embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the present application. As used in one or more embodiments of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present application refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments of the present application to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first aspect may be termed a second aspect, and, similarly, a second aspect may be termed a first aspect, without departing from the scope of one or more embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

First, the noun terms to which one or more embodiments of the present application relate are explained.

Wiki: the hypertext system is open on the network and can be collaboratively created by multiple people, is developed by Woder Canning Ann in 1995, supports community-oriented collaborative writing, and also comprises a group of supporting the writing. MediaWiki is a free open source wiki suite originally created for Wikipedia, written in the PHP language. Now, all wiki projects governed by the non-profit wiki media Foundation, numerous other wiki websites on the Internet, and MediaWiki Home pages are built on this suite of software

Redis (remote Dictionary Server): the remote dictionary service is an open source log-type and Key-Value database which is written by using ANSI C language, supports network, can be based on memory and can be also persistent, and provides API of multiple languages.

Nginx: is a high performance HTTP and reverse proxy web server.

RequestBody: the method is mainly used for receiving data in json character strings transmitted from the front end to the back end.

The multi-person collaboration framework refers to a framework for multi-person collaborative creation, such as a mediawiki framework, an operation mode of the mediawiki framework is a GUI design mode, which aims to create a framework which is open to global knowledge, open source community shared by human, and applied to Wikipedia of global famous knowledge treasury.

The prior method for processing the technical problems comprises the following steps: for high concurrency, multi-level caches are introduced, and caches such as varnish and redis are added manually, but no message pushing and enriching mechanism is made.

The present application also relates to a data processing apparatus based on a multi-user collaboration framework, a computing device, and a computer readable storage medium, which are described in detail in the following embodiments one by one.

Fig. 1 shows a flowchart of a data processing method based on a multi-user collaboration framework according to an embodiment of the present application, which is applied to a master node, and specifically includes the following steps:

step 102: and forwarding the received target service request to a target child node, and determining the request response state of the target service request.

The target service request refers to a request for a target service, for example, the target service request is to add new text content in a web page, delete player information in a game or process pictures in the web page, and the like. The main node is used for receiving the service request and distributing the service request to the corresponding child node. The target child node refers to a node for responding to the target service request. The request response state refers to a state in which the target child node responds to the target service request.

Specifically, the master node receives the target service request, determines a target child node corresponding to the target service request from the plurality of child nodes based on the target service request, forwards the target service request to the target child node, and determines a response condition of the target child node to the target service request, that is, determines a request response state of the target service request.

In a specific embodiment of the present application, taking a target service request as an example of a request for editing picture information, a received request for editing picture information is forwarded to a target child node corresponding to the request for editing picture information, and a request response state of the request for editing picture information is determined.

In practical application, in order to distribute different service requests to different child nodes for processing and achieve load balancing of the nodes, therefore, the method for forwarding a received target service request to a target child node includes:

receiving a target service request;

determining a target child node corresponding to the target service request in the distributed cluster;

and forwarding the target service request to the target child node.

The distributed cluster refers to a child node set composed of a plurality of child nodes.

Specifically, the master node receives a target service request, determines a sub-node in the sub-node set matched with the target service identifier as a target sub-node according to the target service identifier based on the target service identifier carried by the target service request, and forwards the target service request received by the master node to the target sub-node after determining the target sub-node corresponding to the target service request. Load balancing of the nodes can be achieved by adopting Nginx, and other software with the same load balancing effect can be adopted, so that the method is subject to practical application, and the method is not particularly limited.

In a specific embodiment of the present application, following the above example, a picture editing information request is received, a target child node corresponding to the picture editing information request is determined in a child node set by using Nginx, and the picture editing information request is forwarded to the target child node.

By determining the child nodes corresponding to the requests in the node set, the balanced load of the child nodes is realized, the utilization rate of the child nodes is improved conveniently, and the problem that the failure rate of the requests is increased because a single child node processes too many requests at the same time is solved.

After the target service request is forwarded to the target child node, the response condition of the target child node to the target service request needs to be determined, so that the subsequent further operation on the target service request is determined.

In practical applications, the specific method for determining the request response state of the target service request includes:

acquiring request response information corresponding to the target service request;

determining that the request response state of the target service request is a failure state under the condition that the request response information is abnormal information;

and determining that the request response state of the target service request is a success state under the condition that the request response information is success information.

The request response information refers to information returned by the target child node after receiving the target service request. The request response information contains success information or abnormal information, the success information refers to information obtained after the target sub-node successfully processes the target service request, and the failure information refers to information obtained after the target sub-node fails to process or process the target service request. The successful state is the state that the target child node successfully processes the target service request, and the failed state is the state that the target child node fails to process the target service request.

In a specific embodiment of the present application, taking a target service request as a video information deletion request as an example, request response information corresponding to the video information deletion request is obtained, where the request response information includes information that a child node processing request for processing the video information deletion request is overtime, and then it is determined that a request response state of the video information deletion request is a failure state.

In another embodiment of the present application, following the above example, request response information corresponding to the request for deleting the video information is obtained, and if the request response information includes time information for completing processing of the request for deleting the video information, it is determined that a request response status of the request for deleting the video information is a success status.

In order to improve the success rate of node response, the specific method for reallocating the request after obtaining the abnormal information and allocating the request to other idle nodes, that is, determining that the request response state of the target service request is a failure state under the condition that the request response information is the abnormal information, includes:

under the condition that the request response information is abnormal information, reallocating the target service request;

and under the condition that the redistribution times of the target service request exceed a preset distribution threshold value, determining that the request response state of the target service request is a failure state.

The redistribution may be to distribute the target service request to other child nodes except the target child node in the distributed cluster; the redistribution times refer to the total times of distribution of the target service requests; the preset allocation threshold refers to an upper limit value of the allocable times of the target service request.

In practical application, in the case that a target child node does not normally process a target service request, the target service request may be allocated to other child nodes in the distributed cluster, and a specific allocation rule may be set based on an actual situation, for example, a rule for allocating the target service request to an idle child node, a rule for allocating the target service request to a child node that processes fewer requests, and the like may be set; and under the condition that the child node determined based on the distribution rule does not respond to the target service request, determining the request response state of the target service request as a failure state.

In a specific embodiment of the present application, taking a preset allocation threshold as n as an example, a node 1 is configured to receive and respond to a text deletion request, and when an obtained request response is abnormal information, allocate the text deletion request to child nodes except child node 1 in a child node set { child node 1, child node 2... sub node n }, and process the text deletion request, in this embodiment, a rule that service requests are allocated to child nodes with fewer processing requests is adopted, and child nodes in the child node set are arranged in an ascending order according to a node processing quantity, so as to obtain a first child node in the ascending order, for example, child node 3 is a newly allocated child node of the text deletion request; and under the condition that each child node which is redistributed for the character deleting request acquires the abnormal information, determining that the request response state of the character deleting request is a failure state.

In practical application, after the request response state of the request is a success state or a failure state, the request data needs to be recorded, and the specific method for recording the request data includes:

under the condition that the request response state is a failure state, adding target service data of the target service request to a target service database, and adding a failure identifier for the target service data;

and under the condition that the request response state is a success state, adding the target service data of the target service request to the target service database, and adding a success identifier for the target service data.

The target business data refers to a database for storing the target business data; the successful identification means that the status field in the data status information table of the target service database is marked as successful; the failure identification means that the status field in the data status information table of the target service database is marked as failure.

Specifically, under the condition that the target child node successfully responds to the target service request, the target service data of the target service request is stored in a target service database, and the state field of the target service data is marked as successful; and under the condition that the target child node fails to respond to the target service request, storing the target service data of the target service request into a target service database, and editing the state field of the target service data into failure. That is, the target service data corresponding to the target service request is written into the target service database, and a status field is set, where the status field is set to be successful when the request response is successful, and the status field is set to be failed when the request response is failed.

Step 104: and under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database.

The request response state refers to a response state of the target child node to the target service request, namely the request response state is a success state under the condition that the target child node successfully processes the target service request; and under the condition that the target child node does not successfully respond to the target service request, the request response state is a failure state. The target request data refers to request data contained in the target service request; the cache database refers to a database for storing target request data. In order to further improve the response success rate of the request, the target request data in the target service request which is not successfully responded can be stored in the cache database, so that a retry target request can be generated according to the target service request data in the cache database subsequently, and the retry of the target service request is realized by responding to the retry target request.

In a specific embodiment of the present application, taking the text information addition request as an example, when the request response status of the text information addition request is a failure status, the text information addition request data of the text information addition request is added to the cache database.

In practical application, the specific method for adding the target request data of the target service request to the cache database includes:

acquiring target request data of the target service request;

compressing the target request data to generate a request data compression file corresponding to the target request data;

and adding the request data compression file to the cache database.

The request data compression file refers to a compression file generated by compressing target request data.

In a specific embodiment of the present application, taking a request for deleting picture information as an example, obtaining requestbody information in the request for deleting picture information, obtaining a requested data compression file from the requestbody information through json compression, and storing the requested data compression file into a cache database.

By adding the target request data of the target service request into the cache database, the retry target request is generated and responded conveniently on the basis of the target request data in the cache database, so that the response success rate of the target service request is improved.

Step 106: and acquiring the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data.

The preset time period refers to a preset time period, and can be used for determining when to acquire target request data corresponding to the target service request in the cache database. Retrying the target request refers to a request generated according to the target request data, and is used for enabling the target child node to perform processing again on the target service request.

In a specific embodiment of the present application, taking the example that the cache database includes the audio editing request, the preset time period is one minute, the request data is obtained from the cache database once every one minute, the audio editing request data of the audio editing request is obtained, and an audio editing retry request corresponding to the request data is generated.

And the target child node responds to the retry target request by generating the retry target request again, so that the success rate of response of the target service request is improved.

In practical application, the specific method for obtaining the target request data in the cache database based on a preset time period and generating a retry target request corresponding to the target request data includes:

acquiring target request data in the cache database based on a preset time period;

determining request attribute information corresponding to the target request data;

and generating the retry target request according to the request attribute information and the target request data.

The request attribute information refers to attribute information of the request, wherein the request attribute information may include timestamp information, encryption request information, and the like. And combining the request attribute information with the target request data to obtain a retry target request.

In a specific embodiment of the present application, following the above example, every preset time period, that is, every minute, audio editing request data of an audio editing request is obtained from a buffer database; and adding timestamp information to the audio editing request data and making a request encryption identifier for the audio editing request data to generate an audio editing retry request.

Step 108: continuing to perform the step of forwarding the retry target request to the target child node.

After a retry target request is generated according to target request data of the cache database, the main node receives the retry target request and distributes the retry target request to the target sub-nodes, and the target sub-nodes receive the retry target request and respond to the retry target request, namely, the same operation as the target service request is executed. In a specific embodiment of the present application, a retry target request received by a master node is forwarded to a target child node, and a request response status of the retry target request is determined; under the condition that the request response state is a failure state, target request data of a retry target request is added to a cache database; and acquiring request data in the cache database based on a preset time period, and generating a retry target request again.

In practical applications, the method of continuing to perform the step of forwarding the retry target request to the target child node comprises:

deleting the target request data in the cache database under the condition that the request response state of the retry target request is a success state;

and under the condition that the request response state of the retry target request is a failure state, recording the retry times of the target service request in the target service database.

The retry number of the target service request refers to several retries of the target service request. The process of obtaining target request data in the cache database, generating a retry target request and responding to the retry target request is equivalent to retrying the target service request once. When the request response state of the retry target request is a success state, namely the target service request is processed by the sub-node, the target request data in the cache database can be deleted, namely the node processes the target service request without generating the target retry request again; and under the condition that the request response state of the retry target request is a failure state, namely the target service request is still not processed by the sub-node, recording the repetition times of the target service request.

The storage space in the cache database is released by deleting the target request data of the target service request successfully processed by the node, so that the target request data of other target service requests which are not responded by the node can be conveniently stored; after the retry target request is generated, the retry times of the target service request are recorded, so that whether the target service request is retried again or not is judged based on the request times.

In practical applications, deleting the target request data in the cache database includes:

and deleting the target request data in the cache database under the condition that the retry times of the target service request are greater than a first retry threshold value.

The first retry threshold is an upper limit value for retrying the target service request. And under the condition that the retry times of the target service request are greater than a preset first retry threshold, considering that the request failure rate of the target service request is higher, not retrying the target service request any more, and deleting the target request data of the target service data in the cache database.

By setting the upper limit value of the request times, the target service request with high failure rate is not retried any more, excessive occupation of the retry resources is avoided, and the efficiency of service retry is improved.

In practical application, a situation that the request data is not scanned in the cache database may occur, and in order to ensure a retry success rate at this time, the request data with a status field in a failure state may also be acquired in the database for generating a corresponding retry target request, where the specific method includes:

under the condition that target request data in the cache database is not acquired within a preset time period, acquiring service data to be retried carrying a failure identifier from the target service database;

and generating a retry target request corresponding to the to-be-retried service data.

The service data to be retried refers to target request data of a target service request acquired from a target service database. A retry target request corresponding to the target traffic request may be generated based on the traffic data to be retried.

Under the condition that the target service data is not scanned in the cache database, the service data to be retried, namely the service data with the failed status field and less repetition times, is acquired in the target service database, and the retry target request is generated for retrying, so that the successful push of the request is ensured to the maximum extent.

In practical application, a target service database may contain a plurality of pieces of request data carrying a failure identifier, and therefore service data to be retried needs to be determined from the plurality of pieces of request data, and specifically, the method for acquiring the service data to be retried from the target service database, which carries the failure identifier, includes:

acquiring at least one initial service data carrying a failure identifier from the target service database, and determining the retry times corresponding to each initial service data;

and taking the initial service data with the retry times smaller than the second retry threshold as the service data to be retried.

The initial service data refers to the service data which is determined in the target service database and carries the failure identifier. The second retry threshold refers to a preset minimum retry number of the target service request.

In a specific embodiment of the present application, taking 4 times as an example of the second retry threshold, the initial service data { service data 1, service data 2.. service data n } carrying the failure identifier is obtained from the target service database, where the retry number of the service request corresponding to the service data 3 is 2, which is smaller than the preset retry number 4, and the service data 3 is used as the service data to be retried.

In practical application, the retry times of the initial service data can be arranged in an ascending order, and the initial service data which is ranked in the ascending order and is in the front is selected as the service data to be retried; or performing descending order arrangement on the retry times of the initial service data, selecting the initial service data after the sorting as the service data to be retried, and the like, wherein the selected number can be set according to the actual application condition, and is not limited in the application. Namely, the service data with less repetition times in the initial service data is obtained, and the retry target request is generated, so that the success rate of the response of the target service request is improved.

And under the condition that the request data is not scanned in the cache database, determining initial service data with the retry times lower than a second retry threshold value from the target service database as service data to be retried.

The wiki framework cannot monitor the service flow because the wiki framework does not monitor similar plug-ins, and only can monitor data through third-party monitoring software, and the monitoring of the third-party monitoring software can only be accurate to a domain name or an interface, cannot specify a specified service, and does not have functions of alarming the data with problems and the like. The scheme of the application realizes the monitoring of the service data by embedding the service, can set the service threshold value, and alarms the abnormal service data when the monitored service data exceeds the service threshold value.

Based on this, after the child node successfully processes the target service request, the service data returned to the client by the child node response request can be monitored, and the specific monitoring method comprises the following steps:

determining a target service corresponding to the target service request under the condition that the request response state is a success state;

acquiring service data information of the target service based on preset data buried point information corresponding to the target service;

and counting the service data information to generate a service monitoring result of the target service.

The target service refers to a service corresponding to the target service request, and if the target service request is to delete the game login information, the target service may be a game service. The preset data embedded point information refers to embedded point information set for monitoring the target service. The service data information of the target service refers to information obtained in the target service based on preset data buried point information. The service monitoring result refers to data information of the monitoring target service which is used for returning to the client after the service data information determined according to the buried point information is collected.

In practical application, the method for determining the target service corresponding to the target service request includes:

acquiring a target service identifier of the target service request;

and under the condition that the service configuration information matched with the target service identifier is retrieved from a service configuration information table, determining that the service corresponding to the target service identifier is the target service.

The target service identifier is an identifier for indicating a target service, and if the target service request is a request for deleting a game page picture, the target service identifier may be a game. The service configuration information refers to configuration information for configuring monitoring of a service. The service configuration information table is a data table containing service monitoring configuration information corresponding to a service.

Specifically, a target service identifier included in the target service request is obtained, and service configuration information corresponding to the target service identifier is retrieved from a service configuration information table based on the target service identifier; if the service configuration information corresponding to the target service identifier is not retrieved, determining that the target service is not monitored, namely the target service does not need to be monitored at the moment; when the target service needs to be monitored, adding the service configuration information of the target service into a service configuration information table; and if the service configuration information corresponding to the target service identifier is retrieved, taking the service corresponding to the target service identifier as the target service, and taking the service configuration information corresponding to the target service identifier in the service configuration information table as monitoring configuration information for monitoring the target service.

In practical application, the method for determining the preset data buried point information corresponding to the target service comprises the following steps:

acquiring service configuration information corresponding to the target service;

and determining preset data buried point information corresponding to the target service according to the service configuration information.

Specifically, the service configuration information corresponding to the target service is determined in the service configuration information table, the preset data point burying information for monitoring the target service is determined according to the service configuration information, for example, the preset data point burying information for the request is determined according to the service configuration information for processing the text information request in the game webpage, and the preset data point burying information for the request includes monitoring the number of times of adding text to the game webpage, the number of times of deleting text, and the like.

In practical application, after the business data information is counted, the business data information can be further judged to determine whether the information has an abnormal request, and the specific method comprises the following steps:

acquiring a preset service threshold corresponding to the service data information;

and sending an alarm prompt under the condition that the service data information is greater than the preset service threshold.

The preset service threshold may be a value that the service data can reach under a normal condition, or an upper limit value of a value in the service data preset according to an actual use condition.

In a specific embodiment of the present application, taking a preset service threshold as an example, that the number of times of password input is 3, obtaining service data information of a monitoring password input request: the user enters the password 4 times. And sending a mail alarm to the client under the condition that 4 times of passwords are input into the monitored service data information and the number of password input times greater than the preset service threshold is 3 times, namely prompting that the number of password input times reaches the upper limit and the passwords cannot be input continuously.

The service data are monitored, and the monitored service data information is counted, so that the real-time data information can be fed back conveniently; the alarm prompt is carried out on the data information exceeding the preset service threshold value, so that the problem in the service data can be quickly determined, and the problem can be timely processed.

The data processing method based on the multi-user collaboration framework forwards the received target service request to a target child node, and determines the request response state of the target service request; under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database; obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data; continuing to perform the step of forwarding the retry target request to the target child node. According to the data processing method based on the multi-user collaboration framework, firstly, target request data of a target service request which fails to be processed are stored in a cache, a retry target request is generated and responded, the target service request which fails to be responded is automatically retried, the retry of the failure request when a user inputs the request by himself is avoided, and the user experience is improved; the target service request which fails to respond is redistributed, so that the success rate of request response is improved; the main node distributes the target service request to the target child node, so that the balanced load of the nodes is realized, and the possible operation jam caused by large concurrency is avoided.

Secondly, monitoring specific services by embedding points in service data, classifying the services based on the service data, and counting the service data of the specified services; and setting service threshold values for different services, and sending an alarm when the monitored service data information exceeds the threshold values, so that the abnormal condition of related personnel can be conveniently and timely notified, and the stable operation of the server can be ensured.

The following describes the data processing method based on the multi-person collaboration framework further by taking an application of the data processing method based on the multi-person collaboration framework provided by the present application to a picture processing request as an example with reference to fig. 2a and fig. 2 b. Fig. 2a shows a processing flow chart of a data processing method based on a multi-person collaboration framework applied to a picture processing request according to an embodiment of the present application, and fig. 2b shows a flow chart of the data processing method based on the multi-person collaboration framework applied to the picture processing request according to an embodiment of the present application, which specifically includes the following steps:

step 202: and forwarding the received target service request to a target child node, and acquiring request response information corresponding to the target service request.

In a specific embodiment of the present application, taking a picture processing request as an example, a client sends the picture processing request to a master node, and the master node performs load balancing through nginn, forwards the received picture processing request to a child node a corresponding to the request, and obtains request response information corresponding to the picture processing request.

Step 204: and under the condition that the request response information is abnormal information, determining that the request response state of the target service request is a failure state.

Specifically, when the request response information is abnormal information, the target service request may be redistributed, and when the redistribution times exceed the preset distribution times and the node still does not respond, the request response state of the target service request is determined to be a failure state; and under the condition that the request response information is success information, determining that the request response state of the target service request is a success state.

In a specific embodiment of the present application, along with the above example, if the request response information corresponding to the picture processing request includes information that the processing of the picture processing request by the child node a is overtime, the picture processing request is redistributed; and if the redistributed child nodes do not successfully respond to the picture processing request and the times of redistributing the picture processing request reach the preset distribution times, determining that the request response state of the picture processing request is a failure state.

Step 206: and under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database, adding target service data of the target service request to a target service database, and adding a failure identifier for the target service data.

In a specific embodiment of the present application, following the above example, it is determined that the request response status of the picture processing request is a failure status, and request _ body information of the picture processing request, that is, picture processing request data, is added to the cache database; and adding the picture processing service data of the picture processing request into a picture processing database, and adding a failure identifier for the picture processing service data in the picture processing database.

Step 208: and acquiring the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data.

Specifically, whether target request data is contained in a redis cache database is judged; under the condition that the redis cache database contains target request data, adding timestamp information for the target request data, encrypting the data, and obtaining a retry target request; under the condition that the target request data is not contained in the redis cache database, reading the service data carrying the failure identification in the target service database, under the condition that the service data carrying the failure identification is read in the target service database, generating a request capable of retrying according to the service data, and under the condition that the service data carrying the failure identification is not read in the target service database, completing the process of acquiring the service data in the cache database in the period.

In a specific embodiment of the present application, following the above example, the preset time period is 1 minute, the picture processing request data corresponding to the picture processing request is obtained from the cache database every other minute, the timestamp information and the encryption information of the picture processing retry request are created according to the picture processing request data in the cache database, and the picture processing retry request is generated from the picture processing request data, the timestamp information and the encryption information.

Step 210: continuing to perform the step of forwarding the retry target request to the target child node.

Specifically, executing the generated retry target request; in case that the retry target request is successfully responded, the target service request is successfully responded; and under the condition that the retry target request is not successfully responded, judging whether the retry times of the target service request reach an upper limit value or not, if the retry times do not reach the upper limit value, recording the retry times of the target service request, and if the retry times reach the upper limit value, no longer storing the target request data of the target service request into a redis cache database.

In one embodiment of the present application, the above example is used to respond to a picture processing retry request and determine a request response status of the picture processing retry request.

Step 212: and deleting the target request data in the cache database under the condition that the request response state of the retry target request is a success state.

Specifically, under the condition that the request response state of the retry target request is a success state, the target request data of the target request is not stored in the cache database any more; and under the condition that the request response state of the retry target request is a failure state, reserving the target request data in the cache database for the next request retry.

In a specific embodiment of the present application, following the above example, the node successfully responds to the retry request of picture processing, and deletes the data of the picture processing request in the cache database.

Step 214: and determining the target service corresponding to the target service request.

Specifically, after the target service request is successfully responded, the target service can be monitored, and whether the specific service data has abnormal conditions or not is monitored.

In a specific embodiment of the present application, the picture processing service corresponding to the picture processing request is determined along with the above example.

Step 216: and acquiring the service data information of the target service based on the preset data buried point information corresponding to the target service.

In a specific embodiment of the present application, following the above example, it is determined according to the monitoring configuration information corresponding to the picture processing service, that is, which data in the picture processing service is monitored, where the embedded point information includes: detecting the editing times, deleting times and the like of the pictures; and determining the service data information of the picture processing service based on the monitoring of the picture processing service, wherein the service data information comprises 5 times of picture deletion, 3 times of picture editing and the like.

Step 218: and counting the service data information to generate a service monitoring result of the target service.

In a specific embodiment of the present application, the above example is continued, the picture processing service data information of the monitored picture processing request is counted, and the data information is counted based on the type of the picture processing service data, including the number of times of deleting a picture is 5, the number of times of editing a picture is 3, and the like; and generating a line graph at the client based on the image processing service data information for the user to check.

Step 220: acquiring a preset service threshold corresponding to the service data information; and sending an alarm prompt under the condition that the service data information is greater than the preset service threshold.

Specifically, comparing the service data information with a preset service threshold value, and judging whether the service data information exceeding the preset service threshold value exists; if yes, sending an email alarm or alarm information in other forms to the client, and feeding back the monitored service data information to the client; if the information does not exist, the service data information is directly fed back to the client, for example, the service data information is rendered to obtain an information line graph for a user to check.

In a specific embodiment of the present application, following the above example, the preset service threshold is determined as 3 times of the upper limit value of the picture editing times, the picture processing service data information includes 4 times of the picture editing times, and at this time, an alarm mail indicating that the picture editing times exceeds the threshold is sent to the client.

According to the data processing method based on the multi-user collaboration framework, the main node forwards the picture processing request to the sub-node A corresponding to the picture processing request, so that balanced load of the nodes is achieved, and operation blockage possibly caused by large concurrency is avoided; determining a request response state of the picture processing request; the picture processing requests which fail to respond are redistributed, so that the success rate of the response of the picture processing requests is improved; under the condition that the request response state is a failure state, adding the picture processing request data of the picture processing request to a cache database; acquiring the picture processing request data in the cache database based on a preset time period of 1 minute, and generating a picture processing retry request corresponding to the picture processing request; the step of responding the picture processing retry request is continuously executed, and a message retry mechanism is set for the wiki framework, so that the user is prevented from inputting the request by himself to retry the request, the picture processing retry request which fails to respond is automatically retried, and the user experience is improved;

secondly, embedding points in the service data of the picture processing request to realize monitoring specific services; by setting a service threshold, under the condition that the monitored service data exceeds the threshold, an alarm is sent out, so that related personnel can repair the abnormality in time, and the stable operation of the server is ensured.

Corresponding to the above method embodiment, the present application further provides an embodiment of a data processing apparatus based on a multi-user collaboration framework, and fig. 3 illustrates a schematic structural diagram of the data processing apparatus based on the multi-user collaboration framework according to an embodiment of the present application. As shown in fig. 3, the apparatus includes:

a determining module 302 configured to forward the received target service request to a target child node, and determine a request response status of the target service request;

an adding module 304, configured to add target request data of the target service request to a cache database if the request response status is a failure status;

a generating module 306, configured to obtain the target request data in the cache database based on a preset time period, and generate a retry target request corresponding to the target request data;

an execution module 308 configured to continue to perform the step of forwarding the retry target request to the target child node.

The determining module 302, further configured to:

The apparatus further comprises an identity addition module configured to:

The adding module 304, further configured to:

acquiring target request data of the target service request;

and adding the request data compression file to the cache database.

The generating module 306, further configured to:

The execution module 308, further configured to:

The apparatus also includes a monitoring module configured to:

The monitoring module further configured to:

acquiring a target service identifier of the target service request;

The monitoring module further configured to:

The apparatus also includes an alert module configured to:

The determining module 302, further configured to:

receiving a target service request;

and forwarding the target service request to the target child node.

The data processing device based on the multi-user collaboration framework forwards the received target service request to a target child node, and determines a request response state of the target service request; under the condition that the request response state is a failure state, adding target request data of the target service request to a cache database; obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data; continuing to perform the step of forwarding the retry target request to the target child node. According to the data processing device, the target request data of the target service request which fails to be processed is stored in the cache, the retry target request is generated and responded, the retry of the target service request which fails to be responded is automatically carried out, the retry of the failure request which is automatically input by a user is avoided, and the user experience is improved; the target service request which fails to respond is redistributed, so that the success rate of request response is improved; the main node distributes the target service request to the target child node, so that the balanced load of the nodes is realized, and the possible operation jam caused by large concurrency is avoided. Secondly, monitoring specific services by embedding points in service data, classifying the services based on the service data, and counting the service data of the specified services; and setting service threshold values for different services, and sending an alarm when the monitored service data information exceeds the threshold values, so that the abnormal condition of related personnel can be conveniently and timely notified, and the stable operation of the server can be ensured.

The foregoing is an illustrative solution of the data processing apparatus based on the multi-user collaboration framework of the present embodiment. It should be noted that the technical solution of the data processing apparatus based on the multi-person collaboration frame is the same as the technical solution of the data processing method based on the multi-person collaboration frame, and details of the technical solution of the data processing apparatus based on the multi-person collaboration frame, which are not described in detail, can be referred to the description of the technical solution of the data processing method based on the multi-person collaboration frame.

Fig. 4 shows a block diagram of a computing device 400 provided according to an embodiment of the present application. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. Processor 420 is coupled to memory 410 via bus 430 and database 450 is used to store data.

Computing device 400 also includes access device 440, access device 440 enabling computing device 400 to communicate via one or more networks 460. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 440 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the application, the above-described components of computing device 400 and other components not shown in FIG. 4 may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 4 is for purposes of example only and is not limiting as to the scope of the present application. Those skilled in the art may add or replace other components as desired.

Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.

Wherein, the processor 420 realizes the steps of the data processing method based on the multi-person collaboration framework when executing the computer instructions.

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the data processing method based on the multi-person collaboration framework belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the data processing method based on the multi-person collaboration framework.

An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions, and the computer instructions, when executed by a processor, implement the steps of the data processing method based on the multi-person collaboration framework as described above.

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium is the same as that of the data processing method based on the multi-person collaboration framework, and details of the technical solution of the storage medium, which are not described in detail, can be referred to the description of the technical solution of the data processing method based on the multi-person collaboration framework.

The foregoing description of specific embodiments of the present application has been presented. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, etc. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present application disclosed above are intended only to aid in the explanation of the application. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the application and its practical applications, to thereby enable others skilled in the art to best understand and utilize the application. The application is limited only by the claims and their full scope and equivalents.

Claims

1. A data processing method based on a multi-user collaboration framework is applied to a main node and comprises the following steps:

2. The multi-person collaboration framework based data processing method as claimed in claim 1 wherein determining a request response status of the target business request comprises:

3. The data processing method based on multi-person collaboration framework as claimed in claim 2, wherein determining that the request response status of the target service request is a failure status in case that the request response information is abnormal information comprises:

4. The multi-person collaboration framework based data processing method of claim 2, the method further comprising:

5. The multi-person collaboration framework based data processing method as claimed in claim 1, wherein adding target request data of the target service request to a cache database comprises:

acquiring target request data of the target service request;

and adding the request data compression file to the cache database.

6. The data processing method based on multi-user collaboration framework as claimed in claim 1, wherein obtaining the target request data in the cache database based on a preset time period, and generating a retry target request corresponding to the target request data comprises:

7. The multi-person collaboration framework based data processing method as claimed in claim 4 wherein continuing to perform the step of forwarding the retry target request to a target child node comprises:

8. The multi-person collaboration framework based data processing method of claim 7 further comprising:

9. The multi-person collaboration framework based data processing method of claim 8 further comprising:

10. The data processing method based on multi-user collaboration framework as claimed in claim 9, wherein obtaining the service data to be retried carrying the failure flag from the target service database comprises:

11. A multi-person collaboration framework based data processing method as claimed in any one of claims 1 to 10 further comprising:

12. The multi-person collaboration framework based data processing method as claimed in claim 11, wherein determining the target service corresponding to the target service request comprises:

acquiring a target service identifier of the target service request;

13. The data processing method based on multi-user collaboration framework as claimed in claim 12, wherein the preset data embedding point information based on the target service comprises:

14. The data processing method based on multi-person collaboration framework as claimed in claim 11, wherein after counting the service data information to generate the service monitoring result of the target service, further comprising:

15. The multi-person collaboration framework based data processing method according to any of claims 1-10, wherein forwarding the received target service request to a target child node comprises:

receiving a target service request;

and forwarding the target service request to the target child node.

16. A data processing apparatus based on a multi-person collaboration framework, comprising:

17. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1-15 when executing the computer instructions.

18. A computer-readable storage medium storing computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1 to 15.