Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of phobos182@gmail.com
 designates 209.85.160.43 as permitted sender)
Subject: Re: Full stack rolling restart
References: <1401345461865-4059877.post@n3.nabble.com>
From: Jeremy Carroll <phobos182@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <1401345461865-4059877.post@n3.nabble.com>
Message-Id: <B96939CF-6228-41A0-81FF-0DB127E324A7@gmail.com>
Date: Thu, 29 May 2014 09:11:21 -0700
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

We have taken the approach of graceful stop of the RegionServer in maintenan=
ce. Then restarting the DataNode. Once it has registered and back online we s=
tart the RegionServer and move it's regions back. We do not compact before o=
r after the operation since it takes a short period of time, and minor compa=
ctions will regain the small amount of locality lost during the maintenance o=
peration.=20

I believe it's doubtful that he Hadoop project itself will release an offici=
al cluster management / operations framework. So we built a lot of this ours=
elves.=20

Sent from my iPhone

> On May 28, 2014, at 11:37 PM, sameerv <smv1@hotmail.com> wrote:
>=20
> I am curious to know what the industry folks think of rolling restart on t=
he
> full stack. Envisioning something like each node which services it runs,
> stop all services, use new configs and start all services. Is it feasible t=
o
> do this ? Can folks who have tried, share their experiences please?
>=20
> Thanks,
> Sameer
>=20
>=20
>=20
>=20
> --
> View this message in context: http://apache-hbase.679495.n3.nabble.com/Ful=
l-stack-rolling-restart-tp4059877.html
> Sent from the HBase User mailing list archive at Nabble.com.