Use http://search-hadoop.com .

We index all HBase and other Hadoop content - mailing lists, JIRA, Wiki, Web 
site, source code. 


Otis
----
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch




----- Original Message ----
> From: Jean-Daniel Cryans <[email protected]>
> To: [email protected]
> Sent: Tue, July 13, 2010 2:02:47 PM
> Subject: Re: Handling downtime from hbase.client
> 
> That's probably temporary, else there's always google ;)
> 
> J-D
> 
> On  Tue, Jul 13, 2010 at 10:58 AM, Justin Cohen <[email protected]>  
>wrote:
> > Where's the best place to search the mailing list?  The archives  here don't
> > seem to work: http://mail-archives.apache.org/mod_mbox/hbase-user/
> >
> >  Thanks!
> >
> > -justin
> >
> > On 7/13/10 10:47 AM, Jean-Daniel  Cryans wrote:
> >>
> >> This kind of issue was discussed a couple  of times on this mailing
> >> list. Basically, you can play with  hbase.client.pause and
> >> hbase.client.retries.number but you won't  find this satisfactory,
> >> which is why we opened
> >> https://issues.apache.org/jira/browse/HBASE-2445
> >>
> >>  J-D
> >>
> >> On Tue, Jul 13, 2010 at 10:38 AM, Justin Cohen<[email protected]>
> >>   wrote:
> >>
> >>>
> >>> Is there a way to configure  hbase.client call timeouts?  If we have a
> >>> network outage or if  hbase/zk goes down for some reason, we want our
> >>> table.puts to  timeout reasonably (5-15 seconds) so we can queue them up
> >>>  for
> >>> later.  We also want scans and gets to timeout so we can  fail gracefully.
> >>>  I've played with some of the retries and pause  configs but I can't seem
> >>> to
> >>> get a consistent  timeout. It's often over 30 seconds, and occasionally it
> >>> never  times out.
> >>>
> >>> Also, when hbase does come back,  there seems to be a good 30-60 second
> >>> delay
> >>>  before we can contact region servers.
> >>>
> >>> Right now  I'm testing this using hbase in standalone mode, bring up and
> >>>  down
> >>> stop-hbase.sh and  start-hbase.sh
> >>>
> >>> Any tips?
> >>>  Justin
> >>>
> >>>
> >
> 

Reply via email to