[
https://issues.apache.org/jira/browse/HADOOP-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698274#action_12698274
]
Hadoop QA commented on HADOOP-5644:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12405204/5644.trunk.patch
against trunk revision 764287.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/185/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/185/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/185/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/185/console
This message is automatically generated.
> Namnode is stuck in safe mode
> -----------------------------
>
> Key: HADOOP-5644
> URL: https://issues.apache.org/jira/browse/HADOOP-5644
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.18.4, 0.19.2, 0.20.0, 0.21.0
>
> Attachments: 5644.branch-0.18.patch, 5644.branch-0.18.patch,
> 5644.branch-0.18.patch, 5644.branch-0.19.patch, 5644.branch-0.19.patch,
> 5644.branch-0.19.patch, 5644.trunk.patch, 5644.trunk.patch
>
>
> Restarting datanodes while a client is writing to it can cause namenode to
> get stuck in safe mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
