hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9532) Detailed exception info is lost in reportTo method of ErrorReportAction and ReportBadBlockAction
Date Wed, 09 Dec 2015 19:14:10 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yongjun Zhang updated HDFS-9532:
--------------------------------
    Priority: Trivial  (was: Major)

> Detailed exception info is lost in reportTo method of ErrorReportAction and ReportBadBlockAction
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9532
>                 URL: https://issues.apache.org/jira/browse/HDFS-9532
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>            Priority: Trivial
>              Labels: supportability
>
> See code below
> {code}
>     try {
>       bpNamenode.reportBadBlocks(locatedBlock);
>     } catch (RemoteException re) {
>       DataNode.LOG.info("reportBadBlock encountered RemoteException for "
>           + "block:  " + block , re);
>     } catch (IOException e) {
>       throw new BPServiceActorActionException("Failed to report bad block "
>           + block + " to namenode: ");
>     }
>   }
> {code}
> When IOException e is thrown, the information of e is not reported back to caller. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message