[
https://issues.apache.org/jira/browse/HADOOP-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605840#action_12605840
]
Hemanth Yamijala commented on HADOOP-3564:
------------------------------------------
Writing test cases will require some refactoring of HOD code, which is not
currently in the scope. Relied on cross testing to make sure things are
working. The fix can be committed.
> 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.
