CN113032410B - Data processing method, device, electronic equipment and computer storage medium - Google Patents
Data processing method, device, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN113032410B CN113032410B CN201911355053.4A CN201911355053A CN113032410B CN 113032410 B CN113032410 B CN 113032410B CN 201911355053 A CN201911355053 A CN 201911355053A CN 113032410 B CN113032410 B CN 113032410B
- Authority
- CN
- China
- Prior art keywords
- data
- distributed consistency
- consistency system
- tenant
- resource consumption
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 25
- 238000012545 processing Methods 0.000 claims abstract description 34
- 238000000034 method Methods 0.000 claims abstract description 28
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 239000000872 buffer Substances 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000013459 approach Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 241000508269 Psidium Species 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 239000011521 glass Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004984 smart glass Substances 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the invention provides a data processing method, a data processing device, electronic equipment and a computer storage medium, and relates to the technical field of data processing. Wherein the method comprises the following steps: when the distributed consistency system is in a busy state based on the quantity of data requests to be processed in the distributed consistency system, estimating resource consumption data of the data requests to be processed in the distributed consistency system; and executing a current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system. The embodiment of the invention can simply and accurately limit the flow of the request of the distributed consistency system, thereby effectively ensuring the service quality of the distributed consistency system.
Description
Technical Field
The embodiment of the application relates to the technical field of data processing, in particular to a data processing method, a data processing device, electronic equipment and a computer storage medium.
Background
Currently, QOS (Quality of Service ) design is basically implemented by limiting the flow, i.e. limiting the speed, and simply understood is a funnel with two open ends, with a large opening on the input side and a small opening on the output side. The output side always outputs at the maximum predictable speed, no matter how large the flow rate is on the input side. As shown in fig. 1A, the server can always meet the requirement of stable service quality on the basis of stable and controllable request amount, no matter how much the pressure of the client is.
Currently, there are two main ways to limit the request, one is precise rate control. The accurate rate control is generally used for pre-configuring the rate of the flow to be controlled on the premise of better estimating the system capacity and the service flow, and the common method is to use a leak Bucket algorithm or TokenBucket algorithm. Such algorithms are widely used in various system speed limits, such as the basic library guava, the web service nmginx, and toolkits in various languages. However, this approach requires more adaptation work, e.g., different network environments, different server models, possibly different processing rates, and different rate configurations. The other is pressure feedback control. This control approach is more useful in scenarios where it is desirable to maximize the use of the capabilities of the backend server, where requests are accepted when the server has further capabilities to handle the request, and otherwise rejected. Because of the different deployment environments of the same servers, there may be a large difference in processing speed of the servers, a common implementation manner of this method is to allocate a buffer to the servers, where the request first enters the buffer to be cached, and then a special processing module of the server obtains the request from the buffer to process. When the processing capacity of the processing module reaches an upper limit, the buffer will be filled with the request, thereby beginning to reject the request. However, this approach requires additional buffers, which can be complex to implement. Therefore, how to simply and accurately limit the current request of the system is a technical problem to be solved currently.
Disclosure of Invention
In view of the above, embodiments of the present invention provide a data processing method, apparatus, electronic device, and computer storage medium, so as to solve the technical problem in the prior art how to simply and accurately limit the current of a request of a system.
According to a first aspect of an embodiment of the present invention, a data processing method is provided. The method comprises the following steps: when the distributed consistency system is in a busy state based on the quantity of data requests to be processed in the distributed consistency system, estimating resource consumption data of the data requests to be processed in the distributed consistency system; and executing a current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system.
According to a second aspect of an embodiment of the present invention, there is provided a data processing apparatus. The device comprises: the estimating module is used for estimating the resource consumption data of the data request to be processed in the distributed consistency system when the distributed consistency system is in a busy state based on the quantity of the data request to be processed in the distributed consistency system; and the first current limiting module is used for executing current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system.
According to a third aspect of an embodiment of the present application, there is provided an electronic apparatus including: one or more processors; a computer readable medium configured to store one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the data processing method as described in the first aspect of the embodiments described above.
According to a fourth aspect of embodiments of the present application, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a data processing method as described in the first aspect of the above embodiments.
According to the technical scheme provided by the embodiment of the application, when the distributed consistency system is in a busy state based on the number of the data requests to be processed in the distributed consistency system, the resource consumption data of the data requests to be processed in the distributed consistency system is estimated; when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, performing a current limiting operation on data requests sent by clients connected with the distributed consistency system, compared with other existing modes, determining whether the distributed consistency system is in a busy state according to the number of data requests to be processed in the distributed consistency system, and estimating the resource consumption data of the data requests to be processed in the distributed consistency system when the distributed consistency system is determined to be in the busy state based on the number of the data requests to be processed in the distributed consistency system; when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, the data request sent by the client connected with the distributed consistency system is subjected to the current limiting operation, so that the request of the distributed consistency system can be simply and accurately limited, and the service quality of the distributed consistency system is effectively ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present invention, and other drawings may be obtained according to these drawings for a person having ordinary skill in the art.
FIG. 1A is a schematic diagram of a prior art current limiting system;
Fig. 1B is a schematic diagram of an application scenario of a data processing scheme according to an embodiment of the present application;
FIG. 1C is a flowchart illustrating a data processing method according to an embodiment of the present application;
FIG. 1D is a diagram illustrating a queue formed by pending data requests according to a first embodiment of the present application;
FIG. 2 is a flow chart showing steps of a data processing method according to a second embodiment of the present application;
FIG. 3 is a schematic diagram of a data processing apparatus according to a third embodiment of the present application;
FIG. 4 is a schematic diagram of a data processing apparatus according to a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device in a fifth embodiment of the present application;
Fig. 6 is a hardware structure of an electronic device in the sixth embodiment of the present application.
Detailed Description
In order to better understand the technical solutions in the embodiments of the present invention, the following description will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the present invention, shall fall within the scope of protection of the embodiments of the present invention.
The implementation of the embodiments of the present invention will be further described below with reference to the accompanying drawings.
The goddess service is a bottom basic module of the flying distributed consistency system, is used as a practical standard of the consistency service in the ali cloud, is widely applied in the ali cloud, supports cloud products with a plurality of weight levels such as ECS, OSS, maxCompute, tableStore, VPC, alimail and the like, and also supports core services such as nail unitization, ant artificial intelligence service platform and the like in a group. The mythology service provides a series of typical distributed consistency services such as distributed locks, service discovery, metadata storage, etc. As shown in fig. 1B, the connection between the client and the server of the mythology service is session-based, and the client needs to create a session with the server, and maintain the lifetime of the session between the client and the server through regular heartbeats. The specific process is that the client end firstly establishes a long connection with the service end of the NvWa service, then establishes a session on the long connection, and the session establishment can send a normal request after completion, and periodically sends a heartbeat renewing session (keeping the session valid), but in the scene of session disconnection, the long connection needs to be re-established and the session needs to be attempted to be renewed. The server may be a distributed consistency system, which is implemented based on a consistency protocol (such as Paxos, raft, etc.). When the consistency protocol is Raft, the system may include a leader node and a plurality of follower nodes. In order to effectively ensure the service quality of the distributed consistency system in a normal scene, a request sent by a client to the distributed consistency system needs to be limited. Currently, there are two main ways to limit the flow of requests, one is precise rate control and the other is pressure feedback control. However, both of these ways of throttling requests are too complex and do not allow for fine or precise throttling of requests. Therefore, the embodiment of the application provides a data processing method which can simply and accurately limit the flow of the request of the distributed consistency system, thereby effectively ensuring the service quality of the distributed consistency system. The method can be applied to ZooKeeper, web service nginx of Apache communities and tool packages of various languages, such as a Guava current limiting tool RATELIMITER. The specific implementation manner of the data processing method provided by the embodiment of the application is as follows:
Referring to fig. 1C, a flowchart of steps of a data processing method according to a first embodiment of the present application is shown.
Specifically, the data processing method of the present embodiment includes the steps of:
In step S101, when it is determined that the distributed consistency system is in a busy state based on the number of data requests to be processed in the distributed consistency system, resource consumption data of the data requests to be processed in the distributed consistency system is estimated.
In this embodiment, the data request to be processed may be a service data request sent by the client to the distributed consistency system. When the number of data requests to be processed in the distributed consistency system reaches a certain number, the distributed consistency system can be determined to be in a busy state. Specifically, if the number of the data requests to be processed is determined to be greater than or equal to a preset number threshold, the distributed consistency system is determined to be in a busy state. The preset number threshold may be set by those skilled in the art according to actual needs, which is not limited in any way in the embodiment of the present application. More specifically, as shown in fig. 1D, it may be considered that, when a data request sent by a client to the distributed consistency system by the tenant a or the tenant B enters the system, a queue of data requests to be processed may be formed, and only the length of the queue needs to be concerned, which means that only a global value needs to be maintained, and one is added when the data request enters the queue, and one is subtracted when the distributed consistency system sends a response to the data request to the client, where the value may reflect the current running state of the distributed consistency system, and if the value is too large, it means that the current system has excessive data requests to be processed, it is required to limit the flow of the data request sent by the client to the distributed consistency system, which is a characteristic that is not possessed by the existing accurate rate control mode, and pure accurate rate control only forces the inflow speed of the data request according to the configured rate, and does not have the busyness of the current distributed consistency system. Further, the resource consumption data may be understood as resource consumption data estimated when the distributed coherence system processes the pending data request. In particular, the resource consumption data may be time resource data, computing resource data, or storage resource data consumed by the distributed coherence system when processing the data request to be processed. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In some optional embodiments, when predicting resource consumption data of the data request to be processed in the distributed consistency system, determining a request type to which the data request to be processed belongs; determining resource consumption weight data corresponding to the data request to be processed based on the request type to which the data request to be processed belongs; and estimating the resource consumption data of the data request to be processed in the distributed consistency system based on the resource consumption weight data corresponding to the data request to be processed. By determining the request type of the data request to be processed and the resource consumption weight data corresponding to the data request to be processed, the resource consumption data of the data request to be processed in the distributed consistency system can be accurately estimated. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In a specific example, the request type to which the data request to be processed belongs may include at least one of: read request, list request, create request, update request, delete request, heartbeat, session create request, session continue request. Wherein the list request may be understood as a request for requesting a list or manifest. Before predicting the resource consumption data of the data request to be processed in the distributed consistency system, the request type and the resource consumption weight data corresponding to each request type can be preconfigured. For example, when the request type is a read request, the resource consumption weight data corresponding to the read request may be 2, when the request type is a list request, the resource consumption weight data corresponding to the list request may be 4, when the request type is a create request, the resource consumption weight data corresponding to the create request may be 3, when the request type is an update request, the resource consumption weight data corresponding to the update request may be 3, when the request type is a delete request, the resource consumption weight data corresponding to the delete request may be 3, when the request type is a heartbeat, the resource consumption weight data corresponding to the heartbeat may be 1, when the request type is a session creation request, the resource consumption weight data corresponding to the session creation request may be 3, and when the request type is a session continuation request, the resource consumption weight data corresponding to the session continuation request may be 1. The resource consumption weight data may be understood as data for measuring resources consumed by the distributed consistency system when processing a request of a request type to which the distributed consistency system belongs, where the resource consumption weight data may be set according to different characteristics of each system. Furthermore, the request types may not be limited to the above request types, and may be extended to other possible request types. When determining the request type to which the data request to be processed belongs, the request type to which the data request to be processed belongs can be determined according to the content of a request header in the data request to be processed or a type field in a request carrier. When the resource consumption weight data corresponding to the data request to be processed is determined, the corresponding relation between the pre-configured request type and the resource consumption weight data can be searched according to the request type of the data request to be processed so as to determine the resource consumption weight data corresponding to the data request to be processed. When the resource consumption data of the data request to be processed in the distributed consistency system is estimated, the resource consumption weight data corresponding to the data request to be processed can be accumulated to obtain the resource consumption data of the data request to be processed in the distributed consistency system. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In a specific example, the number of data requests to be processed in the distributed consistency system cannot completely reflect the busyness of the current system, because the resource consumption of the system caused by different data requests is different, for example, the resource consumption of the system caused by reading one node is different from the resource consumption of the system possibly caused by reading a plurality of nodes, for example, the resource consumption caused by reading the request and the writing request is also different, a resource consumption weight is configured for each request type, a virtual processing counting mode for the data requests is formed, thus, a separate processing count is not required to be set for each request, and global resource consumption data can be set for the distributed consistency system, so long as the resource data consumed by the data requests to be processed in the current system is kept within a reasonable range, the system is considered to be stable and controllable, and once the data requests sent to the system by a client are exceeded, a current limiting operation is required to be executed. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In step S102, when it is determined that the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, a current limiting operation is performed on a data request transmitted from a client connected to the distributed consistency system.
In this embodiment, if the resource consumption data of the data request to be processed in the distributed consistency system is smaller than or equal to the global resource consumption permission data set by the distributed consistency system, it is indicated that the distributed consistency system is stable and controllable, and it is not necessary to perform a current limiting operation on the data request sent by the client to the distributed consistency system. And if the resource consumption data of the data request to be processed in the distributed consistency system is larger than the global resource consumption permission data set by the distributed consistency system, executing the current limiting operation on the data request sent to the distributed consistency system by the client. In particular, the performing of the throttling operation on the data request sent by the client to the distributed consistency system may be achieved by closing the session between the client and the distributed consistency system, or by stopping listening to a long connection creating the session. Wherein, the global resource consumption permission data can be set by a person skilled in the art according to actual needs, and the embodiment of the application is not limited in any way. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
According to the data processing method provided by the embodiment of the application, when the distributed consistency system is in a busy state based on the number of the data requests to be processed in the distributed consistency system, the resource consumption data of the data requests to be processed in the distributed consistency system is estimated; when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, performing a current limiting operation on data requests sent by clients connected with the distributed consistency system, compared with other existing modes, determining whether the distributed consistency system is in a busy state according to the number of data requests to be processed in the distributed consistency system, and estimating the resource consumption data of the data requests to be processed in the distributed consistency system when the distributed consistency system is determined to be in the busy state based on the number of the data requests to be processed in the distributed consistency system; when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, the data request sent by the client connected with the distributed consistency system is subjected to the current limiting operation, so that the request of the distributed consistency system can be simply and accurately limited, and the service quality of the distributed consistency system is effectively ensured.
The data processing method of the present embodiment may be performed by any suitable device having data processing capabilities, including but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal Digital Assistants (PDAs), tablet computers, notebook computers, palm-top gaming machines, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (e.g., *** Glass, oculus Rift, hololens, gear VR), and the like.
Referring to fig. 2, a flowchart of the steps of a data processing method according to a second embodiment of the present application is shown.
Specifically, the data processing method of the present embodiment includes the steps of:
in step S201, a session creation request carrying tenant information sent by the client is received.
In this embodiment, a tenant field may be added to the request header or the request carrier of the session creation request, and the tenant information may be carried by the tenant field. The tenant information may include at least one of: tenant name, tenant identification information, tenant validity period information. Tenant information is transferred to the distributed consistency system through the session creation request, mainly for realizing independent control of services, and different priorities can be provided for services with different importance according to a degradation principle, so that the important service request can be timely processed under abnormal conditions. In addition, the distributed consistency system can do more abundant current limiting work according to different tenants. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In step S202, a session corresponding to the tenant information is created based on the session creation request, so as to receive, through the session, the data request to be processed sent by the tenant through the client.
In this embodiment, the session may be understood as a mechanism where a client creates a lease with a distributed consistency system and requires the client to periodically send a heartbeat to the distributed consistency system to maintain the lease for a long period of time. The lease may be understood as the period of time that a certain resource is occupied in the computer domain. If the lease is not continued before the deadline, the occupancy relationship of the resources is automatically relieved. In addition, multiple users often use the system, different users refer to different tenants, and in the system, isolation is often needed for different tenants in terms of data, requests and the like, so that the data, the requests and the like can not be influenced mutually. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In a specific example, since the system is a session-based distributed consistency system, binding of the tenant and the session can be accomplished by only adding tenant information to the session creation request, without requiring that tenant information be entered for each data request. Once the session is created, all data requests in the session are bound to one tenant, which simplifies the complexity of the system while reducing the amount of data transmitted by the network. Of course, when the transfer of tenant information is implemented, each data request may carry tenant information, which, although increasing the burden of network transmission, is suitable for a scenario in which information of multiple tenants is stored in a single session. Such a scenario may occur in a front-end of a distributed consistency system, where the front-end proxies service requests of different tenants and completes the service requests of different tenants in one session. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In step S203, when it is determined that the distributed consistency system is in a busy state based on the number of data requests to be processed in the distributed consistency system, resource consumption data of the data requests to be processed in the distributed consistency system is estimated.
Since this step S203 is similar to the step S101 described above, the description thereof will not be repeated here.
In step S204, when it is determined that the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, a throttling operation is performed on the data request sent by the client.
Since this step S204 is similar to the step S102 described above, the description thereof will not be repeated here.
In some alternative embodiments, the method further comprises: determining the type of the tenant to which the data request to be processed belongs; and based on the type of the tenant, executing a current limiting operation on a data request sent by the tenant to the distributed consistency system through the client. By this, the data request sent to the distributed consistency system by the client can be more finely subjected to the current limiting operation by the tenant. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In a specific example, when determining the type of the tenant to which the data request to be processed belongs, the type of the tenant to which the data request to be processed belongs may be determined through a session in which the data request to be processed belongs. Because the session has a corresponding relation with the tenant information, the type of the tenant to which the data request to be processed belongs can be determined as long as the session in which the data request to be processed is located is determined. Wherein the types of the tenants comprise normal types and/or unrestricted types. The tenants are classified into two types because the tenants of some core applications need to have the right to process the service request preferentially, and in some extreme cases, the service request needs to be recovered preferentially, for example, the front end machine of the distributed consistency system needs to recover preferentially, so that the system at the back end can be helped to carry the pressure in advance, and in the extreme cases, the service request of the tenant of an unrestricted type can occupy the service request space of the tenant of a normal type greatly, so that the highest priority processing is obtained. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In a specific example, when performing a throttling operation on a data request sent by the tenant to the distributed consistency system through the client based on the type of the tenant, if resource consumption data of the data request sent by the tenant to the distributed consistency system through the client exceeds resource consumption permission data set by the distributed consistency system for the tenant of the normal type when the type of the tenant is a normal type, performing a throttling operation on a data request sent by the tenant to the distributed consistency system through the client, or performing a throttling operation on a data request sent by the tenant to the distributed consistency system through the client if the resource consumption data of the data request to be processed in the distributed consistency system exceeds global resource consumption permission data set by the distributed consistency system when the data request sent by the tenant through the client is received by the distributed consistency system through the client; when the type of the tenant is an unrestricted type, if the resource consumption data of the data request sent by the tenant to the distributed consistency system through the client exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the unrestricted type, executing a current limiting operation on the data request sent by the tenant to the distributed consistency system through the client. The resource consumption permission data set by the distributed consistency system for the normal type of tenant and the resource consumption permission data set by the distributed consistency system for the unrestricted type of tenant can be set by those skilled in the art according to actual needs, and the embodiment of the present application does not limit any limitation. In addition, the types of the tenants are not limited to normal types and/or unlimited types, the types of the tenants can be expanded to more types, and meanwhile, the distributed consistency system sets different resource consumption permission data for different types of tenants. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
The session cannot be resumed for a long time in the session disconnection scenario, basically due to a large number of invalid connections and invalid reconnection requests. Because the client is reconnected with the distributed consistency system, a timeout mechanism exists, and other service machines can be connected if timeout occurs, but the original machine cannot immediately sense a session disconnection event of the client, and only after a service data request in TCP connection is processed, a large number of invalid reconnection requests are caused, subsequent valid reconnection requests cannot be processed in time, and the subsequent valid reconnection requests become invalid reconnection requests, so that the session cannot be restored between the client and the distributed consistency system for a long time. However, after the data processing scheme provided by the embodiment of the application is adopted, the data request sent by the client to the distributed consistency system can be simply, conveniently and finely limited, so that the distributed consistency system is ensured to process the effective data request to the greatest extent, and further, the disconnected session can be quickly recovered. For example, a session of the front end with the distributed consistency system may be quickly resumed. Specifically, by setting the tenant of the front-end machine to be of an unlimited type, the session of the front-end machine with the distributed consistency system is preferentially restored. Then, a specific recovery time can be calculated. Assuming that the speed of processing per second of the distributed consistency system is V, the total number of sessions in the distributed consistency system is N, and the recovery time of a session that is theoretically disconnected is:
Meaning that if the total number of sessions in a distributed consistency system is 10 ten thousand sessions, the processing speed per second is 2 ten thousand sessions, and in theory, recovery of disconnected sessions can be completed in 5 seconds. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
In practical application, the data processing scheme provided by the embodiment of the application can be applied to all online mythology clusters. Testing is carried out on ten thousands of clusters of ODPS lines, so that the service quality is effectively ensured. It will be appreciated that the above description is exemplary only, and that the embodiments of the application are not limited in any way.
On the basis of the first embodiment, a session creation request carrying tenant information sent by the client is received, and a session corresponding to the tenant information is created based on the session creation request, so that the data request to be processed sent by the tenant through the client is received through the session. Once the session creation is complete, all requests in the session are bound to one tenant, and this design simplifies the complexity of the distributed consistency system while reducing the amount of data transferred by the network in the session.
The data processing method of the present embodiment may be performed by any suitable device having data processing capabilities, including but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal Digital Assistants (PDAs), tablet computers, notebook computers, palm-top gaming machines, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (e.g., *** Glass, oculus Rift, hololens, gear VR), and the like.
Referring to fig. 3, a schematic diagram of a data processing apparatus according to a third embodiment of the present application is shown.
The data processing apparatus of the present embodiment includes: the estimating module 301 is configured to estimate resource consumption data of a data request to be processed in a distributed consistency system when the distributed consistency system is determined to be in a busy state based on the number of data requests to be processed in the distributed consistency system; a first current limiting module 302, configured to perform a current limiting operation on a data request sent by a client connected to the distributed consistency system when it is determined that the resource consumption data exceeds global resource consumption permission data set by the distributed consistency system.
The data processing device of the present embodiment is configured to implement the corresponding data processing method in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again.
Referring to fig. 4, a schematic diagram of the structure of a data processing apparatus according to a fourth embodiment of the present application is shown.
The data processing apparatus of the present embodiment includes: a pre-estimating module 404, configured to pre-estimate resource consumption data of a data request to be processed in a distributed coherency system when the distributed coherency system is determined to be in a busy state based on the number of data requests to be processed in the distributed coherency system; and the first current limiting module 405 is configured to perform a current limiting operation on a data request sent by a client connected to the distributed consistency system when it is determined that the resource consumption data exceeds global resource consumption permission data set by the distributed consistency system.
Optionally, before the estimating module 404, the apparatus further includes: a first determining module 401, configured to determine that the distributed consistency system is in a busy state if it is determined that the number of data requests to be processed is greater than or equal to a preset number threshold.
Optionally, before the estimating module 404, the apparatus further includes: a receiving module 402, configured to receive a session creation request carrying tenant information sent by the client; a creating module 403, configured to create a session corresponding to the tenant information based on the session creation request, so as to receive, through the session, the data request to be processed sent by the tenant through the client.
Optionally, the estimating module 404 is specifically configured to: determining the request type of the data request to be processed; determining resource consumption weight data corresponding to the data request to be processed based on the request type to which the data request to be processed belongs; and estimating the resource consumption data of the data request to be processed in the distributed consistency system based on the resource consumption weight data corresponding to the data request to be processed.
Optionally, the apparatus further comprises: a second determining module 406, configured to determine a type of a tenant to which the data request to be processed belongs; and the second current limiting module 407 is configured to perform a current limiting operation on a data request sent by the tenant to the distributed consistency system through the client based on the type of the tenant.
Optionally, the second current limiting module 407 is specifically configured to: when the type of the tenant is a normal type, if the resource consumption data of the tenant in the distributed consistency system exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the normal type, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, or when the distributed consistency system receives the data request of the tenant sent by the client, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, if the resource consumption data of the data request to be processed in the distributed consistency system exceeds the global resource consumption permission data set by the distributed consistency system; when the type of the tenant is an unrestricted type, if the resource consumption data of the data request sent by the tenant to the distributed consistency system through the client exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the unrestricted type, executing a current limiting operation on the data request sent by the tenant to the distributed consistency system through the client.
The data processing device of the present embodiment is configured to implement the corresponding data processing method in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again.
Fig. 5 is a schematic structural diagram of an electronic device in a fifth embodiment of the present application; the electronic device may include:
One or more processors 501;
computer readable media 502, which may be configured to store one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the data processing method as described in the first or second embodiments.
Fig. 6 is a hardware structure of an electronic device in a sixth embodiment of the present application; as shown in fig. 6, the hardware structure of the electronic device may include: a processor 601, a communication interface 602, a computer readable medium 603 and a communication bus 604;
Wherein the processor 601, the communication interface 602, and the computer readable medium 603 communicate with each other via a communication bus 604;
alternatively, the communication interface 602 may be an interface of a communication module, such as an interface of a GSM module;
Wherein the processor 601 may specifically be configured to: when the distributed consistency system is in a busy state based on the quantity of data requests to be processed in the distributed consistency system, estimating resource consumption data of the data requests to be processed in the distributed consistency system; and executing a current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system.
The processor 601 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), and the like; but may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The computer readable medium 603 can be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code configured to perform the method shown in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via a communication portion, and/or installed from a removable medium. The above-described functions defined in the method of the present application are performed when the computer program is executed by a Central Processing Unit (CPU). The computer readable medium according to the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage media element, a magnetic storage media element, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code configured to carry out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computers may be connected via any kind of network: including a Local Area Network (LAN) or a Wide Area Network (WAN), to connect to the user's computer, or may be connected to external computers (e.g., by way of the internet using an internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions configured to implement the specified logical function(s). The specific relationships in the embodiments described above are merely exemplary, and fewer, more, or an adjusted order of execution of the steps may be possible in a specific implementation. That is, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present application may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes a prediction module and a first current limit module. Where the names of these modules do not constitute a limitation on the module itself in some cases, for example, the estimation module may also be described as "a module that estimates resource consumption data of a data request to be processed in a distributed coherency system when the distributed coherency system is determined to be in a busy state based on the number of data requests to be processed in the distributed coherency system".
As another aspect, the present application also provides a computer-readable medium having stored thereon a computer program which, when executed by a processor, implements a data processing method as described in the above-described embodiment one or embodiment two.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: when the distributed consistency system is in a busy state based on the quantity of data requests to be processed in the distributed consistency system, estimating resource consumption data of the data requests to be processed in the distributed consistency system; and executing a current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system.
The terms "first," "second," "the first," or "the second," as used in various embodiments of the present disclosure, may modify various components without regard to order and/or importance, but these terms do not limit the corresponding components. The above description is only configured for the purpose of distinguishing an element from other elements. For example, the first user device and the second user device represent different user devices, although both are user devices. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure.
When an element (e.g., a first element) is referred to as being "coupled" (operatively or communicatively) to "another element (e.g., a second element) or" connected "to another element (e.g., a second element), it is understood that the one element is directly connected to the other element or the one element is indirectly connected to the other element via yet another element (e.g., a third element). In contrast, it will be understood that when an element (e.g., a first element) is referred to as being "directly connected" or "directly coupled" to another element (a second element), then no element (e.g., a third element) is interposed therebetween.
The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application referred to in the present application is not limited to the specific combinations of the technical features described above, but also covers other technical features formed by any combination of the technical features described above or their equivalents without departing from the inventive concept described above. Such as the above-mentioned features and the technical features disclosed in the present application (but not limited to) having similar functions are replaced with each other.
Claims (12)
1. A method of data processing, the method comprising:
When the distributed consistency system is in a busy state based on the quantity of data requests to be processed in the distributed consistency system, estimating resource consumption data of the data requests to be processed in the distributed consistency system;
When the resource consumption data exceeds the global resource consumption permission data set by the distributed consistency system, executing a current limiting operation on a data request sent by a client connected with the distributed consistency system;
The predicting the resource consumption data of the data request to be processed in the distributed consistency system comprises the following steps: determining the request type of the data request to be processed; determining resource consumption weight data corresponding to the data request to be processed based on the request type to which the data request to be processed belongs; and estimating the resource consumption data of the data request to be processed in the distributed consistency system based on the resource consumption weight data corresponding to the data request to be processed.
2. The method of claim 1, wherein the predicting the pending data request precedes the resource consumption data in the distributed consistency system, the method further comprising:
and if the number of the data requests to be processed is determined to be greater than or equal to a preset number threshold, determining that the distributed consistency system is in a busy state.
3. The method of claim 1, wherein the predicting the pending data request precedes the resource consumption data in the distributed consistency system, the method further comprising:
Receiving a session creation request carrying tenant information sent by the client;
And creating a session corresponding to the tenant information based on the session creation request, so as to receive the data request to be processed, which is sent by the tenant through the client, through the session.
4. The method according to claim 1, wherein the method further comprises:
determining the type of the tenant to which the data request to be processed belongs;
And based on the type of the tenant, executing a current limiting operation on a data request sent by the tenant to the distributed consistency system through the client.
5. The method of claim 4, wherein the performing a current limit operation on the data request sent by the tenant to the distributed consistency system through the client based on the type of the tenant comprises:
when the type of the tenant is a normal type, if the resource consumption data of the tenant in the distributed consistency system exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the normal type, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, or when the distributed consistency system receives the data request of the tenant sent by the client, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, if the resource consumption data of the data request to be processed in the distributed consistency system exceeds the global resource consumption permission data set by the distributed consistency system;
When the type of the tenant is an unrestricted type, if the resource consumption data of the data request sent by the tenant to the distributed consistency system through the client exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the unrestricted type, executing a current limiting operation on the data request sent by the tenant to the distributed consistency system through the client.
6. A data processing apparatus, the apparatus comprising:
the estimating module is used for estimating the resource consumption data of the data request to be processed in the distributed consistency system when the distributed consistency system is in a busy state based on the quantity of the data request to be processed in the distributed consistency system;
The first current limiting module is used for executing current limiting operation on a data request sent by a client connected with the distributed consistency system when the resource consumption data exceeds global resource consumption permission data set by the distributed consistency system;
The estimating module is specifically configured to: determining the request type of the data request to be processed; determining resource consumption weight data corresponding to the data request to be processed based on the request type to which the data request to be processed belongs; and estimating the resource consumption data of the data request to be processed in the distributed consistency system based on the resource consumption weight data corresponding to the data request to be processed.
7. The apparatus of claim 6, wherein prior to the predictive module, the apparatus further comprises:
And the first determining module is used for determining that the distributed consistency system is in a busy state if the number of the data requests to be processed is greater than or equal to a preset number threshold value.
8. The apparatus of claim 6, wherein prior to the predictive module, the apparatus further comprises:
The receiving module is used for receiving a session creation request carrying tenant information sent by the client;
and the creating module is used for creating a session corresponding to the tenant information based on the session creating request so as to receive the data request to be processed, which is sent by the tenant through the client, through the session.
9. The apparatus of claim 6, wherein the apparatus further comprises:
A second determining module, configured to determine a type of a tenant to which the data request to be processed belongs;
and the second current limiting module is used for executing current limiting operation on the data request sent by the tenant to the distributed consistency system through the client based on the type of the tenant.
10. The apparatus according to claim 9, wherein the second flow limiting module is specifically configured to:
when the type of the tenant is a normal type, if the resource consumption data of the tenant in the distributed consistency system exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the normal type, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, or when the distributed consistency system receives the data request of the tenant sent by the client, executing a current limiting operation on the data request of the tenant sent by the client to the distributed consistency system, if the resource consumption data of the data request to be processed in the distributed consistency system exceeds the global resource consumption permission data set by the distributed consistency system;
When the type of the tenant is an unrestricted type, if the resource consumption data of the data request sent by the tenant to the distributed consistency system through the client exceeds the resource consumption permission data set by the distributed consistency system for the tenant of the unrestricted type, executing a current limiting operation on the data request sent by the tenant to the distributed consistency system through the client.
11. An electronic device, comprising:
one or more processors;
A computer readable medium configured to store one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the data processing method of any of claims 1-5.
12. A computer readable medium on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a data processing method as claimed in any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911355053.4A CN113032410B (en) | 2019-12-25 | 2019-12-25 | Data processing method, device, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911355053.4A CN113032410B (en) | 2019-12-25 | 2019-12-25 | Data processing method, device, electronic equipment and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113032410A CN113032410A (en) | 2021-06-25 |
| CN113032410B true CN113032410B (en) | 2024-05-03 |
Family
ID=76458094
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911355053.4A Active CN113032410B (en) | 2019-12-25 | 2019-12-25 | Data processing method, device, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113032410B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113923163A (en) * | 2021-10-20 | 2022-01-11 | 广东亿迅科技有限公司 | Long connection message channel based current limiting method and system |
| CN114254036A (en) * | 2021-11-12 | 2022-03-29 | 阿里巴巴（中国）有限公司 | Data processing method and system |
| CN114629806B (en) * | 2022-04-13 | 2023-12-12 | 腾讯科技(成都)有限公司 | Data processing method, device, electronic equipment, storage medium and program product |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101959252A (en) * | 2009-07-15 | 2011-01-26 | 华为技术有限公司 | Quality of service (QoS) control and strategy configuration method and device |
| CN106713171A (en) * | 2015-07-28 | 2017-05-24 | 腾讯科技（深圳）有限公司 | Server and delay-queue-based current-limiting protection system and method |
| CN107204967A (en) * | 2016-03-18 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Resources regulation method and device during safe physical examination |
| CN109120548A (en) * | 2018-07-02 | 2019-01-01 | 联动优势电子商务有限公司 | A kind of flow control methods and device |
| CN109885399A (en) * | 2019-01-17 | 2019-06-14 | 平安普惠企业管理有限公司 | Data processing method, electronic device, computer equipment and storage medium |
| CN110049084A (en) * | 2018-12-10 | 2019-07-23 | 阿里巴巴集团控股有限公司 | Current-limiting method, device and the equipment of distributed system |
| CN110401720A (en) * | 2019-07-31 | 2019-11-01 | 中国工商银行股份有限公司 | Information processing method, device, system, application server and medium |
| CN110417677A (en) * | 2019-07-29 | 2019-11-05 | 北京易捷思达科技发展有限公司 | A kind of QoS control method based on Ceph distributed storage Osd end data Recovery |
| CN110430141A (en) * | 2019-08-08 | 2019-11-08 | 北京字节跳动网络技术有限公司 | Current-limiting method and device |
| CN110460541A (en) * | 2019-07-30 | 2019-11-15 | 秒针信息技术有限公司 | Current-limiting method and device applied to web server |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7865547B2 (en) * | 2002-09-12 | 2011-01-04 | Siemens Enterprise Communications, Inc. | System and method for accessing busy IP network resources |
| NZ595563A (en) * | 2009-03-31 | 2014-04-30 | Freestyle Technology Pty Ltd | A communications process, device and system |
| FR3011420A1 (en) * | 2013-09-30 | 2015-04-03 | Orange | IMPROVED MANAGEMENT OF NETWORK CONNECTIONS |
-
2019
- 2019-12-25 CN CN201911355053.4A patent/CN113032410B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101959252A (en) * | 2009-07-15 | 2011-01-26 | 华为技术有限公司 | Quality of service (QoS) control and strategy configuration method and device |
| CN106713171A (en) * | 2015-07-28 | 2017-05-24 | 腾讯科技（深圳）有限公司 | Server and delay-queue-based current-limiting protection system and method |
| CN107204967A (en) * | 2016-03-18 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Resources regulation method and device during safe physical examination |
| CN109120548A (en) * | 2018-07-02 | 2019-01-01 | 联动优势电子商务有限公司 | A kind of flow control methods and device |
| CN110049084A (en) * | 2018-12-10 | 2019-07-23 | 阿里巴巴集团控股有限公司 | Current-limiting method, device and the equipment of distributed system |
| CN109885399A (en) * | 2019-01-17 | 2019-06-14 | 平安普惠企业管理有限公司 | Data processing method, electronic device, computer equipment and storage medium |
| CN110417677A (en) * | 2019-07-29 | 2019-11-05 | 北京易捷思达科技发展有限公司 | A kind of QoS control method based on Ceph distributed storage Osd end data Recovery |
| CN110460541A (en) * | 2019-07-30 | 2019-11-15 | 秒针信息技术有限公司 | Current-limiting method and device applied to web server |
| CN110401720A (en) * | 2019-07-31 | 2019-11-01 | 中国工商银行股份有限公司 | Information processing method, device, system, application server and medium |
| CN110430141A (en) * | 2019-08-08 | 2019-11-08 | 北京字节跳动网络技术有限公司 | Current-limiting method and device |
Non-Patent Citations (2)
| Title |
|---|
| 基于微服务架构的基础设施设计;蒋勇;;软件;20160515(05);全文 * |
| 基于资源感知的SaaS服务QoS保障机制研究;杨恩峰;张勇;刘士军;;小型微型计算机***;20130115(01);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113032410A (en) | 2021-06-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113032410B (en) | Data processing method, device, electronic equipment and computer storage medium | |
| US20200202312A1 (en) | Method and system for selectively using network coding for propagating transactions in a blockchain network | |
| US11265235B2 (en) | Technologies for capturing processing resource metrics as a function of time | |
| CN107645407B (en) | Method and device for adapting QoS | |
| US9172646B2 (en) | Dynamic reconfiguration of network devices for outage prediction | |
| EP3218807B1 (en) | Method and system for real-time resource consumption control in a distributed computing environment | |
| EP2838243B1 (en) | Capability aggregation and exposure method and system | |
| US9059941B1 (en) | Providing router information according to a programmatic interface | |
| CN110058937B (en) | Method, apparatus and medium for scheduling dedicated processing resources | |
| CN113141321B (en) | Data transmission method based on edge calculation and electronic equipment | |
| CN112600761B (en) | Resource allocation method, device and storage medium | |
| CN109428926B (en) | Method and device for scheduling task nodes | |
| US10827001B2 (en) | Managing connections for data communications | |
| CN116069493A (en) | Data processing method, device, equipment and readable storage medium | |
| CN114253698A (en) | Resource scheduling method, system, electronic device and storage medium | |
| US20180131756A1 (en) | Method and system for affinity load balancing | |
| US10374986B2 (en) | Scalable, real-time messaging system | |
| CN113225265B (en) | Flow control method, device, equipment and computer storage medium | |
| CN114884823A (en) | Flow congestion control method and device, computer readable medium and electronic equipment | |
| CN114765613A (en) | Client-driven cloud network access system and method | |
| CN115022245A (en) | Data transmission method, related device, equipment and storage medium | |
| JP6595419B2 (en) | API providing apparatus and API request control method | |
| US9674282B2 (en) | Synchronizing SLM statuses of a plurality of appliances in a cluster | |
| US11876730B2 (en) | Method and apparatus for using high availability controller with local area network (LAN) for local cloud | |
| US11621919B2 (en) | Dynamic load balancing in reactive systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |