[
https://issues.apache.org/jira/browse/HDFS-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428907#comment-16428907
]
Ajay Kumar commented on HDFS-13384:
-----------------------------------
[~elgoiri] thanks for updating the patch. Ya, you are right, seems datanodes
are registering for all nameservices.
MiniRouterDFSCluster#generateNamenodeConfiguration L419 add all nameservices to
datanode config. I think its ok if we don't separate DataNodes for nameservices
but then we can skip (L217-233) assertion after slowdown of only subcluster0 as
we know we will get 4 live datanodes under current settings. For timeout shall
we create a junit rule as that will bind other testcases in timeout as well?
> RBF: Improve timeout RPC call mechanism
> ---------------------------------------
>
> Key: HDFS-13384
> URL: https://issues.apache.org/jira/browse/HDFS-13384
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Minor
> Attachments: HDFS-13384.000.patch, HDFS-13384.001.patch
>
>
> When issuing RPC requests to subclusters, we have a time out mechanism
> introduced in HDFS-12273. We need to improve this is handled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
