[
https://issues.apache.org/jira/browse/HDFS-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370517#comment-16370517
]
Chris Douglas commented on HDFS-13119:
--------------------------------------
bq. As this is technically a bug, I'd like to push it for 2.9.1 and 3.0.1 (or
3.0.2).
There's a vote for 3.0.1 in progress, but you can contact the release manager
([~eddyxu]) in case he rolls another RC.
bq. Any idea what's the current state with the branches? My guess is branch-2.9
and branch-3.0.
AFAIK:
trunk -> 3.2
3.1.0 -> branch-3.1
3.0.2 -> branch-3.0
3.0.1 -> branch-3.0.1
2.10 -> branch-2
2.9.1 -> branch-2.9
> RBF: Manage unavailable clusters
> --------------------------------
>
> Key: HDFS-13119
> URL: https://issues.apache.org/jira/browse/HDFS-13119
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: 3.0.0
> Reporter: Íñigo Goiri
> Assignee: Yiqun Lin
> Priority: Major
> Labels: RBF
> Fix For: 3.1.0, 2.10.0, 3.2.0
>
> Attachments: HDFS-13119.001.patch, HDFS-13119.002.patch,
> HDFS-13119.003.patch, HDFS-13119.004.patch, HDFS-13119.005.patch,
> HDFS-13119.006.patch
>
>
> When a federated cluster has one of the subcluster down, operations that run
> in every subcluster ({{RouterRpcClient#invokeAll()}}) may take all the RPC
> connections.
--
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
