Transparent failover

• US 8,856,582 B2
• Filed: 06/30/2011
• Issued: 10/07/2014
• Est. Priority Date: 06/30/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: George, Mathew, Kruse, David M., Pinkerton, James T., Battepati, Roopesh C., Jolly, Tom, Swan, Paul R., Shang, Mingdong, Lovinger, Daniel Edward
• Primary Examiner(s): MASKULINSKI, MICHAEL C
• Application Number:
  US13/174,271
• Publication Number:
  US 20130007518A1
• Time in Patent Office: 1,195 Days
• Field of Search: 714/4.11, 714/15
• US Class Current: 714/4.11
• CPC Class Codes: G06F 11/1443 Transmit or communication errors
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Claims

1. A computer implemented method of providing consistent availability to clients accessing a shared file system on a server cluster, the method comprising:

receiving at a file server a request to connect to the file server to access file information in a shared file system, the request to connect being formatted according to a file access protocol, wherein the file server is one of a plurality of servers in a server cluster;

sending a first response from the file server, the first response establishing a session with a client for allowing access to file information in the shared file system, the first response being formatted according to the file access protocol;

receiving a request at the file server to open a persistent handle on the file server for accessing a file in the shared file system by the client, the request to open a persistent handle including a handle identifier provided by the client;

in response to receiving the request to open a persistent handle, the file server;

storing first state information about the session in association with the handle identifier; and

sending a second response to the client granting access to the file;

after a client disconnect, receiving a request to reestablish the session using the persistent handle;

reestablishing the session using the first state information;

after reestablishing the session, receiving a new request from the client, the new request including the handle identifier;

determining, using the handle identifier, that the new request is a replay of a previously sent request.

2. The method of claim 1, wherein the first state information comprises state of an operation that if resent by the client causes the file server to end up in an inconsistent state.

3. The method of claim 2, wherein the file access protocol is a version of the Server Message Block (SMB) protocol.

4. The method of claim 3, wherein the first state information comprises state of one or more of:

byte range locks held by the client and create operations sent by the client.

5. The method of claim 3, further comprising:

before the client disconnect, registering with a resume filter to store second state information regarding the session.

6. The method of claim 5, wherein the second state information comprises state of one or more of:

leases held by the client and opens held by the client.

7. The method of claim 5, wherein the reestablishing the session further comprises using the second state information.

8. The method of claim 1, wherein the client disconnect occurs because of a failure of the file server and the reestablishing the connection is performed by a second file server in the server cluster.

9. A computer readable storage medium comprising computer executable instructions that when executed by a processor perform a method of maintaining consistent state, the method comprising:

sending a request by a client to connect to a server to access file information, the request to connect being formatted according to a file access protocol;

receiving a first response from the server, the first response establishing a session with the client for allowing access to file information on the server, the first response being formatted according to the file access protocol;

sending a request to open a persistent handle on the server for accessing a file on the server by the client, the request to open a persistent handle including a handle identifier provided by the client;

receiving a second response at the client granting access to the file;

detecting that the client has been disconnected from the server;

sending a request to reestablish the session using the persistent handle, the request to reestablish the session including the handle identifier;

determining that the session has been reestablished;

sending a new request; and

after the session is reestablished, determining that the new request is a replay of a previously sent request.

10. The computer readable storage medium of claim 9, wherein the server is one of a plurality of servers in a server cluster, and the disconnection occurs because of a failure of the server, wherein the reestablishing the session is performed by a second server of the plurality of servers in the server cluster.

11. The computer readable storage medium of claim 10, wherein the file access protocol is a version of the Server Message Block (SMB) protocol.

12. The computer readable storage medium of claim 9, wherein the new request comprises the handle identifier and is a replay of a request for one or more of:

a byte range lock held by the client before the disconnection and a create request sent by the client before the disconnection.

13. A system of providing consistent availability to clients accessing a shared file system on a server cluster, the system comprising:

at least one processor;

memory, operatively coupled to the at least one processor and containing instructions that, when executed by the at least one processor, cause the at least one processor to perform a method, the method comprising;

receiving at a file server a request to connect to the file server to access file information in a shared file system, the request to connect being formatted according to a file access protocol, wherein the file server is one of a plurality of servers in a server cluster;

sending a first response from the file server, the first response establishing a session with a client for allowing access to file information in the shared file system, the first response being formatted according to the file access protocol;

receiving a request at the file server to open a persistent handle on the file server for accessing a file in the shared file system by the client, the request to open a persistent handle including a handle identifier provided by the client;

in response to receiving the request to open a persistent handle, the file server;

storing first state information about the session in association with the handle identifier; and

sending a second response to the client granting access to the file;

after a client disconnect, receiving a request to reestablish the session using the persistent handle;

reestablishing the session using the first state information;

after reestablishing the session, receiving a new request from the client, the new request including the handle identifier;

determining, using the handle identifier, that the new request is a replay of

14. The system of claim 13, wherein the first state information comprises state of an operation that if resent by the client causes the file server to end up in an inconsistent state.

15. The system of claim 14, wherein the file access protocol is a version of the Server Message Block (SMB) protocol.

16. The system of claim 15, wherein the first state information comprises state of one or more of:

byte range locks held by the client and create operations sent by the client.

17. The system of claim 15, further comprising:

before the client disconnect, registering with a resume filter to store second state information regarding the session.

18. The system of claim 17, wherein the second state information comprises state of one or more of:

leases held by the client and opens held by the client.

19. The system of claim 17, wherein the reestablishing the session further comprises using the second state information.

20. The system of claim 13, wherein the client disconnect occurs because of a failure of the file server and the reestablishing the connection is performed by a second file server in the server cluster.