US 12,443,494 B2
Prevention of residual data writes after non-graceful node failure in a cluster
Clinton Douglas Knight, Apex, NC (US); Joseph Eli Webster, Wichita, KS (US); and Christopher Michael Reeder, Everett, WA (US)
Assigned to NetApp, Inc., San Jose, CA (US)
Filed by NetApp, Inc., San Jose, CA (US)
Filed on Mar. 12, 2024, as Appl. No. 18/602,963.
Prior Publication US 2025/0291685 A1, Sep. 18, 2025
Int. Cl. G06F 11/00 (2006.01); G06F 11/16 (2006.01); G06F 11/18 (2006.01); G06F 11/20 (2006.01); H04L 65/00 (2022.01); H04L 67/00 (2022.01)
CPC G06F 11/181 (2013.01) [G06F 11/16 (2013.01); G06F 11/1666 (2013.01); G06F 11/20 (2013.01); G06F 11/2017 (2013.01); H04L 65/00 (2013.01); H04L 67/00 (2013.01)] 20 Claims
OG exemplary drawing
 
11. A system for protecting data from a non-graceful node failure in a cluster of computing nodes, the system comprising:
a storage system storing a plurality of storage volumes;
a controller for a storage orchestrator executing on a controller node of the computing nodes; and
a plurality of servers for the storage orchestrator executing on a plurality of the computing nodes, wherein the plurality of computing nodes is configured to execute one or more pods that access the storage system, wherein,
the controller is configured to determine a node in the cluster has failed and mark the node as dirty;
a server of the plurality of servers executing on the node is configured to send, to the controller, a request for mounting of a storage volume of the plurality of storage volumes while the node is marked as dirty,
the controller is configured to reject the request and direct the server to erase a write buffer on the node, and
the server is configured to erase the write buffer in response to direction from the controller.