You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hector Sandoval Chaverri (Jira)" <ji...@apache.org> on 2023/05/25 20:21:00 UTC

[jira] [Created] (HDFS-17026) NamenodeHeartbeatService should update JMX report with configurable frequency

Hector Sandoval Chaverri created HDFS-17026:
-----------------------------------------------

             Summary: NamenodeHeartbeatService should update JMX report with configurable frequency
                 Key: HDFS-17026
                 URL: https://issues.apache.org/jira/browse/HDFS-17026
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: rbf
            Reporter: Hector Sandoval Chaverri


TheĀ NamenodeHeartbeatService currently calls each of the Namenode's JMX endpoint every time it wakes up (default value is every 5 seconds).

In a cluster with 40 routers, we have observed service degradation on some of theĀ  Namenodes, since the JMX request obtains Datanode status and blocks other RPC requests. However, JMX report data doesn't seem to be used for critical paths on the routers.

We should configure the NamenodeHeartbeatService so it updates the JMX reports on a slower frequency than the Namenode states or to disable the reports completely.

The class calls out the JMX request being optional even though there is no implementation to turn it off:
{noformat}
// Read the stats from JMX (optional)
updateJMXParameters(webAddress, report);{noformat}



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

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