[
https://issues.apache.org/jira/browse/HADOOP-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602555#action_12602555
]
Hadoop QA commented on HADOOP-3483:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383434/3483.2.patch
against trunk revision 663447.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+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 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/2583/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2583/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2583/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2583/console
This message is automatically generated.
> [HOD] Improvements with cluster directory handling
> --------------------------------------------------
>
> Key: HADOOP-3483
> URL: https://issues.apache.org/jira/browse/HADOOP-3483
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Fix For: 0.18.0
>
> Attachments: 3483.1.patch, 3483.2.patch, 3483.patch
>
>
> The following improvements are asked for from users related to cluster
> directory handling:
> - Create a new cluster directory if one does not exist.
> - If a cluster directory points to a dead cluster, currently allocate fails
> with a message asking user to deallocate it first. Instead, it should issue a
> warning, deallocate the cluster and automatically allocate a fresh one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.