Abstract: Each node of a storage cluster determines its capabilities and advertises the set of capabilities along with respective capability weights to other nodes of the storage cluster. Nodes monitor their systems for capability changes and, as capabilities of the nodes dynamically change, the dynamic changes to the node capabilities are similarly advertised. The advertised capabilities are passed to a cluster service manager which creates capabilities groups based on the advertised capabilities of the nodes. When a service is deployed to the storage cluster or moved within the cluster, the cluster service manager determines the set of required capabilities associated with the service, and uses the capabilities groups to identify nodes of the storage cluster for implementation of the service. Where more than one node has advertised the required sets of capabilities, the weights are used in an election process to determine which node should be used to implement the service.

Abstract: Each node of a storage cluster determines its capabilities and advertises the set of capabilities along with respective capability weights to other nodes of the storage cluster. Nodes monitor their systems for capability changes and, as capabilities of the nodes dynamically change, the dynamic changes to the node capabilities are similarly advertised. The advertised capabilities are passed to a cluster service manager which creates capabilities groups based on the advertised capabilities of the nodes. When a service is deployed to the storage cluster or moved within the cluster, the cluster service manager determines the set of required capabilities associated with the service, and uses the capabilities groups to identify nodes of the storage cluster for implementation of the service. Where more than one node has advertised the required sets of capabilities, the weights are used in an election process to determine which node should be used to implement the service.

Abstract: Actual files, which may comprise objects, are stored from a high-performance cluster storage of a first system to a lower performance storage of a remote second computing system as a backup. A set of proxy files, which point to locations of the actual files within the backup, is created that may be stored to a cluster storage system, or to the lower performance storage, at the remote second computing system. A user, or application, of the first system may access an actual file from the backup that is pointed to in a corresponding proxy file. The actual file accessed from the backup may be stored to a new location at a cluster storage to facilitate future access requests made before the actual file is restored from the backup to the first system. The proxy file corresponding to the accessed file may point to the new location of the retrieved file.

Abstract: Facilitating antivirus scan filing locking based on cluster lock mechanism in distributed file systems is provided herein. A system comprises a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations comprise determining an antivirus scan status of an object, based on an open object request received from a node device of a cluster of node devices, which is determined through the use of Lock Value Blocks. The antivirus scanning of the object is a precondition for opening the object. The antivirus scan status of the object is one of an unscanned status, a queued status, or a scanned status. Further, the operations can comprise, based on the antivirus scan status being the queued status or the scanned status, selectively facilitating the opening of the object at the node device while circumventing the precondition.

Abstract: Facilitating the implementation of cluster counters on lock value blocks in distributed file systems is provided herein. A system comprises a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations comprise receiving, from a first node device of a group of node devices, first information indicative of a first lock value block status of an object, and, from a second node device of the group of node devices, second information indicative of a second lock value block status of the object. The operations also can comprise merging the first information and the second information, resulting in a status of a lock value block of the object implemented at respective node devices of the group of node devices.

Abstract: Facilitating antivirus scan filing locking based on cluster lock mechanism in distributed file systems is provided herein. A system comprises a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations comprise determining an antivirus scan status of an object, based on an open object request received from a node device of a cluster of node devices, which is determined through the use of Lock Value Blocks. The antivirus scanning of the object is a precondition for opening the object. The antivirus scan status of the object is one of an unscanned status, a queued status, or a scanned status. Further, the operations can comprise, based on the antivirus scan status being the queued status or the scanned status, selectively facilitating the opening of the object at the node device while circumventing the precondition.

Abstract: Implementations are provided herein for non-disruptive upgrade including rollback capabilities for a distributed file system within a cluster of nodes. To continue availability of the file system to external clients during the upgrade process, nodes can be upgraded piecemeal, for example, in one implementation, one node at a time. When a node is undergoing certain stages of the upgrade process, external clients can be directed toward the remaining nodes of the file system that are not currently being upgraded, including already upgraded nodes, to perform client activity. During the upgrade process, a first subset of nodes can be running in an upgraded state while a second subset of nodes can be in a non-upgraded state, both providing access to external clients in a seamless manner. In one implementation, a second namespace can be established at the onset of the upgrade process that reflects the new version of the operating system.