[
https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943111#comment-16943111
]
Brahma Reddy Battula commented on HDFS-14284:
---------------------------------------------
Ok.Just I want to confirm when router is can't access state store we can
shutdown the router.
{quote}This shouldn't break compatibility as it would be a new field in the new
remote exception.
{quote}
I was talking about "new NoNamenodesAvailableException" where we are going to
add one more field( and this exception was introduced b. I was concerned about
this.
[~ayushtkn] and [~inigoiri], if you both are ok. Then I am ok.
[~hemanthboyina] you can update the patch,as [~crh] suggested.
> 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: [email protected]
For additional commands, e-mail: [email protected]
