[
https://issues.apache.org/jira/browse/HADOOP-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576901#action_12576901
]
Hemanth Yamijala commented on HADOOP-2924:
------------------------------------------
Couple of comments:
- We should print the error message from socket.error. This will help us debug
problems better, given the very core nature of the change we are making to the
port detection method.
- We should also decrement the value of retries in case we get socket.error.
This is not being done even currently, but, I think, is clearly intended.
- Recommend removing the unused methods. I've checked they are indeed unused.
> HOD is trying to bring up task tracker on port which is already in
> close_wait state
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-2924
> URL: https://issues.apache.org/jira/browse/HADOOP-2924
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Aroop Maliakkal
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Fix For: 0.17.0
>
> Attachments: HADOOP-2924
>
>
> While bringing up task tracker using random ports, HOD is not checking
> whether the port is in CLOSE_WAIT state. So when it starts task tracker, we
> will be getting an address bind error on that port. We can avoid this error
> if we check for CLOSE_WAIT state on that port before starting the tasktracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
