Distributed filesystem atomic flush transactions

• US 10,440,141 B2
• Filed: 10/05/2017
• Issued: 10/08/2019
• Est. Priority Date: 06/29/2012
• Status: Active Grant

• Current Assignee: William M. Pitts
• Original Assignee: William M. Pitts
• Inventors: Pitts, William M
• Primary Examiner(s): Mejia, Anthony
• Assistant Examiner(s): Boustany, Jihad K
• Application Number:
  US15/726,116
• Publication Number:
  US 20180048733A1
• Time in Patent Office: 733 Days
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 65/40 Support for services or applications
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Large scale high performance file proxy caching sites may be configured to coalesce many client write operations into one very large assemblage of modified file data. At some point the caching site will flush all modified file data downstream towards the origin file server. In some instances the amount of modified data being flushed may be more than can be transferred in a single network request. When multiple network requests are required, the consistency guarantee provided by many filesystems requires that the file either be updated with the data contained in all of the network requests or not be modified at all. In addition, once the first flush request is processed no other file read or write requests can be serviced until the last flush request has been processed. This document discloses methods for performing atomic multi-request flush operations within a large geographically distributed filesystem environment.

Claims

1. A networked computing system where a file access request has been passed between an upstream site and a file service proxy cache node, the networked computing system comprising:

an upstream site, the upstream site including;

one or more hardware processors;

system memory coupled to the one or more hardware processors, the system memory storing instructions that are executable by the one or more hardware processors;

the one or more hardware processors executing the instructions stored in the system memory to flush modified file data downstream towards an origin file server, including the following;

acquire a site channel containing modified file data, the site channel bound into a single integrated channel traversing one or more file service proxy cache nodes through which the flush request will pass; and

prepare a flush request, the flush request;

being an atomic operation;

including a file access request, wherein the file access request includes making modifications to a file located on the origin file server; and

including modified file data to save to a stable memory, wherein;

 

the modified file data is sent in multiple network flush requests; and

 

each flush request is uniquely identified; and

 

the last flush request of the atomic operation is identified with a flag referred to as DATA_COMPLETE; and

 

each flush request includes at least one modified file extent;

the one or more file service proxy cache nodes, each file service proxy cache node;

being a network node located between the upstream site and the origin file server node; and

including;

one or more hardware processors;

system memory coupled to the one or more hardware processors, the system memory storing instructions that are executable by the one or more hardware processors;

the one or more hardware processors executing the instructions stored in the system memory to complete a flush request, including the following;

receive the flush request from the upstream site;

store each received modified file extent in a first shadow extent referenced by the site channel, wherein the shadow extent is a temporary buffer;

dispatch the received flush request containing the modified file extents to a downstream node, wherein the downstream node includes at least one of;

 

a file service proxy cache node closer to the origin file server node;

or

 

the origin file server node; and

the origin file server node including;

one or more hardware processors;

system memory coupled to the one or more hardware processors, the system memory storing instructions that are executable by the one or more hardware processors;

the one or more hardware processors executing the instructions stored in the system memory to complete a flush request, including the following;

receive the flush request from the file service proxy cache node located upstream of the origin file server node;

store each received modified file extent in a second shadow extent referenced by the site channel, wherein the shadow extent is a temporary buffer;

if the flush request contains a DATA_COMPLETE flag;

 

write all shadow extents to the origin filesystem; and

 

if all shadow extents are successfully written to the origin filesystem;

 

replace all extents that have shadow extents with their respective shadow extent; and

 

send a response to the file service proxy cache node located upstream of the origin file server node that includes a flag referred to as ALL_DATA_RECEIVED that indicates all data was successfully received; and

 

send a first status code, wherein the first status code indicates the successful completion of the flush request;

 

if all shadow extents are not successfully written to the origin filesystem;

 

discard all shadow extents; and

 

send a response to the file service proxy cache node located upstream of the origin file server node that includes a second status code, wherein the second status code indicates the failure of the flush request;

if the flush request does not contain a DATA_COMPLETE flag;

 

send a response to the file service proxy cache node located upstream of the origin file server node that includes the first status code, wherein the first status code indicates the successful completion of the flush request; and

wherein each of the file service proxy cache nodes and the upstream site;

receive a flush request response from the downstream node, the response including a status code, wherein the status code includes at least one of;

the first status code;

or

the second status code;

replace all extents that have shadow extents with their respective shadow extent when the status code is the first status code;

delete all modified file data saved to the shadow extents when the status code is the second status code; and

wherein each of the file service proxy cache nodes;

send a response to an upstream node, wherein;

the upstream node includes at least one of;

a file service proxy cache node closer to the upstream site;

or

the upstream site; and

the response includes at least one of;

the first status code;

or

the second status code.

2. The system of claim 1, wherein the instructions stored in the system memory of the upstream site is the same as:

the instructions stored in the system memory of each of the one or more file service proxy cache nodes; and

the instructions stored in the system memory of the origin file server node.

3. The system of claim 2, wherein the flush request includes a flush level, the flush level indicating the class of memory to which the flush data will be propagated.

4. The system of claim 3, wherein the flush level specifies the file service proxy cache node'"'"'s cache memory as the flush destination.

5. The system of claim 3, wherein the flush level specifies the file service proxy cache node'"'"'s persistent memory as the flush destination.

6. The system of claim 3, wherein the flush level specifies the file on the origin file server node as the flush destination.

7. The system of claim 3, wherein when the flush level specifies a file service proxy cache node'"'"'s cache memory or persistent memory, the file service proxy cache node operates as the origin file server node.

8. The system of claim 1 further comprising:

when the file service proxy cache node receives a response to the flush request;

the file service proxy cache node remaining committed to the upstream site by only accepting and processing file access requests targeting the file from the upstream site when an ALL_DATA_RECEIVED response flag is not set, indicating that the origin file server node has not received and accepted all flush data.