hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Íñigo Goiri (JIRA) <j...@apache.org>
Subject [jira] [Updated] (HDFS-13852) RBF: The DN_REPORT_TIME_OUT and DN_REPORT_CACHE_EXPIRE should be configured in RBFConfigKeys.
Date Mon, 17 Sep 2018 16:58:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Íñigo Goiri updated HDFS-13852:
-------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: HDFS-13891

> RBF: The DN_REPORT_TIME_OUT and DN_REPORT_CACHE_EXPIRE should be configured in RBFConfigKeys.
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-13852
>                 URL: https://issues.apache.org/jira/browse/HDFS-13852
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: federation, hdfs
>    Affects Versions: 3.1.0, 2.9.1, 3.0.1
>            Reporter: yanghuafeng
>            Assignee: yanghuafeng
>            Priority: Major
>         Attachments: HDFS-13852.001.patch, HDFS-13852.002.patch, HDFS-13852.003.patch,
HDFS-13852.004.patch
>
>
> In the NamenodeBeanMetrics the router will invokes 'getDataNodeReport' periodically.
And we can set the dfs.federation.router.dn-report.time-out and dfs.federation.router.dn-report.cache-expire
to avoid time out. But when we start the router, the FederationMetrics will also invoke the
method to get node usage. If time out error happened, we cannot adjust the parameter time_out.
And the time_out in the FederationMetrics and NamenodeBeanMetrics should be the same.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message