Sand timer algorithm for tracking in-flight data storage requests for data replication

A system comprising:

• a memory;
• and
• at least one processor that is operatively coupled to the memory, the at least one processor being configured to perform the operations of:
• storing, in the memory, a pair of tracking tables, each of the tracking tables being arranged to alternate between a tracking table designation and a drain table designation, each of the tracking tables in the pair being arranged to have a different designation than the other tracking table in the pair;
• recording any incoming data storage requests in one of the tracking tables that is currently designated as an active tracking table;
• flipping the respective designations of the tracking tables;
• removing any remaining data storage requests, from one of the tracking tables that is currently designated as a drain table, when the remaining data storage requests are completed;
• transmitting, to a management node, a notification that one of the tracking tables that is currently designated as the drain table is empty, the notification being transmitted after all of the remaining data storage requests have been removed from one of the tracking tables that is currently designated as the drain table.

A non-transitory computer-readable medium configured to store one or more processor-executable instructions which when executed by at least one processor cause the at least one processor to perform the operations of:

• storing, in a memory of a storage node, a pair of tracking tables, each of the tracking tables being arranged to alternate between a tracking table designation and a drain table designation, each of the tracking tables in the pair being arranged to have a different designation than the other tracking table in the pair;
• recording all incoming data storage requests that are received at the storage node in one of the tracking tables that is currently designated as an active tracking table of the storage node;
• flipping the respective designations of the tracking tables;
• removing any remaining data storage requests, from one of the tracking tables that is currently designated as a drain table of the storage node, when the remaining data storage requests are completed;
• transmitting, to a management node, a notification that the drain table of the storage node is empty, the notification being transmitted after all of the remaining data storage requests have been removed from one of the tracking tables that is currently designated as the drain table of the storage node.