Write back coordination node for cache latency correction

• US 10,042,763 B2
• Filed: 06/19/2017
• Issued: 08/07/2018
• Est. Priority Date: 07/16/2014
• Status: Expired due to Fees

• Current Assignee: ClearSky Data Co.
• Original Assignee: ClearSky Data, Inc. (Amazon.com, Inc.)
• Inventors: Vekiarides, Lazarus, Suman, Daniel, Lacy, Janice Ann
• Primary Examiner(s): Bragdon, Reginald G
• Assistant Examiner(s): VO, THANH DUC
• Application Number:
  US15/626,714
• Publication Number:
  US 20180018261A1
• Time in Patent Office: 414 Days
• CPC Class Codes: G06F 12/0806 Multiuser, multiprocessor or multiprocessing cache systems
• CPC Class Codes: G06F 12/0811 with multilevel cache hierarchies
• CPC Class Codes: G06F 12/0897 with two or more cache hierarchy levels with multilevel cache hierarchies G06F12/0811
• CPC Class Codes: G06F 12/10 Address translation
• CPC Class Codes: G06F 2212/283 Plural cache memories
• CPC Class Codes: G06F 2212/62 Details of cache specific to multiprocessor cache arrangements

Abstract

A coordinating node acts as a write back cache, isolating local cache storage endpoints from latencies associated with accessing geographically remote cloud cache and storage resources.

Claims

1. A coordinator node apparatus for operating on data blocks comprising:

a first interface, connected to a cache storage endpoint over a first network connection;

a second interface, connected to cloud storage over a second network connection,

the first and second network connections further such that a physical distance between the coordinator node and the cache storage endpoint is shorter than a physical distance between the coordinator node and the cloud storage;

a third interface, connected to local storage;

a processor for

responding to a block write request from the cache storage endpoint as a write back cache, by acknowledging the block write request to the cache storage endpoint when a data block associated with the write request is not presently stored in the local storage;

maintaining a global Logical Block Address (LBA) metadata map; and

distributing the global LBA metadata map to the cache storage endpoint and to the cloud storage.

2. The apparatus of claim 1 wherein the first network connection to the storage endpoint is a local area network connection or a metropolitan area network connection.

3. The apparatus of claim 1 wherein the second network connection to the cloud storage is a wide area network connection.

4. The apparatus of claim 1 wherein a variability in latency associated with the first network connection is one-third or less of a variability in latency associated with the second network connection.

5. The apparatus of claim 3 wherein the cloud storage is provided by a service accessible over the wide area network connection.

6. The apparatus of claim 1 wherein the processor is further for:

storing the data block and metadata associated with the block write request in the local storage, and

forwarding the data block and metadata associated with the block write request to the cloud storage.

7. The apparatus of claim 1 wherein the processor is further for assigning a signature to a data block, and maintaining, in the global LBA metadata map, metadata that specifies (a) a mapping between at least one of LBAs and the signature, and (b) a mapping between the signature and a logical address for the data block.

8. The apparatus of claim 1 wherein the L2 storage endpoint comprises two or more devices each storing a portion of one or more LBAs assigned by the global LBA metadata map.

9. The apparatus of claim 1 wherein the processor further deduplicates the data block in the local storage before forwarding the data block to the cloud storage.

10. The apparatus of claim 1 wherein the processor further, upon receiving a read request from the storage endpoint, searches the local storage for a data block associated with the read request that may be stored from a prior write request before requesting the data block from the cloud storage.

11. The apparatus of claim 1 wherein the cache storage endpoint further operates as a write-through cache for access requests received from the local storage.

12. The apparatus of claim 11 wherein acknowledging the write request to the cache storage endpoint also isolates one or more local storage devices from a latency associated with storing the data associated with the write request to the cloud storage.

13. The apparatus of claim 1 wherein the processor further receives updates to the global LBA metadata map from the cache storage endpoint.

14. A method comprising:

accessing a local storage device providing a local cache;

connecting to a cache storage endpoint over a first network connection;

connecting to remote cloud storage over a second network connection;

the first and second network connections such that a physical distance between the local cache and the cache storage endpoint is shorter than a physical distance between the local cache and the cloud storage;

responding to a block write request from the cache storage endpoint as a write back cache, by acknowledging the block write request to the cache storage endpoint when a data block associated with the write request is not presently stored in the local cache;

maintaining a global logical block address (LBA) metadata map; and

distributing the global LBA metadata map to the cache storage endpoint and to the cloud storage.

15. The method of claim 14 wherein the first network connection is a local area network connection or a metropolitan area network connection.

16. The method of claim 14 wherein the second network connection is a wide area network connection.

17. The method of claim 16 wherein the cloud storage is provided by a service accessible over a wide area network connection.

18. The method of claim 14 wherein a latency associated with the first network connection varies over a time that is one-third or less of a time over which a latency associated with the second network connection varies.

19. The method of claim 14 further comprising step of:

storing the data block associated with the write request and block-related metadata in the local cache, before forwarding the data block associated with the write request and the block-related metadata to the cloud storage.

20. The method of claim 19 further comprising steps of:

assigning a signature to the data block; and

maintaining, in the global LBA metadata map, a mapping between at least one of LBAs and the signature, and a mapping between the signature and a logical address for the data block.

21. The method of claim 19 wherein the storage endpoint comprises two or more devices each such device further storing a portion of one or more LBAs assigned by the global LBA metadata map.

22. The method of claim 19 additionally comprising:

in response to the cache storage endpoint satisfying a write request, receiving updates to a portion of the global LBA metadata map from the cache storage endpoint.

23. The method of claim 14 further comprising:

deduplicating the data in the local cache before forwarding the data block associated with the write request to the cloud storage.

24. The method of claim 14 further comprising:

upon receiving a read request from the cache storage endpoint, searching the local cache for a data block associated with the read request that may be stored from a prior write request before requesting the data block from the cloud storage.

25. The method of claim 14 further comprising the step of:

at the cache storage endpoint, responding to write requests received from the local storage device as a write-through cache.

26. The method of claim 25 wherein acknowledging the write request to the cache storage endpoint also isolates one or more local storage devices from a latency associated with storing the data associated with the write request to the cloud storage.