Methods and systems parallel raid rebuild in a distributed storage system
A method for rebuilding data, comprising: obtaining, from a metadata node, a source file data layout for a source file and a target file data layout for a target file, wherein the source file is associated with a degraded mapped RAID group and the target file is associated with a new mapped RAID group; generating, by the client application node, a plurality of input/output (I/O) requests to read a portion of the data associated with the source file using the source file data layout; obtaining, in response to the plurality of I/O requests, the portion of the data associated with the source file; rebuilding a second portion of the data associated with source file using the portion of the data; and initiating, storage of at least the second portion of the data associated with the source file in the storage pool using the target file data layout.
1. A method for rebuilding data, the method comprising:
obtaining, from a metadata node and by file system (FS) client executing on a client application node, a source file data layout for a source file and a target file data layout for a target file, wherein the source file is associated with a degraded mapped RAID group and the target file is associated with a new mapped RAID group;
generating, by a memory hypervisor module executing on the client application node, a plurality of input/output (I/O) requests to read a portion of the data associated with the source file using the source file data layout;
issuing, by the memory hypervisor module, the plurality of I/O requests to a storage pool;
obtaining, by the client application node and in response to the plurality of I/O requests, the portion of the data associated with the source file;
rebuilding a second portion of the data associated with source file using the portion of the data associated with the source file;
initiating, using the memory hypervisor, storage of at least the second portion of the data associated with the source file in the storage pool using the target file data layout,
wherein a second client application is able to obtain read only access to the data associated with the source file during the rebuilding; and
issuing, by the client application node, a notification to the metadata node that the rebuilding of the target file is completed after at least the second portion of the data is stored in the storage pool.
2. The method of claim 1 , wherein the metadata node, after receiving the notification, permits the second client application to obtain read write access to the data using the target file data layout.
3. The method of claim 1 , wherein the degraded mapped RAID group comprises a plurality of memory devices, wherein at least one of the plurality of memory devices in the degraded mapped RAID group has failed, and wherein the portion of the data is obtained from the plurality of memory devices that have not failed.
4. The method of claim 3 , wherein the second portion of the data corresponds to data that was previously stored on the at least one of the plurality of memory devices in the degraded mapped RAID group that has failed.
5. The method of claim 3 , wherein the storage pool comprises the plurality of memory devices, wherein a memory device of the plurality of memory devices is located on a storage node and a second memory device of the plurality of memory devices is located on the client application node.
6. The method of claim 5 , wherein at least one of the plurality of I/O requests is issued directly to the storage node and is not processed by the metadata node.
7. The method of claim 3 , wherein at least one of the plurality the memory devices is a persistent memory (PMEM) device.
8. A non-transitory computer readable medium comprising instructions which, when executed by a processor, enables the processor to perform a method for rebuilding data, the method comprising:
obtaining, from a metadata node and by file system (FS) client executing on a client application node, a source file data layout for a source file and a target file data layout for a target file, wherein the source file is associated with a degraded mapped RAID group and the target file is associated with a new mapped RAID group;
generating, by a memory hypervisor module executing on the client application node, a plurality of input/output (I/O) requests to read a portion of the data associated with the source file using the source file data layout,
issuing, by the memory hypervisor module, the plurality of I/O requests to a storage pool;
obtaining, by the client application node and in response to the plurality of I/O requests, the portion of the data associated with the source file;
rebuilding a second portion of the data associated with source file using the portion of the data associated with the source file;
initiating, using the memory hypervisor, storage of at least the second portion of the data associated with the source file in the storage pool using the target file data layout,
wherein a second client application is able to obtain read only access to the data associated with the source file during the rebuilding; and
issuing, by the client application node, a notification to the metadata node that the rebuilding of the target file is completed after at least the second portion of the data is stored in the storage pool.
9. The non-transitory computer readable medium of 8 , wherein the metadata node, after receiving the notification, permits the second client application to obtain read write access to the data using the target file data layout.
10. The non-transitory computer readable medium of 8 , wherein the degraded mapped RAID group comprises a plurality of memory devices, wherein at least one of the plurality of memory devices in the degraded mapped RAID group has failed, and wherein the portion of the data is obtained from the plurality of memory devices that have not failed.
11. The non-transitory computer readable medium of 10 , wherein the second portion of the data corresponds to data that was previously stored on the at least one of the plurality of memory devices in the degraded mapped RAID group that has failed.
12. The non-transitory computer readable medium of 10 , wherein the storage pool comprises the plurality of memory devices, wherein a memory device of the plurality of memory devices is located on a storage node and a second memory device of the plurality of memory devices is located on the client application node.
13. The non-transitory computer readable medium of 12 , wherein at least one of the plurality of I/O requests is issued directly to the storage node and is not processed by the metadata node.
14. The non-transitory computer readable medium of 10 , wherein at least one of the plurality the memory devices is a persistent memory (PMEM) device.
15. A node, comprising;
memory;
a processor, wherein the processor is configured to:
obtain, from a metadata node and by file system (FS) client executing on a client application node, a source file data layout for a source file and a target file data layout for a target file, wherein the source file is associated with a degraded mapped RAID group and the target file is associated with a new mapped RAID group;
generate, by a memory hypervisor module executing on the client application node, a plurality of input/output (I/O) requests to read a portion of the data associated with the source file using the source file data layout;
issue, by the memory hypervisor module, the plurality of I/O requests to a storage pool;
obtain, by the client application node and in response to the plurality of I/O requests, the portion of the data associated with the source file;
rebuild a second portion of the data associated with source file using the portion of the data associated with the source file;
initiate, using the memory hypervisor, storage of at least the second portion of the data associated with the source file in the storage pool using the target file data layout,
wherein a second client application is able to obtain read only access to the data associated with the source file during the rebuilding; and
issue, by the client application node, a notification to the metadata node that the rebuilding of the target file is completed after at least the second portion of the data is stored in the storage pool.
16. The node of claim 15 ,
wherein the metadata node, after receiving the notification, permits the second client application to obtain read write access to the data using the target file data layout.
17. The node of claim 15 ,
wherein the degraded mapped RAID group comprises a plurality of memory devices,
wherein at least one of the plurality of memory devices in the degraded mapped RAID group has failed, and wherein the portion of the data is obtained from the plurality of memory devices that have not failed.
18. The node of claim 17 ,
wherein the second portion of the data corresponds to data that was previously stored on the at least one of the plurality of memory devices in the degraded mapped RAID group that has failed.