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 "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2019/10/01 20:27:00 UTC
[jira] [Commented] (HDFS-14284) RBF: Log Router identifier when
reporting exceptions
[ https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942294#comment-16942294 ]
Brahma Reddy Battula commented on HDFS-14284:
---------------------------------------------
Agree with [~crh]. May be we can handle seperate Jira and handle only "NoNamenodesAvailableException" here..?
I have one question here, what we are going to achieve by adding routerID to following..? will client retry to another router..? ( and wn't be incompatiable if there is some automation.)
Exception in thread "main" org.apache.hadoop.ipc.RemoteException(java.io.IOException): No namenode available under nameservice ns0
> RBF: Log Router identifier when reporting exceptions
> ----------------------------------------------------
>
> Key: HDFS-14284
> URL: https://issues.apache.org/jira/browse/HDFS-14284
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: hemanthboyina
> Priority: Major
> Attachments: HDFS-14284.001.patch, HDFS-14284.002.patch
>
>
> The typical setup is to use multiple Routers through ConfiguredFailoverProxyProvider.
> In a regular HA Namenode setup, it is easy to know which NN was used.
> However, in RBF, any Router can be the one reporting the exception and it is hard to know which was the one.
> We should have a way to identify which Router/Namenode was the one triggering the exception.
> This would also apply with Observer Namenodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org