Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPcDmSsnj1Fv=QCqu7GyCB__+DLEn1j-tr1ZbP2182zAj-CjVw@mail.gmail.com>
References: 
 <CAPcDmSsnj1Fv=QCqu7GyCB__+DLEn1j-tr1ZbP2182zAj-CjVw@mail.gmail.com>
Date: Thu, 6 Dec 2012 09:20:29 +0800
Message-ID: 
 <CA+RK=_D6F4PX-B+bMggCivc0A3718K-vOyLoOc03sVmx54RUzA@mail.gmail.com>
Subject: assignment - is master beeing a watchdog useful?
From: Andrew Purtell <apurtell@apache.org>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f6435569b4e3f04d024e759

--e89a8f6435569b4e3f04d024e759
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

My information here may be stale.

I remember we increased the timeout interval from 3 to 30 minutes, because
the master injecting itself into mid-assignment often triggered races and
led to double assignments and other bad stuff. At 30 minutes, this is not
useful IMO. As an operator I'd run hbck to sort it out long before then.


On Thursday, December 6, 2012, Nicolas Liochon wrote:

> See comments in HBASE-7247: the master checks the time spent by the
> regionserver, and assign it to another if it takes too long. It adds
> complexity.
>
> from Stack: "I'm currently of the opinion that this expensive facility of
> master failing an open because it has been taking too long on a particula=
r
> regionserver has been of no use =96 worse, it has only caused headache =
=96 but
> I may be just not remembering and others out on dev list will have better
> recall than I."
>
> So, opinions & memories are more than welcome.
> Removing this feature would be a huge simplification!
>
> Cheers,
>
> Nicolas
>


--=20
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--e89a8f6435569b4e3f04d024e759--