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

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

                Author: ASF GitHub Bot
            Created on: 05/Sep/19 10:53
            Start Date: 05/Sep/19 10:53
    Worklog Time Spent: 10m 
      Work Description: lokeshj1703 commented on issue #1375: HDDS-2048: State 
check during container state transition in datanode should be lock protected
URL: https://github.com/apache/hadoop/pull/1375#issuecomment-528309534
 
 
   @nandakumar131 Thanks for reviewing the PR! I have updated changes as per 
offline discussion.
 
----------------------------------------------------------------
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: 307063)
    Time Spent: 50m  (was: 40m)

> State check during container state transition in datanode should be lock 
> protected
> ----------------------------------------------------------------------------------
>
>                 Key: HDDS-2048
>                 URL: https://issues.apache.org/jira/browse/HDDS-2048
>             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: 50m
>  Remaining Estimate: 0h
>
> Currently container state checks during state transition are not lock 
> protected in KeyValueHandler. These can cause invalid state transitions.



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