You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "xiaojunxiang (Jira)" <ji...@apache.org> on 2024/03/28 04:15:00 UTC

[jira] [Created] (HDFS-17444) Add JournalSyncerStarted jmx metrics, to Indicates whether the JournalSyncer thread has been started.

xiaojunxiang created HDFS-17444:
-----------------------------------

             Summary: Add JournalSyncerStarted jmx metrics, to Indicates whether the JournalSyncer thread has been started.
                 Key: HDFS-17444
                 URL: https://issues.apache.org/jira/browse/HDFS-17444
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: hdfs
    Affects Versions: 3.3.6, 3.3.4
            Reporter: xiaojunxiang
            Assignee: xiaojunxiang


  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 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. 

  Extra info: The JournalSyncer thread is started when a NameNode requests EditLog information.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org