[
https://issues.apache.org/jira/browse/HDFS-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948739#comment-14948739
]
Hadoop QA commented on HDFS-9181:
---------------------------------
\\
\\
| (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/12765601/HDFS-9123.004.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 1107bd3 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/12864/console |
This message was automatically generated.
> Better handling of exceptions thrown during upgrade shutdown
> ------------------------------------------------------------
>
> Key: HDFS-9181
> URL: https://issues.apache.org/jira/browse/HDFS-9181
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Minor
> Attachments: HDFS-9123.004.patch, HDFS-9181.002.patch,
> HDFS-9181.003.patch
>
>
> Previously in HDFS-7533, a bug was fixed by suppressing exceptions during
> upgrade shutdown. It may be appropriate as a temporary fix, but it would be
> better if the exception is handled in some other ways.
> One way to handle it is by emitting a warning message. There could exist
> other ways to handle it. This jira is created to discuss how to handle this
> case better.
> Thanks to [~templedf] for bringing this up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
