hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7439) Add BlockOpResponseProto's message to DFSClient's exception message
Date Mon, 02 Mar 2015 07:09:05 GMT

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

Tsz Wo Nicholas Sze updated HDFS-7439:
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.0
           Status: Resolved  (was: Patch Available)

I have committed this.  Thanks, Takanobu!

> Add BlockOpResponseProto's message to DFSClient's exception message
> -------------------------------------------------------------------
>
>                 Key: HDFS-7439
>                 URL: https://issues.apache.org/jira/browse/HDFS-7439
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer & mover, datanode, hdfs-client
>            Reporter: Ming Ma
>            Assignee: Takanobu Asanuma
>            Priority: Minor
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7439.1.patch, HDFS-7439.2.patch, HDFS-7439.3.patch
>
>
> When (BlockOpResponseProto#getStatus() != SUCCESS), it helps with debugging if DFSClient
can add BlockOpResponseProto's message to the exception message applications will get. For
example, instead of
> {noformat}
>         throw new IOException("Got error for OP_READ_BLOCK, self="
>             + peer.getLocalAddressString() + ", remote="
>             + peer.getRemoteAddressString() + ", for file " + file
>             + ", for pool " + block.getBlockPoolId() + " block " 
>             + block.getBlockId() + "_" + block.getGenerationStamp());
> {noformat}
> It could be,
> {noformat}
>         throw new IOException("Got error for OP_READ_BLOCK, self="
>             + peer.getLocalAddressString() + ", remote="
>             + peer.getRemoteAddressString() + ", for file " + file
>             + ", for pool " + block.getBlockPoolId() + " block " 
>             + block.getBlockId() + "_" + block.getGenerationStamp()
>             + ", status message " + status.getMessage());
> {noformat}
> We might want to check out all the references to BlockOpResponseProto in DFSClient.



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

Mime
View raw message