Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <258885537.1205425944387.JavaMail.jira@brutus>
Date: Thu, 13 Mar 2008 09:32:24 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-2924) HOD is trying to bring up task
 tracker on  port which is already in close_wait state
In-Reply-To: <1353379691.1204543491125.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578374#action_12578374 ] 

Hemanth Yamijala commented on HADOOP-2924:
------------------------------------------

+1 for the changes.

Going to do patch available to run through Hudson.

> 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.