CN113535415B - Resource acquisition method and terminal - Google Patents
Resource acquisition method and terminal Download PDFInfo
- Publication number
- CN113535415B CN113535415B CN202110685145.XA CN202110685145A CN113535415B CN 113535415 B CN113535415 B CN 113535415B CN 202110685145 A CN202110685145 A CN 202110685145A CN 113535415 B CN113535415 B CN 113535415B
- Authority
- CN
- China
- Prior art keywords
- acquired
- upstream node
- resource
- resources
- resource acquisition
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
Abstract
The invention discloses a resource acquisition method and a terminal, which are used for receiving resource acquisition requests sent by an upstream node, judging whether the number of all resource acquisition requests reaches a threshold value if the resources to be acquired are locked, returning a special abnormal identifier to the upstream node if the number of all resource acquisition requests reaches the threshold value, carrying out request locking by the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster; therefore, when the resources to be acquired are locked and the number of the requests reaches a threshold value, the requests of the upstream nodes are locked, invalid requests of the upstream nodes can be reduced, and the safety and the robustness of the system are improved, so that the efficiency of resource acquisition is improved.
Description
Technical Field
The present invention relates to the field of resource management technologies, and in particular, to a resource obtaining method and a terminal.
Background
In the present distributed system, there are many situations where resources are shared, such as a shared memory resource, and only one thread is allowed to access at a time. In order to implement this access mechanism, a mechanism is generally used at present to lock the resource, for example, an interface provided by a server side, where the interface accesses a shared memory resource, because the interface of the server side provides concurrent access to the outside, in order to ensure that only one thread accesses the memory resource at the same time, the interface method internally locks a module accessing the shared resource, that is, the module needs to acquire a lock preferentially every time, and access to the shared resource is allowed after the lock is successfully acquired.
However, the interfaces of the server end all need to provide concurrent access, and in a concurrent scene, after a certain interface calls and locks the resource, when other interfaces call again later, the resource cannot be obtained again because the resource is locked, and then abnormal information is returned. However, because the downstream resource is locked, the upstream system cannot know, and thus under this scenario, the upstream service will continue to call the downstream interface, which results in increased invalid requests and reduced service processing efficiency.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: the resource acquisition method and the terminal are provided, and the resource acquisition efficiency can be improved.
In order to solve the technical problems, the invention adopts the following technical scheme:
a resource acquisition method comprising the steps of:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, carrying out request locking on the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster.
In order to solve the technical problems, the invention adopts another technical scheme that:
a resource acquisition terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, carrying out request locking on the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster.
The invention has the beneficial effects that: receiving resource acquisition requests sent by an upstream node, judging whether the number of all resource acquisition requests reaches a threshold value if the resources to be acquired are locked, returning a special abnormal identifier to the upstream node if the number of all resource acquisition requests reaches the threshold value, carrying out request locking by the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster; therefore, when the resources to be acquired are locked and the number of the requests reaches a threshold value, the requests of the upstream nodes are locked, invalid requests of the upstream nodes can be reduced, and the safety and the robustness of the system are improved, so that the efficiency of resource acquisition is improved.
Drawings
FIG. 1 is a flow chart of a resource acquisition method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a resource acquisition terminal according to an embodiment of the present invention.
Detailed Description
In order to describe the technical contents, the achieved objects and effects of the present invention in detail, the following description will be made with reference to the embodiments in conjunction with the accompanying drawings.
Referring to fig. 1, an embodiment of the present invention provides a method for obtaining resources, including the steps of:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, carrying out request locking on the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster.
From the above description, the beneficial effects of the invention are as follows: receiving resource acquisition requests sent by an upstream node, judging whether the number of all resource acquisition requests reaches a threshold value if the resources to be acquired are locked, returning a special abnormal identifier to the upstream node if the number of all resource acquisition requests reaches the threshold value, carrying out request locking by the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster; therefore, when the resources to be acquired are locked and the number of the requests reaches a threshold value, the requests of the upstream nodes are locked, invalid requests of the upstream nodes can be reduced, and the safety and the robustness of the system are improved, so that the efficiency of resource acquisition is improved.
Further, the request locking of the upstream node according to the special exception identifier includes:
and setting and starting request locking in an upstream node according to the special exception identifier, and setting a time threshold for the request locking by the upstream node.
From the above description, setting and opening the request lock at the upstream node according to the special exception identifier can reduce invalid requests of the upstream node to the resource to be acquired after the resource to be acquired is locked.
Further, the method further comprises the following steps:
judging whether the set time length of the request locking is greater than the time threshold, if so, deleting the locking information corresponding to the resource to be acquired in the public cluster;
and if the lock information of the resource to be acquired does not exist in the public cluster, receiving a resource acquisition request sent by the upstream node.
As can be seen from the above description, when the setting time of the request lock is longer than the time threshold, the lock information in the public cluster is deleted, and when the lock information of the resource to be acquired in the public cluster does not exist, the request sent by the upstream node can be received again, so that the robustness of the program is improved.
Further, the returning the special exception identification to the upstream node includes:
establishing a monitoring channel between the upstream node and the node where the resource to be acquired is located;
and sending the special abnormal identifier of the node where the resource to be acquired is located to the upstream node according to the monitoring channel.
As can be seen from the above description, by establishing a listening channel in the upstream node and the resource to be acquired, the upstream node can acquire information of the resource to be acquired according to the listening channel.
Further, the method further comprises the following steps:
if the locked resources to be acquired are unlocked or the number of all the resource acquisition requests does not reach a threshold value, notifying the upstream node to unlock the requests of the resources to be acquired, and deleting the lock information corresponding to the resources to be acquired in the public cluster.
As can be seen from the above description, deleting the lock information in the common cluster can reduce the storage pressure of the common cluster after the locked resource to be acquired is unlocked or when the number of all the resource acquisition requests does not reach the threshold.
Referring to fig. 2, another embodiment of the present invention provides a resource obtaining terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, carrying out request locking on the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster.
As can be seen from the above description, receiving a resource acquisition request sent by an upstream node, if a resource to be acquired is already locked, judging whether the number of all the resource acquisition requests reaches a threshold, if so, returning a special abnormal identifier to the upstream node, and performing request locking by the upstream node according to the special abnormal identifier, synchronizing lock information of the resource to be acquired to a public cluster, and acquiring the lock information of the resource to be acquired by the upstream node requesting locking by querying the public cluster; therefore, when the resources to be acquired are locked and the number of the requests reaches a threshold value, the requests of the upstream nodes are locked, invalid requests of the upstream nodes can be reduced, and the safety and the robustness of the system are improved, so that the efficiency of resource acquisition is improved.
Further, the request locking of the upstream node according to the special exception identifier includes:
and setting and starting request locking in an upstream node according to the special exception identifier, and setting a time threshold for the request locking by the upstream node.
From the above description, setting and opening the request lock at the upstream node according to the special exception identifier can reduce invalid requests of the upstream node to the resource to be acquired after the resource to be acquired is locked.
Further, the method further comprises the following steps:
judging whether the set time length of the request locking is greater than the time threshold, if so, deleting the locking information corresponding to the resource to be acquired in the public cluster;
and if the lock information of the resource to be acquired does not exist in the public cluster, receiving a resource acquisition request sent by the upstream node.
As can be seen from the above description, when the setting time of the request lock is longer than the time threshold, the lock information in the public cluster is deleted, and when the lock information of the resource to be acquired in the public cluster does not exist, the request sent by the upstream node can be received again, so that the robustness of the program is improved.
Further, the returning the special exception identification to the upstream node includes:
establishing a monitoring channel between the upstream node and the node where the resource to be acquired is located;
and sending the special abnormal identifier of the node where the resource to be acquired is located to the upstream node according to the monitoring channel.
As can be seen from the above description, by establishing a listening channel in the upstream node and the resource to be acquired, the upstream node can acquire information of the resource to be acquired according to the listening channel.
Further, the method further comprises the following steps:
if the locked resources to be acquired are unlocked or the number of all the resource acquisition requests does not reach a threshold value, notifying the upstream node to unlock the requests of the resources to be acquired, and deleting the lock information corresponding to the resources to be acquired in the public cluster.
As can be seen from the above description, deleting the lock information in the common cluster can reduce the storage pressure of the common cluster after the locked resource to be acquired is unlocked or when the number of all the resource acquisition requests does not reach the threshold.
The resource acquisition method and the terminal are suitable for various shared resource scenes, can improve the resource acquisition efficiency, and are described by the following specific embodiments:
example 1
Referring to fig. 1, a method for obtaining resources includes the steps of:
s1, receiving a resource acquisition request sent by an upstream node.
Specifically, in this embodiment, the upstream node includes a client, when all requests for acquiring resources sent by the client are performed in normal order, the resource acquisition request sent by the client normally arrives at the public platform gateway, and the public platform gateway requests the resource issuing system to acquire a resource interface, and locks resources in advance in the interface after the request arrives at the resource acquisition interface.
S2, if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, carrying out request locking on the upstream node according to the special abnormal identifier, synchronizing the lock information of the resources to be acquired to a public cluster, and acquiring the lock information of the resources to be acquired by the upstream node requesting locking through inquiring the public cluster.
Specifically, when all requests for acquiring resources arrive concurrently, at this time, if the resource acquisition request locks the resource to be acquired and the resource acquisition and processing are being performed, counting all subsequent resource acquisition requests, recording the subsequent resource acquisition requests in the local memory, and when the number of the resource acquisition requests reaches 10, returning the SPECIAL exception CODE 'special_code' uniformly and quickly by all subsequent requests, and synchronizing the lock information of the resource to be acquired into the public redis cluster.
The SPECIAL exception identifier is the SPECIAL exception CODE "special_code" described above.
Wherein the returning of the special exception identification to the upstream node comprises:
establishing a monitoring channel between the upstream node and the node where the resource to be acquired is located;
and sending the special abnormal identifier of the node where the resource to be acquired is located to the upstream node according to the monitoring channel.
Specifically, a monitoring channel is established between all clients and the downstream node where the resource to be acquired is located, the monitoring channel is similar to a long-link monitoring channel of a zookeeper cluster, and when the downstream node locks the resource and waits for a request of the locked resource to reach a preset threshold value, the upstream node is informed of that the resource is locked in real time.
Wherein the request locking of the upstream node according to the special exception identifier comprises:
and setting and starting request locking in an upstream node according to the special exception identifier, and setting a time threshold for the request locking by the upstream node.
Specifically, when the public platform gateway does not acquire the return information of the resource distribution system, the interface is indicated to be in normal business processing. When the upstream node acquires the special abnormal code returned by the downstream node, a request locking switch is set and started in a local memory of the upstream node, and a time threshold is set for the request locking switch; when the subsequent public platform gateway continues to receive the client request, as the switch is opened at this time, whether the lock information in the public redis cluster still exists or not is directly inquired, and when the lock information still exists, abnormal information is quickly returned to the client to prompt information such as 'resources are busy, please process later', and the like, and the resource issuing system is not required to be called again.
Judging whether the set time length of the request locking is greater than the time threshold, if so, deleting the locking information corresponding to the resource to be acquired in the public cluster;
and if the lock information of the resource to be acquired does not exist in the public cluster, receiving a resource acquisition request sent by the upstream node.
Specifically, when lock information in the public redis cluster is queried for a certain time, or when the time set by a switch in a local memory of the last time exceeds a preset threshold value, the information of the public redis cluster is not checked any more when the subsequent public platform gateway calls an interface of the voucher system, a resource acquisition request sent by an upstream node is received, and a downstream interface is directly accessed.
Therefore, by the lock synchronization mechanism in this embodiment, after the downstream shared resource is locked, the lock information can be synchronized to the public information, and the lock information in the public information will be queried in advance before the downstream method is called again by the upstream service for a subsequent period of time, and when the lock information still exists, a part of reentrant flow which does not need to call the downstream service can be intercepted, so that the problem of reentry request can be solved, the invalid request to the downstream can be reduced, and the processing efficiency of the system is further improved.
Example two
The difference between the present embodiment and the first embodiment is that it is further defined how to acquire a resource when the locked resource to be acquired is unlocked or the number of all resource acquisition requests does not reach a threshold, specifically:
if the locked resources to be acquired are unlocked or the number of all the resource acquisition requests does not reach a threshold value, notifying the upstream node to unlock the requests of the resources to be acquired, and deleting the lock information corresponding to the resources to be acquired in the public cluster.
In this embodiment, when the downstream node is unlocked or the downstream node is still locked, but the request for the locked resource is waiting for a certain value, the upstream node may be notified of the unlocked resource, and the subsequent upstream node may delete the switch setting in the local memory and continue to issue the request to the downstream node.
Example III
Referring to fig. 2, a resource obtaining terminal includes a memory, a processor and a computer program stored in the memory and capable of running on the processor, where the processor implements the steps of the resource obtaining method according to the first or second embodiments when executing the computer program.
In summary, according to the resource acquisition method and the terminal provided by the invention, a resource acquisition request sent by an upstream node is received, if resources to be acquired are already locked, whether the number of all the resource acquisition requests reaches a threshold value is judged, if the number of the resource acquisition requests reaches the threshold value, a special abnormal identifier is returned to the upstream node, the upstream node performs request locking according to the special abnormal identifier, lock information of the resources to be acquired is synchronized to a public cluster, and the upstream node requesting locking acquires the lock information of the resources to be acquired by querying the public cluster; the upstream node performs request locking to set and start the request locking switch, and further processes the resource locking information by judging whether the setting time of the request locking switch reaches a time threshold value, so that the robustness of the system is ensured; therefore, when the resources to be acquired are locked and the number of requests reaches a threshold value, the requests of the upstream nodes are locked, and invalid requests of the upstream nodes can be controllably reduced by the method for synchronizing the lock information to different upstream nodes, so that the safety and the robustness of the system are improved to a certain extent.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent changes made by the specification and drawings of the present invention, or direct or indirect application in the relevant art, are included in the scope of the present invention.
Claims (6)
1. A method for obtaining resources, comprising the steps of:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, performing request locking on the upstream node according to the special abnormal identifier, and synchronizing the lock information of the resources to be acquired to a public cluster, wherein the upstream node requesting locking acquires the lock information of the resources to be acquired by querying the public cluster;
the request locking of the upstream node according to the special exception identifier comprises the following steps:
setting and starting request locking in an upstream node according to the special abnormal identifier, and setting a time threshold for the request locking by the upstream node;
the returning of the special exception identification to the upstream node includes:
establishing a monitoring channel between the upstream node and the node where the resource to be acquired is located;
and sending the special abnormal identifier of the node where the resource to be acquired is located to the upstream node according to the monitoring channel.
2. The resource acquisition method according to claim 1, further comprising:
judging whether the set time length of the request locking is greater than the time threshold, if so, deleting the locking information corresponding to the resource to be acquired in the public cluster;
and if the lock information of the resource to be acquired does not exist in the public cluster, receiving a resource acquisition request sent by the upstream node.
3. The resource acquisition method according to claim 1, further comprising:
if the locked resources to be acquired are unlocked or the number of all the resource acquisition requests does not reach a threshold value, notifying the upstream node to unlock the requests of the resources to be acquired, and deleting the lock information corresponding to the resources to be acquired in the public cluster.
4. A resource acquisition terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the following steps when executing the computer program:
receiving a resource acquisition request sent by an upstream node;
if the resources to be acquired corresponding to the resource acquisition requests are locked, judging whether the number of all the resource acquisition requests reaches a threshold value, if so, returning a special abnormal identifier to the upstream node, performing request locking on the upstream node according to the special abnormal identifier, and synchronizing the lock information of the resources to be acquired to a public cluster, wherein the upstream node requesting locking acquires the lock information of the resources to be acquired by querying the public cluster;
the request locking of the upstream node according to the special exception identifier comprises the following steps:
setting and starting request locking in an upstream node according to the special abnormal identifier, and setting a time threshold for the request locking by the upstream node;
the returning of the special exception identification to the upstream node includes:
establishing a monitoring channel between the upstream node and the node where the resource to be acquired is located;
and sending the special abnormal identifier of the node where the resource to be acquired is located to the upstream node according to the monitoring channel.
5. The resource acquisition terminal of claim 4, further comprising:
judging whether the set time length of the request locking is greater than the time threshold, if so, deleting the locking information corresponding to the resource to be acquired in the public cluster;
and if the lock information of the resource to be acquired does not exist in the public cluster, receiving a resource acquisition request sent by the upstream node.
6. The resource acquisition terminal of claim 4, further comprising:
if the locked resources to be acquired are unlocked or the number of all the resource acquisition requests does not reach a threshold value, notifying the upstream node to unlock the requests of the resources to be acquired, and deleting the lock information corresponding to the resources to be acquired in the public cluster.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110685145.XA CN113535415B (en) | 2021-06-21 | 2021-06-21 | Resource acquisition method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110685145.XA CN113535415B (en) | 2021-06-21 | 2021-06-21 | Resource acquisition method and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535415A CN113535415A (en) | 2021-10-22 |
| CN113535415B true CN113535415B (en) | 2023-08-04 |
Family
ID=78125364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110685145.XA Active CN113535415B (en) | 2021-06-21 | 2021-06-21 | Resource acquisition method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535415B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010191575A (en) * | 2009-02-17 | 2010-09-02 | Panasonic Corp | Resource exclusive control method and resource exclusive control device |
| CN105338094A (en) * | 2015-11-17 | 2016-02-17 | 中国建设银行股份有限公司 | Data processing method and system |
| CN109697127A (en) * | 2017-10-24 | 2019-04-30 | 华为技术有限公司 | The method and apparatus that the access operation of a kind of pair of shared resource locks |
| CN111158878A (en) * | 2019-12-30 | 2020-05-15 | 北京三快在线科技有限公司 | Resource transfer request thread control method, device and storage medium |
| CN111399991A (en) * | 2020-06-05 | 2020-07-10 | 腾讯科技（深圳）有限公司 | Virtual resource locking method and device, storage medium and electronic device |
| CN111737020A (en) * | 2020-06-24 | 2020-10-02 | 广联达科技股份有限公司 | Concurrent processing method and device for distributed cluster |
| CN112256424A (en) * | 2020-09-22 | 2021-01-22 | 北京达佳互联信息技术有限公司 | Virtual resource processing method, device and system, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7337290B2 (en) * | 2003-04-03 | 2008-02-26 | Oracle International Corporation | Deadlock resolution through lock requeing |
-
2021
- 2021-06-21 CN CN202110685145.XA patent/CN113535415B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010191575A (en) * | 2009-02-17 | 2010-09-02 | Panasonic Corp | Resource exclusive control method and resource exclusive control device |
| CN105338094A (en) * | 2015-11-17 | 2016-02-17 | 中国建设银行股份有限公司 | Data processing method and system |
| CN109697127A (en) * | 2017-10-24 | 2019-04-30 | 华为技术有限公司 | The method and apparatus that the access operation of a kind of pair of shared resource locks |
| CN111158878A (en) * | 2019-12-30 | 2020-05-15 | 北京三快在线科技有限公司 | Resource transfer request thread control method, device and storage medium |
| CN111399991A (en) * | 2020-06-05 | 2020-07-10 | 腾讯科技（深圳）有限公司 | Virtual resource locking method and device, storage medium and electronic device |
| CN111737020A (en) * | 2020-06-24 | 2020-10-02 | 广联达科技股份有限公司 | Concurrent processing method and device for distributed cluster |
| CN112256424A (en) * | 2020-09-22 | 2021-01-22 | 北京达佳互联信息技术有限公司 | Virtual resource processing method, device and system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535415A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101150146B1 (en) | System and method for managing cached objects using notification bonds | |
| CN109684285B (en) | User mode network file system file locking method, device and equipment | |
| CN111274214B (en) | File lock processing method and device, electronic equipment and storage medium | |
| US20070214143A1 (en) | NFS server, NFS server control program and NFS server control method | |
| CN111163159A (en) | Message subscription method, device, server and computer readable storage medium | |
| CN111258723B (en) | Transaction processing method, device, system, medium and equipment of distributed system | |
| CN113645152B (en) | Service degradation method and terminal | |
| CN111147560B (en) | Data synchronization method based on HTTP (hyper text transport protocol) and breakpoint continuous transmission | |
| CN114629883B (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN110727507B (en) | Message processing method and device, computer equipment and storage medium | |
| CN113535415B (en) | Resource acquisition method and terminal | |
| CN114598749B (en) | Service access method and device | |
| CN110430282B (en) | Data transmission method and device between nodes of distributed system | |
| CN101751292B (en) | Method for realizing consistency function of multimachine core data in ATC (automatic timing corrector) system | |
| CN107423454B (en) | Method, device and equipment for processing file lock in distributed file system | |
| CN114374657A (en) | Data processing method and device | |
| EP3758308A1 (en) | Correspondence processing method and device based on interworking rcs system | |
| US20140280347A1 (en) | Managing Digital Files with Shared Locks | |
| CN111339173A (en) | Data sharing method, server and readable storage medium | |
| CN112019452B (en) | Method, system and related device for processing service requirement | |
| CN116225726A (en) | Deadlock information collection method, storage medium and device for database cluster | |
| CN114095487B (en) | Remote task execution method, device and storage medium | |
| US20230044681A1 (en) | Udsf record retrieval and deletion | |
| CN113448710B (en) | Distributed application system based on business resources | |
| CN109213766B (en) | Data zero-delay processing method and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |