You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Nandakumar (JIRA)" <ji...@apache.org> on 2017/02/08 09:01:41 UTC
[jira] [Commented] (HDFS-11395)
RequestHedgingProxyProvider#RequestHedgingInvocationHandler hides the
Exception thrown from NameNode
[ https://issues.apache.org/jira/browse/HDFS-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857689#comment-15857689 ]
Nandakumar commented on HDFS-11395:
-----------------------------------
If we get RemoteException other than {{StandbyException}}, it is safe to throw it rather than wrapping it into {{MultiException}}.
[~arpitagarwal] any comment or suggestion on this?
> RequestHedgingProxyProvider#RequestHedgingInvocationHandler hides the Exception thrown from NameNode
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-11395
> URL: https://issues.apache.org/jira/browse/HDFS-11395
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Reporter: Nandakumar
> Assignee: Nandakumar
>
> When using RequestHedgingProxyProvider, in case of Exception (like FileNotFoundException) from ActiveNameNode, {{RequestHedgingProxyProvider#RequestHedgingInvocationHandler.invoke}} receives {{ExecutionException}} since we use {{CompletionService}} for the call. The ExecutionException is put into a map and wrapped with {{MultiException}}.
> So for a FileNotFoundException the client receives {{MultiException(Map(ExecutionException(InvocationTargetException(RemoteException(FileNotFoundException)))))}}
> It will cause problem in clients which are handling RemoteExceptions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org