Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <9840370.1174639952536.JavaMail.jira@brutus>
Date: Fri, 23 Mar 2007 01:52:32 -0700 (PDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1085) Remove 'port rolling' from
 Mini{DFS|MR}Cluster
In-Reply-To: <25360615.1173308124463.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy updated HADOOP-1085:
----------------------------------

    Status: Patch Available  (was: Open)

Nigel, can you try anc check if this works better for the patch process? Thanks!

> Remove 'port rolling' from Mini{DFS|MR}Cluster
> ----------------------------------------------
>
>                 Key: HADOOP-1085
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1085
>             Project: Hadoop
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.12.0
>            Reporter: Arun C Murthy
>         Assigned To: Arun C Murthy
>             Fix For: 0.13.0
>
>         Attachments: HADOOP-1085_20070311_1.patch
>
>
> The rolling of ports in these 2 clusters lead to a lot of timing issues and failed test cases; as witnessed in our patch process.
> The way around is to let the OS pick the port for the NameNode/JobTracker and let the the DataNode/TaskTracker query them for the port to connect to and then use that port.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.