[
https://issues.apache.org/jira/browse/HDFS-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Íñigo Goiri updated HDFS-16705:
-------------------------------
Summary: RBF: Support healthMonitor timeout configurable and cache NN and
client proxy in NamenodeHeartbeatService (was: RBF supports healthMonitor
timeout configurable and cache NN and client proxy in NamenodeHeartbeatService)
> RBF: Support healthMonitor timeout configurable and cache NN and client proxy
> in NamenodeHeartbeatService
> ---------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16705
> URL: https://issues.apache.org/jira/browse/HDFS-16705
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: ZanderXu
> Assignee: ZanderXu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> When I read NamenodeHeartbeatService.class of RBF, I feel that there are
> somethings we can do for NamenodeHeartbeatService.class.
> * Cache NameNode Protocol and Client Protocol to avoid creating a new proxy
> every time
> * Supports healthMonitorTimeout configuration
> * Format code of getNamenodeStatusReport to make it clearer
--
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
