[
https://issues.apache.org/jira/browse/HADOOP-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605691#action_12605691
]
Hadoop QA commented on HADOOP-3564:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12384118/HADOOP-3564.1
against trunk revision 668612.
+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 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2673/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2673/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2673/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2673/console
This message is automatically generated.
> Sometime after successful hod allocation datanode fails to come up with
> java.net.BindException for dfs.datanode.ipc.address
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3564
> URL: https://issues.apache.org/jira/browse/HADOOP-3564
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.18.0
> Reporter: Karam Singh
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3564.1
>
>
> From Jira: HADOOP-3283 which introduced new conf parameter
> dfs.datanode.ipc.address which defaults to 50020.
> When static dfs of hadoop version 0.18.0 running and its conf is not having
> dfs.datanode.ipc.address specified, then datanode start with 50020 port for
> ipc, w
> When we use hod allocate without using static dfs.datanode on some machine
> fails to come. On further investigation it has been found sometimes when
> torque provides list nodes, that list also contain some static dfs node.
> When hodring tries to start datanode on a machine where a static dfs datanode
> of hadoop 0.18.0 is running, hod's dynamic dfs datanode fails to come with
> exception -: java.net.BindException: Problem binding to /0.0.0.0:50020 :
> Address already in use
> beacuse hod provides ports for dfs.datanode.address and
> dfs.datanode.http.address.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
