[ https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937848#comment-16937848 ]
Ayush Saxena commented on HDFS-14284: ------------------------------------- IMO changing to RIOE from IOE won’t be a problem. Anyone catching IOE would still be able to catch it since RIOE extends IOE and as said RIOE will be a better also since the client can easily do getRouterId and stuff, it will also differentiate the general IOE from the ones coming from router > 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 > > > 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