Methods and systems for mirroring and failover of nodes
A method for managing nodes includes detecting, by a failover node, a failure of a primary node, based on the detecting, updating a sparse virtual space to indicate that a file system previously local to the primary node is now local to the failover node, wherein the sparse virtual space is managed by a file system container executing on the failover node, and initiate execution of an instance of an application on the failover node, wherein a second instance of the application was previously executing on the primary node, and wherein the instance of the application uses the file system.
1. A method for managing nodes, comprising:
detecting, by a failover node, a failure of a primary node;
based on the detecting, updating a sparse virtual space to indicate that a file system previously local to the primary node is now local to the failover node, wherein the sparse virtual space is managed by a file system container executing on the failover node;
initiate execution of an instance of an application on the failover node, wherein a second instance of the application was previously executing on the primary node, and wherein the instance of the application uses the file system local to the failover node;
determining, after initiating execution of the instance of the application on the failover node, if the primary node is operational;
in response to determining that the primary node is not operational:
designating a new failover node; and
initiating mirroring of data written by the instance of the application to the file system to the new failover node;
in response to determining that the primary node is operational:
synchronizing data stored in the failover node with the primary node, wherein only the data written by the instance of the application to the file system local to the failover node while the primary node was not operational is written to the file system local to the primary node; and
updating the sparse virtual space to indicate that the file system previously local to the failover node is now remote to the failover node, wherein after the updating the file system is local to the primary node.
2. The method of claim 1 , further comprising:
in response to determining that the primary node is operational, ceasing execution of the instance of the application on the failover node.
3. The method of claim 1 , further comprising:
prior to detecting the failure:
receiving data from the primary node;
storing the data in a memory of the failover node.
4. The method of claim 1 , wherein detecting the failure comprises:
sending by the file system container a heartbeat message to the primary node; and
determining, after a period of time has elapsed, that no response was received from the primary node.
5. The method of claim 1 , wherein updating the sparse virtual space to indicate that the file system previously local to the primary node is now local to the failover node further comprises assuming a virtual address previously assumed by the primary node.
6. A non-transitory computer readable medium comprising instructions which, when executed by a computer processor, enables the computer processor to perform a method for processing requests, the method comprising:
detecting, by a failover node, a failure of a primary node;
based on the detecting, updating a sparse virtual space to indicate that a file system previously local to the primary node is now local to the failover node, wherein the sparse virtual space is managed by a file system container executing on the failover node;
initiate execution of an instance of an application on the failover node, wherein a second instance of the application was previously executing on the primary node, and wherein the instance of the application uses the file system local to the failover node;
determining, after initiating execution of the instance of the application on the failover node, if the primary node is operational;
in response to determining that the primary node is not operational:
designating a new failover node; and
initiating mirroring of data written by the instance of the application to the file system to the new failover node;
in response to determining that the primary node is operational:
synchronizing data stored in the failover node with the primary node, wherein only the data written by the instance of the application to the file system local to the failover node while the primary node was not operational is written to the file system local to the primary node; and
updating the sparse virtual space to indicate that the file system previously local to the failover node is now remote to the failover node, wherein after the updating the file system is local to the primary node.
7. The non-transitory computer readable medium of claim 6 , the method further comprising:
in response to determining that the primary node is operational, ceasing execution of the instance of the application on the failover node.
8. The non-transitory computer readable medium of claim 6 , the method further comprising:
prior to detecting the failure:
receiving data from the primary node; and
storing the data in a memory of the failover node.
9. The non-transitory computer readable medium of claim 6 , wherein detecting the failure comprises:
sending by the file system container a heart beat message to the primary node; and
determining, after a period of time has elapsed, that no response was received from the primary node.
10. The non-transitory computer readable medium of claim 6 , wherein updating the sparse virtual space to indicate that the file system previously local to the primary node is now local to the failover node further comprises assuming a virtual address previously assumed by the primary node.
11. A failover node, comprising:
memory; and
a processor, wherein the processor is configured to:
detect a failure of a primary node;
based on the detecting, updating a sparse virtual space to indicate that a file system previously local to the primary node is now local to the failover node, wherein the sparse virtual space is managed by a file system container executing on the failover node;
initiate execution of an instance of an application on the failover node, wherein a second instance of the application was previously executing on the primary node, and wherein the instance of the application uses the file system local to the failover node;
determining, after initiating execution of the instance of the application on the failover node, if the primary node is operational;
in response to determining that the primary node is not operational:
designating a new failover node; and
initiating mirroring of data written by the instance of the application to the file system to the new failover node;
in response to determining that the primary node is operational:
synchronizing data stored in the failover node with the primary node, wherein only the data written by the instance of the application to the file system local to the failover node while the primary node was not operational is written to the file system local to the primary node; and
updating the sparse virtual space to indicate that the file system previously local to the failover node is now remote to the failover node, wherein after the updating the file system is local to the primary node.
12. The failover node of claim 11 , further programmed to:
in response to determining that the primary node is operational, ceasing execution of the instance of the application on the failover node.
13. The failover node of claim 12 , further programmed to:
prior to detecting the failure:
receive data from the primary node;
store the data in the memory.
14. The failover node of claim 11 , wherein detecting the failure comprises:
sending by the file system container a heart beat message to the primary node;
determining, after a period of time has elapsed, that no response was received from the primary node.