Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAMWNowHvwRY7g0smtw6qHC3ieR7DzQJ4FWPCZk9kAFVFbfs_mw@mail.gmail.com>
References: 
 <CAMWNowHvwRY7g0smtw6qHC3ieR7DzQJ4FWPCZk9kAFVFbfs_mw@mail.gmail.com>
From: Ted Dunning <tdunning@maprtech.com>
Date: Wed, 26 Sep 2012 15:07:28 -0700
Message-ID: 
 <CAND0qzuY5T9Z8tU9jDpuwVRJBas=1u+9YAtTFaCWUOmoekdpXQ@mail.gmail.com>
Subject: Re: splitting jobtracker and namenode
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3b9d2f95f0bd04caa20d0d

--e89a8f3b9d2f95f0bd04caa20d0d
Content-Type: text/plain; charset=ISO-8859-1

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
>

--e89a8f3b9d2f95f0bd04caa20d0d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Why are you changing the TTL on DNS if you aren&#39;t moving the name? =A0I=
f you are just changing the config to a new name, then caching won&#39;t ma=
tter.<br><br><div class=3D"gmail_quote">On Wed, Sep 26, 2012 at 1:46 PM, Pa=
tai Sangbutsarakum <span dir=3D"ltr">&lt;<a href=3D"mailto:silvianhadoop@gm=
ail.com" target=3D"_blank">silvianhadoop@gmail.com</a>&gt;</span> wrote:<br=
>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Hadoopers,<br>
<br>
My production Hadoop 0.20.2 cluster has been running Pri. namenode and<br>
Jobtracker together in the same box for long time. it&#39;s time to<br>
separate them. I am trying to write up a procedure on this to make<br>
sure that it won&#39;t cause any issues.<br>
<br>
- Decrease TTL of DNS entry for value of mapred.job.tracker<br>
- Prepare new name in DNS entry for value of mapred.job.tracker<br>
- Change value of mapred.job.tracker (in mapred-site.xml) to new<br>
server and propagate the new config to whole cluster and clients (<br>
where Hadoop jobs are submitted from )<br>
- Create directory defined in mapred.local.dir on new server.<br>
- Make sure that new jobtracker server is not in slave or master file.<br>
- run stop-mapred.sh on current jobtracker server<br>
- run start-mapred.sh on new jobtracker server<br>
<br>
Do I miss anything ?<br>
<br>
Please suggest.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Patai<br>
</font></span></blockquote></div><br>

--e89a8f3b9d2f95f0bd04caa20d0d--