[
https://issues.apache.org/jira/browse/HDFS-16513?focusedWorklogId=756801&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-756801
]
ASF GitHub Bot logged work on HDFS-16513:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/22 01:48
Start Date: 14/Apr/22 01:48
Worklog Time Spent: 10m
Work Description: tomscut commented on PR #4087:
URL: https://github.com/apache/hadoop/pull/4087#issuecomment-1098630345
Thank you @xkrogen for your detailed explanation. I left out some
information. You are right.
I thought it was ANN automatic rolledits feature first, then discuss whether
to let SNN trigger ANN to rolledits. I got the order of the two wrong.
And I thought that "if the active NN is not rolling its logs periodically"
meant that the configuration cycle is very large, or that EditLogTailerThread
exits because of some UnknowException. As a result, ANN cannot normally roll
its logs. Let SNN trigger ANN to roll edits, just to add another layer of
assurance. I made a mistake here.
Issue Time Tracking
-------------------
Worklog Id: (was: 756801)
Time Spent: 2h 50m (was: 2h 40m)
> [SBN read] Observer Namenode should not trigger the edits rolling of active
> Namenode
> ------------------------------------------------------------------------------------
>
> Key: HDFS-16513
> URL: https://issues.apache.org/jira/browse/HDFS-16513
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: tomscut
> Assignee: tomscut
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> To avoid frequent edtis rolling, we should disable OBN from triggering the
> edits rolling of active Namenode.
> It is sufficient to retain only the triggering of SNN and the auto rolling of
> ANN.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
