hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harsh J <ha...@cloudera.com>
Subject Re: Large startup time in remote MapReduce job
Date Tue, 21 Jun 2011 21:02:53 GMT

On Wed, Jun 22, 2011 at 2:28 AM, Allen Wittenauer <aw@apache.org> wrote:
> On Jun 21, 2011, at 1:31 PM, Harsh J wrote:
>> Gabor,
>> 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?

P.s. Gabor: Moving the discussion to mapreduce-user@hadoop.apache.org
Please use the general@ list only for general project-wide discussions
on Hadoop.

Harsh J

View raw message