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

ASF GitHub Bot logged work on HDFS-15820:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Feb/21 15:24
            Start Date: 04/Feb/21 15:24
    Worklog Time Spent: 10m 
      Work Description: bshashikant opened a new pull request #2682:
URL: https://github.com/apache/hadoop/pull/2682


   Please see https://issues.apache.org/jira/browse/HDFS-15820.
   


----------------------------------------------------------------
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: 547686)
    Remaining Estimate: 0h
            Time Spent: 10m

> Ensure snapshot root trash provisioning happens only post safe mode exit
> ------------------------------------------------------------------------
>
>                 Key: HDFS-15820
>                 URL: https://issues.apache.org/jira/browse/HDFS-15820
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, on namenode startup, snapshot trash root provisioning starts as 
> along with trash emptier service but namenode might not be out of safe mode 
> by then. This can fail the snapshot trash dir creation thereby crashing the 
> namenode. The idea here is to trigger snapshot trash provisioning only post 
> safe mode exit.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to