Cache data processing using cache cluster with configurable modes

• US 20100299553A1
• Filed: 05/19/2010
• Published: 11/25/2010
• Est. Priority Date: 05/25/2009
• Status: Active Grant

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Cen, Wenchu
• Granted Patent: US 8,972,773 B2
• Time in Patent Office: Days
• US Class Current: 714/4.1
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 12/0811 with multilevel cache hierarchies
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 2212/1016 Performance improvement
• CPC Class Codes: G06F 2212/261 Storage comprising a plurality of storage devices
• CPC Class Codes: G06F 2212/283 Plural cache memories
• CPC Class Codes: G06F 2212/284 being distributed
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/40 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

Abstract

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.

Claims

1. A method for processing cache data, comprising:

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;

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.

2. The method of claim 1, wherein determining whether the master cache service node has failed includes comparing a failure count with a threshold.

3. The method of claim 1, in the event that the master cache service node has failed, further comprising associating the master cache service node with a failure tag.

4. The method of claim 1, in the event that the master cache service node has failed, further comprising associating the master cache service node with a failure tag, and setting a failure validity period of the master cache service node.

5. The method of claim 1, wherein selecting the backup cache service node includes:

identifying available cache service nodes in the cluster are not marked with failure tags; and

selecting the backup cache service node among the available cache service nodes.

6. The method of claim 1, further comprising waiting for a response from the back up cache service node.

7. The method of claim 1, wherein prior to sending the cache processing request to the master cache service node, the method further comprising:

identifying available cache service nodes that are not marked with failure tags; and

selecting the master cache service node among the available cache service nodes.

8. The method of claim 1, wherein sending the cache processing request and waiting for the response are performed asynchronously.

9. The method of claim 1, 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 failure state of the master cache service node.

10. A caching system comprising:

a cache cluster comprising 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; and

a cache client configured to;

send a cache processing request to the master cache service node;

wait for a response from the master cache service node;

determine whether the master cache service node has failed; and

in the event that the master cache service node has failed, select a backup cache service node.

11. The system of claim 10, wherein determining whether the master cache service node has zo failed includes comparing a failure count with a threshold.

12. The method of claim 10, in the event that the master cache service node has failed, the cache client is further configured to cause the master cache service node to be associated with a failure tag.

13. The system of claim 10, in the event that the master cache service node has failed, the cache client is further configured to cause the master cache service node to be associated with a failure tag and a failure validity period.

14. The system of claim 10, wherein selecting the backup cache service node includes:

identifying available cache service nodes in the cluster are not marked with failure tags;

selecting the backup cache service node among the available cache service nodes.

15. The system of claim 10, wherein the cache client is further configured to wait for a response from the back up cache service node.

16. The system of claim 10, wherein prior to sending the cache processing request to the master cache service node, the cache client is further configured to:

identify available cache service nodes that are not marked with failure tags; and

select the master cache service node among the available cache service nodes.

17. The system of claim 10, wherein sending the cache processing request and waiting for the response are performed asynchronously.

18. The system of claim 10, wherein 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 failure state of the master cache service node.