Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAPcDmStQYsi+cz4dewncQHpxNLiPrNm0aWWUOv6vcuV+N6ozPQ@mail.gmail.com>
References: 
 <CAPQV63WypuPAXJAXaS=Ca-wNMMqxfbPXaGpdgjVYfiNT+UZT-Q@mail.gmail.com>
	<CAPcDmStQYsi+cz4dewncQHpxNLiPrNm0aWWUOv6vcuV+N6ozPQ@mail.gmail.com>
Date: Sun, 2 Dec 2012 21:53:20 -0500
Message-ID: 
 <CAPQV63XijwpeMGdTH77uRBwrH3FhUmp6ViSsdjaWVba16issZw@mail.gmail.com>
Subject: Re: Put while move or split
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=UTF-8

Ok. so if on the client side I'm "simply" using Puts, scans and gets
fron the HTableInterface, I don't have to worry about that since it
will retry.

But I still should consider catching exceptions when regions are not
available because the region server is down for less than 3 minutes,
right?

Thanks,

JM

2012/12/2, Nicolas Liochon <nkeywal@gmail.com>:
> It's not accessible, but it's more or less transparent (latency impact
> aside) for the end user: the hbase client will retry the operation.
>
> On Sun, Dec 2, 2012 at 11:10 PM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org> wrote:
>
>> ?
>