[ 
https://issues.apache.org/jira/browse/HDDS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916872#comment-16916872
 ] 

Hudson commented on HDDS-1981:
------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17190 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17190/])
HDDS-1981: Datanode should sync db when container is moved to CLOSED or 
(github: rev 4379370fb1102de222b810b91e6b8c758a3affc2)
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/LevelDBStore.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/keyvalue/KeyValueContainer.java
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/RocksDBStore.java
* (edit) hadoop-hdds/common/src/main/proto/DatanodeContainerProtocol.proto
* (edit) 
hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/keyvalue/TestKeyValueContainerMarkUnhealthy.java
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/MetadataStore.java


> Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED 
> state
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-1981
>                 URL: https://issues.apache.org/jira/browse/HDDS-1981
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED 
> state. This will ensure that the metadata is persisted.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to