hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@apache.org>
Subject Re: Large startup time in remote MapReduce job
Date Wed, 22 Jun 2011 17:08:32 GMT

On Jun 21, 2011, at 2:02 PM, Harsh J wrote:
>>> 
>>> If your jar does not contain code changes that need to get transmitted
>>> every time, you can consider placing them on the JT/TT classpaths
>> 
>>        ... which means you get to bounce your system every time you change code.
> 
> Its ugly, but if the jar filename remains the same there shouldn't
> need to be any bouncing. Doable if there's no activity at replacement
> point of time?

	I have yet to find a jar file that never ever changes.

	It may take a year+, but it will change.  The corollary is that you'll need to change it
at the worst possible time and in an incompatible way such that older code will break and
need to be upgraded.  So don't do it. :)


Mime
View raw message