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

ASF GitHub Bot logged work on HDDS-1981:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Aug/19 12:56
            Start Date: 22/Aug/19 12:56
    Worklog Time Spent: 10m 
      Work Description: lokeshj1703 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-523893866
 
 
   @supratimdeka Thanks for reviewing the PR! I have pushed a commit addressing 
your comments.
   @bshashikant Can we address the compaction issue in another jira?
 
----------------------------------------------------------------
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: 299416)
    Time Spent: 1h 40m  (was: 1.5h)

> 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 40m
>  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