[
https://issues.apache.org/jira/browse/HDFS-17444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832690#comment-17832690
]
ASF GitHub Bot commented on HDFS-17444:
---------------------------------------
xiaojunxiang2023 commented on PR #6694:
URL: https://github.com/apache/hadoop/pull/6694#issuecomment-2029037464
@hiwangzhihui, Hi~, please help me review it.
> Add getJournalSyncerStatus jmx metrics, to Indicates whether the
> JournalSyncer thread for the every namespace has enter working state.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17444
> URL: https://issues.apache.org/jira/browse/HDFS-17444
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.3.4, 3.3.6
> Reporter: xiaojunxiang
> Assignee: xiaojunxiang
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-03-31-09-31-18-056.png
>
>
> The JornalNode JVM process is not immediately in a normal state until the
> JournalSyncer thread is started.
> For some management platforms such as Ambari rolling restart JournalNode, we
> need a jmx metric to determine whether the JournalSyncer thread is started
> and enter working state for current namespace before restarting the next
> JournalNode. Otherwise, restart too quickly and more than half of
> JournalNodes will be out of order, causing the NameNode to die.
> When i add it , the effect is as follows:
> !image-2024-03-31-09-31-18-056.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
