[
https://issues.apache.org/jira/browse/HDDS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDDS-161:
-------------------------------------
Description:
When a container needs to be closed at the Datanode, SCM will queue a close
command which will be encoded as a part of Heartbeat Response to the Datanode.
This command will be picked up from the response at the Datanode which will
then be submitted to the XeiverServer to process the close command. This will
just queue a ContainerCloseCommand to the Ratis, where the leader would start
the transaction while the followers will reject the closeContainer request.
While handling the close container inaise the Datanode, we need to ensure all
the ongoing chunkWrites finish before close can proceeed through. It should
also reject any any incoming I/Os in between. This will be handled as a part of
separate jira.
was:When a container needs to be closed at the Datanode, SCM will queue a
close command which will be encoded as a part of Heartbeat Response to the
Datanode. This command will be picked up from the response at the Datanode
which will then be submitted to the XeiverServer to process the close command.
> Add functionality to queue ContainerClose command from SCM Hearbeat Reposnse
> to Ratis
> -------------------------------------------------------------------------------------
>
> Key: HDDS-161
> URL: https://issues.apache.org/jira/browse/HDDS-161
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
>
> When a container needs to be closed at the Datanode, SCM will queue a close
> command which will be encoded as a part of Heartbeat Response to the
> Datanode. This command will be picked up from the response at the Datanode
> which will then be submitted to the XeiverServer to process the close
> command. This will just queue a ContainerCloseCommand to the Ratis, where the
> leader would start the transaction while the followers will reject the
> closeContainer request.
> While handling the close container inaise the Datanode, we need to ensure all
> the ongoing chunkWrites finish before close can proceeed through. It should
> also reject any any incoming I/Os in between. This will be handled as a part
> of separate jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
