[
https://issues.apache.org/jira/browse/HDFS-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524569#comment-14524569
]
Hadoop QA commented on HDFS-3927:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12544787/HDFS-3927.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/10523/console |
This message was automatically generated.
> DFSInputStream#blockSeekTo may print incorrect warn msg for IOException
> -----------------------------------------------------------------------
>
> Key: HDFS-3927
> URL: https://issues.apache.org/jira/browse/HDFS-3927
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Minor
> Attachments: HDFS-3927.patch
>
>
> In DFSInputStream#blockSeekTo, for most IOExceptions (except
> InvalidEncryptionKeyException and InvalidBlockTokenException), the current
> code only prints "Failed to connect to targetAddr", which can be incorrect
> since there are other possible cases, e.g., the chosen node (remote/local)
> can be connected but the block/replica cannot be found. The correct error msg
> (including the error msg from remote node) should be printed to log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
