[
https://issues.apache.org/jira/browse/HDDS-1981?focusedWorklogId=299180&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-299180
]
ASF GitHub Bot logged work on HDDS-1981:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Aug/19 05:39
Start Date: 22/Aug/19 05:39
Worklog Time Spent: 10m
Work Description: bshashikant commented on issue #1319: HDDS-1981:
Datanode should sync db when container is moved to CLOSED or QUASI_CLOSED state
URL: https://github.com/apache/hadoop/pull/1319#issuecomment-523756239
Thanks @lokeshj1703 for working on this. I think running explicit compaction
before close might make it heavy operation. Can we run compaction in the
background or in a separate thread after closing the container?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 299180)
Time Spent: 1h 10m (was: 1h)
> 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
> Time Spent: 1h 10m
> 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]
