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 "Chris Nauroth (Jira)" <ji...@apache.org> on 2022/10/25 17:07:00 UTC

[jira] [Resolved] (HDFS-8510) Provide different timeout settings for hdfs dfsadmin -getDatanodeInfo.

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

Chris Nauroth resolved HDFS-8510.
---------------------------------
    Resolution: Won't Fix

This is an old improvement proposal that I'm no longer planning on implementing. I'm going to close the issue. If anyone else would find it useful, please feel free to reopen and reassign. I'd be happy to help with code review.

> Provide different timeout settings for hdfs dfsadmin -getDatanodeInfo.
> ----------------------------------------------------------------------
>
>                 Key: HDFS-8510
>                 URL: https://issues.apache.org/jira/browse/HDFS-8510
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Major
>
> During a rolling upgrade, an administrator runs {{hdfs dfsadmin -getDatanodeInfo}} to check if a DataNode has stopped.  Currently, this operation is subject to the RPC connection retries defined in {{ipc.client.connect.max.retries}} and {{ipc.client.connect.retry.interval}}.  This issue proposes adding separate configuration properties to control the retries for this operation.



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