[ 
https://issues.apache.org/jira/browse/HDFS-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043716#comment-18043716
 ] 

ASF GitHub Bot commented on HDFS-15616:
---------------------------------------

github-actions[bot] commented on PR #2373:
URL: https://github.com/apache/hadoop/pull/2373#issuecomment-3629625309

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Disable Observer NameNode to trigger edit log roll
> --------------------------------------------------
>
>                 Key: HDFS-15616
>                 URL: https://issues.apache.org/jira/browse/HDFS-15616
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HDFS-15616.001.patch, HDFS-15616.002.patch, 
> HDFS-15616.003.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently when Observer is transitioned from StandbyState, the editLogTailer 
> will still send the request to roll editLog to ActiveNN, which should be 
> disabled to keep the definition of "logRollPeriodMs" clear.
> One thing I'm not sure is for a cluster with multi standby Namenode, all the 
> standby NN will trigger the roll. Should this feature be extended to all 
> standby NNs or implementing on observers first?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to