[
https://issues.apache.org/jira/browse/HDFS-16513?focusedWorklogId=756503&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-756503
]
ASF GitHub Bot logged work on HDFS-16513:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Apr/22 16:16
Start Date: 13/Apr/22 16:16
Worklog Time Spent: 10m
Work Description: xkrogen commented on PR #4087:
URL: https://github.com/apache/hadoop/pull/4087#issuecomment-1098241563
> The pendingDatanodeMessage issue mentioned here strikes me as a bit risky.
...
I'm not following. The issue described from HDFS-2737 says that "if the
active NN is not rolling its logs periodically ... many datanode messages
\[will\] be queued up in the PendingDatanodeMessage structure". Certainly it is
bad if we don't have a way to ensure that the logs are rolled regularly. But
HDFS-14378 just proposes making the ANN roll its own edit logs, instead of
relying on the SbNN to roll them. I don't see the risk
Issue Time Tracking
-------------------
Worklog Id: (was: 756503)
Time Spent: 2h 40m (was: 2.5h)
> [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 40m
> 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]
