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

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

                Author: ASF GitHub Bot
            Created on: 19/Apr/22 11:27
            Start Date: 19/Apr/22 11:27
    Worklog Time Spent: 10m 
      Work Description: tomscut opened a new pull request, #4201:
URL: https://github.com/apache/hadoop/pull/4201

   JIRA: HDFS-16547.
   
   Currently, when a Namenode is in safemode(under starting or enter safemode 
manually), we can transfer this Namenode to Observer by command. This Observer 
node may receive many requests and then throw a SafemodeException, this causes 
unnecessary failover on the client.
   
   So Namenode in safe mode should not be transfer to observer state.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 758400)
    Remaining Estimate: 0h
            Time Spent: 10m

> [SBN read] Namenode in safe mode should not be transfer to observer state
> -------------------------------------------------------------------------
>
>                 Key: HDFS-16547
>                 URL: https://issues.apache.org/jira/browse/HDFS-16547
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: tomscut
>            Assignee: tomscut
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, when a Namenode is in safemode(under starting or enter safemode 
> manually), we can transfer this Namenode to Observer by command. This 
> Observer node may receive many requests and then throw a SafemodeException, 
> this causes unnecessary failover on the client.
> So Namenode in safe mode should not be transfer to observer state.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to