[
https://issues.apache.org/jira/browse/HDDS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supratim Deka resolved HDDS-1740.
---------------------------------
Resolution: Not A Problem
On the Datanode, Container state changes are driven through
KeyValueContainer.updateContainerData()
this always resets the in-memory state of the container to the previous state
in case the update to the container YAML hits any exception. Also, the
container YAML is sync flushed to persistent storage as implemented in:
ContainerDataYAML.createContainerFile()
So I am marking this as not a problem.
> Handle Failure to Update Ozone Container YAML
> ---------------------------------------------
>
> Key: HDDS-1740
> URL: https://issues.apache.org/jira/browse/HDDS-1740
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
>
> Ensure consistent state in-memory and in the persistent YAML file for the
> Container.
> If an update to the YAML fails, then the in-memory state also does not change.
> This ensures that in every container report, the SCM continues to see the
> specific container is still in the old state. And this triggers a retry of
> the state change operation from the SCM.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
