Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of silvianhadoop@gmail.com
 designates 209.85.215.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAND0qzuY5T9Z8tU9jDpuwVRJBas=1u+9YAtTFaCWUOmoekdpXQ@mail.gmail.com>
References: 
 <CAMWNowHvwRY7g0smtw6qHC3ieR7DzQJ4FWPCZk9kAFVFbfs_mw@mail.gmail.com>
	<CAND0qzuY5T9Z8tU9jDpuwVRJBas=1u+9YAtTFaCWUOmoekdpXQ@mail.gmail.com>
Date: Wed, 26 Sep 2012 15:28:26 -0700
Message-ID: 
 <CAMWNowE7Jc0LWdT4FHqyC-d=4PmuRBOGLqmCfaHibUER-VeV=w@mail.gmail.com>
Subject: Re: splitting jobtracker and namenode
From: Patai Sangbutsarakum <silvianhadoop@gmail.com>
To: user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Thanks Ted, that's true.


On Wed, Sep 26, 2012 at 3:07 PM, Ted Dunning <tdunning@maprtech.com> wrote:
> Why are you changing the TTL on DNS if you aren't moving the name?  If you
> are just changing the config to a new name, then caching won't matter.
>
>
> On Wed, Sep 26, 2012 at 1:46 PM, Patai Sangbutsarakum
> <silvianhadoop@gmail.com> wrote:
>>
>> Hi Hadoopers,
>>
>> My production Hadoop 0.20.2 cluster has been running Pri. namenode and
>> Jobtracker together in the same box for long time. it's time to
>> separate them. I am trying to write up a procedure on this to make
>> sure that it won't cause any issues.
>>
>> - Decrease TTL of DNS entry for value of mapred.job.tracker
>> - Prepare new name in DNS entry for value of mapred.job.tracker
>> - Change value of mapred.job.tracker (in mapred-site.xml) to new
>> server and propagate the new config to whole cluster and clients (
>> where Hadoop jobs are submitted from )
>> - Create directory defined in mapred.local.dir on new server.
>> - Make sure that new jobtracker server is not in slave or master file.
>> - run stop-mapred.sh on current jobtracker server
>> - run start-mapred.sh on new jobtracker server
>>
>> Do I miss anything ?
>>
>> Please suggest.
>>
>> Patai
>
>