hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2924) HOD is trying to bring up task tracker on port which is already in close_wait state
Date Wed, 12 Mar 2008 09:08:46 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated HADOOP-2924:
--------------------------------------------

    Attachment: HADOOP-2924.1

Included the above changes. Also, increased the default retries to 900(which takes around
6.2 secs in the worst case of no single available port out of 900 ports). The default retries
used to be 30.

> 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, HADOOP-2924.1
>
>
> 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.


Mime
View raw message