I thought a lot more about this issue and it could be a bigger undertaking than I thought, basically any HTable operation can throw ZK-related errors and I think they should be considered as fatal.
In the mean time HBase could improve the situation a bit. You say it was spinning, do you know where exactly? Looking at the 0.90 code, if there's a ConnectionLoss it will be eaten by HCM.prefetchRegionCache and then the normal .META. querying will take place so I don't see where it could be spinning. J-D On Mon, Apr 11, 2011 at 2:13 PM, Sandy Pratt <[email protected]> wrote: > Thanks J-D. I'll keep an eye on the Jira. > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of Jean- >> Daniel Cryans >> Sent: Monday, April 11, 2011 11:52 >> To: [email protected] >> Subject: Re: Catching ZK ConnectionLoss with HTable >> >> I'm cleaning this up in this jira >> https://issues.apache.org/jira/browse/HBASE-3755 >> >> But it's a failure case I haven't seen before, really interesting. >> There's a HTable that's created in the guts if HCM that will throw a >> ZookeeperConnectionException but it will bubble up as an IOE. I'll try to >> address this too in 3755. >> >> J-D >>
