Systems and methods for strong write consistency when replicating data
A solid state drive is provided for improving write consistency when replicating data. The solid state drive includes a plurality of memory die, a host interface, and a memory controller. The memory controller is configured to receive write commands from a host server, update a list of write commands and a status of execution of the write commands to include the write commands from the host server, and write data payloads associated with the write commands to at least a first memory die and a second memory die of the plurality of memory die. In response to the data payloads being written, the memory controller is configured to update the status of execution for the data payloads in the list of write commands and receive an indication that the data payloads have been written to an external device.
1. A solid state drive for improving write consistency when replicating data, the solid state drive comprising:
a plurality of memory die;
a host interface; and
a memory controller, the memory controller configured to:
receive one or more write commands from a host server,
update a list of write commands and a status of execution of the write commands to include the one or more write commands from the host server,
write one or more data payloads associated with the one or more write commands, respectively, to at least a first memory die of the plurality of memory die and to a second memory die of the plurality of memory die,
in response to the one or more data payloads being written, update the status of execution for the one or more data payloads in the list of write commands,
receive an indication that the one or more data payloads have been written to an external device, and
in response to receiving the indication that one or more data payloads have been written to the external device, reallocate, as free memory, memory of the second memory die containing the one or more data payloads.
2. The solid state drive of claim 1 , wherein the external device is a remote server.
3. The solid state drive of claim 1 , wherein the host interface is further configured to:
write the one or more data payloads associated with the one or more write commands to the second memory die after the one or more data payloads associated with the one or more write commands have been written to the first memory die.
4. The solid state drive of claim 1 , wherein the host interface is further configured to detect a failure event.
5. The solid state drive of claim 4 , wherein, in response to detecting the failure event, the host interface is further configured to:
update the list to indicate the failure event; and
in response to detecting that the failure event occurred on the second memory die: retrieve the one or more data payloads associated with the one or more write commands from the first memory die, and
write the retrieved one or more data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.
6. The solid state drive of claim 4 , wherein, in response to detecting the failure event, the host interface is further configured to:
determine that the host server has experienced the failure event;
retrieve one or more data payloads associated with one or more write commands that have not been executed from the first memory die; and
write the one or more data payloads associated with the one or more write commands that have not been executed from the first die memory on an external solid state drive.
7. The solid state drive of claim 4 , wherein, in response to detecting the failure event, the host interface is further configured to:
determine a connection failure with an external device; and
write the data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.
8. The solid state drive of claim 4 , wherein, in response to detecting the failure event, the host interface is further configured to:
determine that an external device has experienced the failure event; and
write the data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.
9. A method for improving write consistency when replicating data, the method comprising:
receiving one or more write commands from a host server;
updating a list of write commands and a status of execution of the write commands to include the one or more write commands from the host server;
writing one or more data payloads associated with the one or more write commands, respectively, to at least a first memory die of the plurality of memory die and to a second memory die of the plurality of memory die;
in response to the one or more data payloads being written, updating the status of execution for the one or more data payloads in the list of write commands;
receiving an indication that the one or more data payloads have been written to an external device; and
in response to receiving the indication that one or more data payloads have been written to the external device, reallocating, as free memory, memory of the second memory die containing the one or more data payloads.
10. The method of claim 9 , wherein the external device is a remote server.
11. The method of claim 9 , further comprising:
writing the one or more data payloads associated with the one or more write commands to the second memory die after the one or more data payloads associated with the one or more write commands have been written to the first memory die.
12. The method of claim 9 , wherein the host interface is further configured to detect a failure event.
13. The method of claim 12 , further comprising:
in response to detecting the failure event:
updating the list to indicate the failure event, and
in response to detecting that the failure event occurred on the second memory die: retrieving the one or more data payloads associated with the one or more write commands from the first memory die, and
writing the retrieved one or more data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.
14. The method of claim 12 , further comprising:
in response to detecting the failure event:
determining that the host server has experienced the failure event,
retrieving one or more data payloads associated with one or more write commands that have not been executed from the first memory die, and
writing the one or more data payloads associated with the one or more write commands that have not been executed from the first die memory on an external solid state drive.
15. The method of claim 12 , further comprising:
in response to detecting the failure event:
determining a connection failure with an external device, and
writing the data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.
16. The method of claim 12 , further comprising:
in response to detecting the failure event:
determining that an external device has experienced the failure event, and
writing the data payloads associated with the one or more write commands to a third die memory in the plurality of die memory.