[
https://issues.apache.org/jira/browse/HDDS-2198?focusedWorklogId=319744&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-319744
]
ASF GitHub Bot logged work on HDDS-2198:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Sep/19 18:44
Start Date: 27/Sep/19 18:44
Worklog Time Spent: 10m
Work Description: nandakumar131 commented on pull request #1540:
HDDS-2198. SCM should not consider containers in CLOSING state to come out of
safemode.
URL: https://github.com/apache/hadoop/pull/1540
There are cases where SCM can be stuck in safemode for ever if it considers
containers in CLOSING state for coming out of safemode
* If there are 5 containers in OPEN state inside SCM
* Out of 5, 3 containers are created in datanodes by the client.
* 2 containers are yet to be created in datanodes
* Due to some pipeline issue, pipeline close action is sent.
* All 5 container's state are changed from OPEN to CLOSING in SCM.
* Eventually , 3 container's state moves from CLOSING to CLOSED in SCM as
the datanodes closes those containers.
* 2 of the containers are still in CLOSING state.
* SCM is restarted.
* SCM will never gets container reports for the containers which were in
CLOSING state as those containers were never created in datanodes.
* SCM will remain in safemode.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 319744)
Remaining Estimate: 0h
Time Spent: 10m
> SCM should not consider containers in CLOSING state to come out of safemode
> ---------------------------------------------------------------------------
>
> Key: HDDS-2198
> URL: https://issues.apache.org/jira/browse/HDDS-2198
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Nilotpal Nandi
> Assignee: Nanda kumar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are cases where SCM can be stuck in safemode for ever if it considers
> containers in CLOSING state for coming out of safemode
> * If there are 5 containers in OPEN state inside SCM
> * Out of 5, 3 containers are created in datanodes by the client.
> * 2 containers are yet to be created in datanodes
> * Due to some pipeline issue, pipeline close action is sent.
> * All 5 container's state are changed from OPEN to CLOSING in SCM.
> * Eventually , 3 container's state moves from CLOSING to CLOSED in SCM as the
> datanodes closes those containers.
> * 2 of the containers are still in CLOSING state.
> * SCM is restarted.
> * SCM will never gets container reports for the containers which were in
> CLOSING state as those containers were never created in datanodes.
> * SCM will remain in safemode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
