Client side backoff filter for rate limiting
US-2024314075-A1 · Sep 19, 2024 · US
US9317384B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9317384-B2 |
| Application number | US-201414578049-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 19, 2014 |
| Priority date | May 25, 2009 |
| Publication date | Apr 19, 2016 |
| Grant date | Apr 19, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Processing cache data includes sending a cache processing request to a master cache service node in a cache cluster that includes a plurality of cache service nodes, the cache cluster being configurable in an active cluster configuration mode wherein the plurality of cache service nodes are all in working state and a master cache service node is selected among the plurality of cache service nodes, or in a standby cluster configuration mode, wherein the master cache service node is the only node among the plurality of cache service nodes that is in working state. It further includes waiting for a response from the master cache service node, determining whether the master cache service node has failed; and in the event that the master cache service node has failed, selecting a backup cache service node.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: a cache client configured to: send a cache processing request to a master cache service node in a plurality of cache service nodes, wherein the cache processing request includes an operation; determine that the master cache service node has failed; and in response to the determination that the master cache service node has failed: select a backup cache service node from the plurality of cache service nodes to perform the cache processing request; send the cache processing request to the backup cache service node, wherein a task execution thread pool prevents one or more cache service nodes from the plurality of cache service nodes other than the backup cache service node from performing the operation; receive a successful operation result corresponding to the cache processing request from the backup cache service node; and in response to the successful operation result, store the operation and the successful operation result in a cluster operation task queue, wherein the operation and the successful operation result are to be copied from the cluster operation task queue to the master cache service node in the event that the master cache service node recovers from failure. 2. The system of claim 1 , wherein in response to the determination that the master cache service node has failed, the master cache service node is associated with a failure tag. 3. The system of claim 1 , wherein in response to the determination that the master cache service node has failed, the master cache service node is associated with a failure tag and set with a failure validity period. 4. The system of claim 1 , wherein in response to the determination that the master cache service node has failed, the cache client is further configured to: perform heartbeat detection on the master cache service node; and in the event that the master cache service node continues to fail, renew a failure state of the master cache service node. 5. The system of claim 1 , wherein the cache client is further configured to select the master cache service node from the plurality of cache service nodes by identifying cache service nodes that are not marked with failure tags. 6. The system of claim 1 , wherein the cache client is further configured to select the master cache service node from the plurality of cache service nodes by: querying at least a subset of the plurality of cache service nodes for a corresponding plurality of sets of parameters; combining each of the corresponding plurality of sets of parameters using weights corresponding to a set of parameters to obtain a corresponding calculation result; and selecting the master cache service node from the plurality of cache service nodes based at least in part on corresponding calculation results. 7. The system of claim 6 , wherein the set of parameters includes one or more of the following: a processing capacity index, a present total cache data volume, and a request response time. 8. The system of claim 1 , wherein the determination that the master cache service node has failed is based at least in part on a returned operation result received from the master cache service node. 9. A method, comprising: sending a cache processing request to a master cache service node in a plurality of cache service nodes, wherein the cache processing request includes an operation; determining that the master cache service node has failed; and in response to the determination that the master cache service node has failed: selecting a backup cache service node from the plurality of cache service nodes to perform the cache processing request; sending the cache processing request to the backup cache service node, wherein a task execution thread pool prevents one or more cache service nodes from the plurality of cache service nodes other than the backup cache service node from performing the operation; receiving a successful operation result corresponding to the cache processing request from the backup cache service node; and in response to the successful operation result, storing the operation and the successful operation result in a cluster operation task queue, wherein the operation and the successful operation result are to be copied from the cluster operation task queue to the master cache service node in the event that the master cache service node recovers from failure. 10. The method of claim 9 , wherein in response to the determination that the master cache service node has failed, the master cache service node is associated with a failure tag. 11. The method of claim 9 , wherein in response to the determination that the master cache service node has failed, the master cache service node is associated with a failure tag and set with a failure validity period. 12. The method of claim 9 , wherein in response to the determination that the master cache service node has failed, further comprising: performing heartbeat detection on the master cache service node; and in the event that the master cache service node continues to fail, renewing a failure state of the master cache service node. 13. The method of claim 9 , further comprising selecting the master cache service node from the plurality of cache service nodes by identifying cache service nodes that are not marked with failure tags. 14. The method of claim 9 , further comprising selecting the master cache service node from the plurality of cache service nodes by: querying at least a subset of the plurality of cache service nodes for a corresponding plurality of sets of parameters; combining each of the corresponding plurality of sets of parameters using weights corresponding to a set of parameters to obtain a corresponding calculation result; and selecting the master cache service node from the plurality of cache service nodes based at least in part on corresponding calculation results. 15. The method of claim 14 , wherein the set of parameters includes one or more of the following: a processing capacity index, a present total cache data volume, and a request response time. 16. The method of claim 9 , wherein the determination that the master cache service node has failed is based at least in part on a returned operation result received from the master cache service node. 17. A computer program product, wherein the computer program product is embodied in a non-transitory computer readable storage medium and comprises computer instructions for: sending a cache processing request to a master cache service node in a plurality of cache service nodes, wherein the cache processing request includes an operation; determining that the master cache service node has failed; and in response to the determination that the master cache service node has failed: selecting a backup cache service node from the plurality of cache service nodes to perform the cache processing request; sending the cache processing request to the backup cache service node, wherein a task execution thread pool prevents one or more cache service nodes from the plurality of cache service nodes other than the backup cache service node from performing the operation; receiving a successful operation result corresponding to the cache processing request from the backup cache service node; and in response to the successful operation result, storing the operation and the successful operation result in a cluster operation task queue, wherein the operation and the successful operation result are to be copied from the cluster operation task queue to the master cache service node in the event that
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
Electricity · mapped topic
Redundant storage or storage space (G06F11/2056 takes precedence) · CPC title
for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title
with a network or matrix configuration · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.