hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-237) Better handling of dfsadmin command when namenode is slow
Date Mon, 07 Sep 2015 02:30:46 GMT

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

Harsh J resolved HDFS-237.
--------------------------
    Resolution: Later

This older JIRA is a bit stale given the multiple changes that went into the RPC side. Follow
HADOOP-9640 and related JIRAs instead for more recent work.

bq. a separate rpc queue

This is supported today via the servicerpc-address configs (typically set to 8022, and strongly
recommended for HA modes).

> Better handling of dfsadmin command when namenode is slow
> ---------------------------------------------------------
>
>                 Key: HDFS-237
>                 URL: https://issues.apache.org/jira/browse/HDFS-237
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Koji Noguchi
>
> Probably when hitting HADOOP-3810, Namenode became unresponsive.  Large time spent in
GC.
> All dfs/dfsadmin command were timing out.
> WebUI was coming up after waiting for a long time.
> Maybe setting a long timeout would have made the dfsadmin command go through.
> But it would be nice to have a separate queue/handler which doesn't compete with regular
rpc calls.
> All I wanted to do was dfsadmin -safemode enter, dfsadmin -finalizeUpgrade ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message