Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <29301589.1148070451017.JavaMail.jira@brutus>
Date: Fri, 19 May 2006 20:27:31 +0000 (GMT+00:00)
From: "Yoram Arnon (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-232) jar files sent to task tracker
 should override existing jar
In-Reply-To: <25736722.1147990685938.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-232?page=comments#action_12412585 ] 

Yoram Arnon commented on HADOOP-232:
------------------------------------

debugging the hadoop distcp command required it.
the command is executed by the dfs client, which is in this case a map task.
the class is part of the hadoop release however, so it already resided on the tasktracker's nodes. We wanted to actually override it using a newly sent jar, without upgrading and restarting the map-reduce cluster.
we saw that as a general enough case to warrant a change to the task tracker.

I guess that an alternate solution would be to unbundle the 'external' programs from the main jar file.


> jar files sent to task tracker should override existing jar
> -----------------------------------------------------------
>
>          Key: HADOOP-232
>          URL: http://issues.apache.org/jira/browse/HADOOP-232
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Reporter: Yoram Arnon
>     Assignee: Milind Bhandarkar
>     Priority: Minor
>  Attachments: hadoop-232.patch
>
> jar files sent to task tracker are appended to list, rather than prepended to it.
> this results in the original jar getting executed, although a new one was sent  - not the intent.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira