[
https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769697#comment-16769697
]
Íñigo Goiri commented on HDFS-14284:
------------------------------------
One of the Routers is triggering some exceptions and it is very hard to know
which of the Routers (currently 16) to check for more detailed logs.
The easy solution is to add the Router identifier to the exception that we
throw from the Router.
However, this might be a common scenario in general and we may want to also
change the ConfiguredFailoverProxyProvider to identify the source of the
exception.
I think this might be similar for the Observer Namenodes if we have multiple of
them.
[~xkrogen], [~csun], any thoughts on doing this generic?
In any case, I think we should add this to the Router side too.
> 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
> Priority: Major
>
> 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
(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
