File change notifications in a scale-out NAS system

• US 9,591,059 B2
• Filed: 03/13/2013
• Issued: 03/07/2017
• Est. Priority Date: 03/13/2013
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ambach, Christian Markus Michael, Sahlberg, Ronnie Leif
• Primary Examiner(s): Christensen, Scott B
• Assistant Examiner(s): CONCANNON, SEAN D
• Application Number:
  US13/800,687
• Publication Number:
  US 20140280697A1
• Time in Patent Office: 1,455 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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]

Abstract

An apparatus for file change notifications includes a notification creation module that creates, on a first local node, a file change notification message in response to a client creating, deleting, and/or modifying a file system item addressed through a file path. The first local node notifies associated local client processes representing clients connected to the first local node and flagged to receive file change information. The apparatus includes a node identification module that checks a global node for second local nodes flagged to receive file change information for the file path and a notification distribution module that sends a file change notification message from the first local node to the second local nodes in response to receiving identification of the second local nodes. A second local node notifies associated local client processes representing clients connected to a second local node and flagged to receive change information for the file path.

Claims

1. An apparatus comprising:

a client registration module that;

receives a client file change notification request from a local client process at a local node, the client file change notification request specifying a file path and an identifier for the local client process such that a file change notification message is sent to the local client process in response to detecting a change in a directory specified by the file path;

performs a first flagging of a local client process at one or more of a first local node and one or more second local nodes to receive file change information in response to receiving the client file change notification request from a local client process at a local node without sending the file change notification request to a global node to reduce communications with the global node; and

creates an entry for the local client process in a local database of the first local node based on the client file change notification request, the local database comprising entries corresponding to the first flagging of the local client processes, the local database entry comprising the local client process identifier and the file path;

a node registration module that;

performs a second flagging of the first local node to receive file change information for a file path in response to the first flagging, the local client process being the first local client process of a plurality of local client processes associated with the local node flagged to receive file change information for the file path; and

creates an entry for the first local node in a global database of a global node in response to the second flagging, the global database comprising entries corresponding to the second flagging of the first local node, the global database entry comprising the local node identifier and the file path;

a notification creation module that;

detects by the first local node a file change that comprises a client one or more of creating, deleting, or modifying a file system item addressed through a file path; and

creates, on the first local node, a file change notification message in response to detecting the file change, the first local node sending the file change notification message to one or more local client processes flagged to receive file change information for the file path based on entries in the local database, wherein a local client process is associated with the first local node and represents a client connected to the first local node and wherein the file change notification message comprises information regarding a file change for the file path;

a node identification module that checks the global database of the global node to determine one or more second local nodes flagged to receive file change information for the file path, the one or more second local nodes different than the first local node;

a notification distribution module that sends a file change notification message from the first local node to the determined one or more second local nodes in response to receiving identification of the one or more second local nodes flagged to receive file change information for the file path, a second local node sending a file change notification message to one or more second local client processes flagged to receive file change information for the file path, the one or more second local client processes associated with the second local node and being different than the one or more local client processes associated with the first local node wherein a second local client process represents a client connected to a second local node;

a client deregistration module that;

receives, by the first local node, a client unflag request, the client unflag request specifying the file path and the identifier for the local client process such that delivery of the file change notification messages to the local client process in response to detecting a change in a directory specified by the file path ceases;

performs a first unflagging of a local client process at the first local node from receiving file change information for the file path in response to the client unflag request without sending the client unflag request to the global node; and

updates an entry for the local client process in the local database with a deletion marker and a first timestamp based on a determination that the local client process is the last local client process unflagged to receive file change notifications for the file path, the first timestamp indicating a time when the last local client process was unflagged to receive file change notifications for the file path, the entry being removed from the local database in response to expiration of a predetermined period of time after the time indicated by the first timestamp; and

a node deregistration module that;

performs a second unflagging of a local node from receiving file change information for a file path in response to the first unflagging, the local client process being the last local client process of a plurality of local client processes associated with the first local node unflagged to receive file change information for the file path; and

updates an entry for the first local node in the global database with a deletion marker and a second timestamp in response to the second unflagging, the second timestamp indicating a time when the last local node was unflagged to receive file change notifications for the file path, the entry being removed from the global database based on expiration of a predetermined period of time after the time indicated by the second timestamp,

wherein at least a portion of the said modules comprise one or more of hardware and executable code, the executable code stored on one or more non-transitory computer readable storage media.

2. The apparatus of claim 1, wherein the global node stores identification of the one or more second local nodes flagged to receive file change information without storing one or more of file change notification information and local client process information associated with the file change notification information.

3. The apparatus of claim 1, wherein the notification information comprises one or more of a local client process identifier, and one or more local client process attributes.

4. The apparatus of claim 1, wherein flagging a local node to receive file change information comprises storing identification information associated with the local node on a data store of the global node, the identification information comprising one or more of a file path, a local node name, and a local node number.

5. The apparatus of claim 1, further comprising a proxy module that receives a file change notification message from a first local node and sends the file change notification message to one or more local client processes flagged to receive file change information in response to receiving identification of one or more local client processes flagged to receive file change information.

6. The apparatus of claim 1, wherein the first local node, the global node, and the one or more second local nodes communicate over a network protocol, the network protocol comprising a server message block protocol.

7. A system comprising:

a first local node;

a global node;

one or more second local nodes, wherein the first local node, the global node, and the one or more second local nodes communicate over a network and each comprise a processor and an operating system executing on the processor;

a client registration module that;

receives a client file change notification request from a local client process at a local node, the client file change notification request specifying a file path and an identifier for the local client process such that a file change notification message is sent to the local client process in response to detecting a change in a directory specified by the file path;

performs a first flagging of a local client process at one or more of a first local node and one or more second local nodes to receive file change information in response to receiving the client file change notification request from a local client process at a local node without sending the file change notification request to a global node to reduce communications with the global node; and

creates an entry for the local client process in a local database of the first local node based on the client file change notification request, the local database comprising entries corresponding to the first flagging of the local client processes, the local database entry comprising the local client process identifier and the file path;

a node registration module that;

performs a second flagging of the first local node to receive file change information for a file path in response to the first flagging, the local client process being the first local client process of a plurality of local client processes associated with the local node flagged to receive file change information for the file path; and

creates an entry for the first local node in a global database of a global node in response to the second flagging, the global database comprising entries corresponding to the second flagging of the first local node, the global database entry comprising the local node identifier and the file path;

a notification creation module that;

detects by the first local node a file change that comprises a client one or more of creating, deleting, or modifying a file system item addressed through a file path; and

creates, on the first local node, a file change notification message in response to detecting the file change, the first local node sending the file change notification message to one or more local client processes flagged to receive file change information for the file path based on entries in the local database, wherein a local client process is associated with the first local node and represents a client connected to the first local node and wherein the file change notification message comprises information regarding a file change for the file path;

a node identification module that checks the global database of the global node to determine one or more second local nodes flagged to receive file change information for the file path, the one or more second local nodes different than the first local node;

a notification distribution module that sends a file change notification message from the first local node to the determined one or more second local nodes in response to receiving identification of the one or more second local nodes flagged to receive file change information for the file path, a second local node sending a file change notification message to one or more second local client processes flagged to receive file change information for the file path, the one or more second local client processes associated with the second local node and being different than the one or more local client processes associated with the first local node wherein a second local client process represents a client connected to a second local node;

a client deregistration module that;

receives, by the first local node, a client unflag request, the client unflag request specifying the file path and the identifier for the local client process such that delivery of the file change notification messages to the local client process in response to detecting a change in a directory specified by the file path ceases;

performs a first unflagging of a local client process at the first local node from receiving file change information for the file path in response to the client unflag request without sending the client unflag request to the global node; and

updates an entry for the local client process in the local database with a deletion marker and a first timestamp based on a determination that the local client process is the last local client process unflagged to receive file change notifications for the file path, the first timestamp indicating a time when the last local client process was unflagged to receive file change notifications for the file path, the entry being removed from the local database in response to expiration of a predetermined period of time after the time indicated by the first timestamp; and

a node deregistration module that;

performs a second unflagging of a local node from receiving file change information for a file path in response to the first unflagging, the local client process being the last local client process of a plurality of local client processes associated with the first local node unflagged to receive file change information for the file path; and

updates an entry for the first local node in the global database with a deletion marker and a second timestamp in response to the second unflagging, the second timestamp indicating a time when the last local node was unflagged to receive file change notifications for the file path, the entry being removed from the global database based on expiration of a predetermined period of time after the time indicated by the second timestamp,

wherein at least a portion of the said modules comprise one or more of hardware and executable code, the executable code stored on one or more non-transitory computer readable storage media.

8. The system of claim 7, further comprising a computer network that facilitates communication between one or more of the first local node, the global node, and the one or more second local nodes, the computer network comprising a server message block protocol.