[ https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936081#comment-16936081 ]
Íñigo Goiri commented on HDFS-14284: ------------------------------------ [~hemanthboyina], it would be something like that but that one is too specific. I would like to have RouterIOException or something like that that would take the routerId as a parameter (or even get it automatically). So ConnectionNullException would be a subclass of this and do: {code} throw new ConnectionNullException("Cannot get a connection to " + rpcAddress, router.getRouterId()); {code} (Or just the new and infer the router Id by itself using a static or similar.) > 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 > > 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