[
https://issues.apache.org/jira/browse/HDFS-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513450#comment-14513450
]
Hadoop QA commented on HDFS-8226:
---------------------------------
\\
\\
| (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/12728225/HDFS-8226.1.patch |
| Optional Tests | site |
| git revision | trunk / 1a2459b |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/10402/console |
This message was automatically generated.
> Non-HA rollback compatibility broken
> ------------------------------------
>
> Key: HDFS-8226
> URL: https://issues.apache.org/jira/browse/HDFS-8226
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: J.Andreina
> Assignee: J.Andreina
> Priority: Blocker
> Attachments: HDFS-8226.1.patch
>
>
> In HA while performing rollback , we use “hdfs namenode –rollback” which
> would prompt user for confirmation. ( Implemented as part of HDFS-5138)
> For Non-HA , as per doc if we perform rollback using “start-dfs.sh –rollback”
> , then namenode startup hangs ( As it tries to start namenode in daemon mode
> , hence will not be able to prompt user for confirmation )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
