[
https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938979#comment-16938979
]
CR Hota commented on HDFS-14284:
--------------------------------
[~hemanthboyina] [~inigoiri] [~ayushtkn] Thanks for the discussion so far.
Overall approach looks fine.
Can we separate out RIOEx from hadoop-common and StandByExe not extend from
RIOEx? Its best not to change hadoop-common directly for this feature.
RIOEx can be added in hdfs-rbf project and standby can be used directly to
construct the error msg containing the router id before creating standby
exception. Anyways standby already has logic in client side to failover, log of
standby will automatically output the router id used when exception was created
in server.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
