hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hemanthboyina (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14284) RBF: Log Router identifier when reporting exceptions
Date Tue, 24 Sep 2019 17:34:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937025#comment-16937025

hemanthboyina commented on HDFS-14284:

attached patch , please review [~elgoiri]

> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message