Gustavo, Ben's opinion is that it should not belong in the default API but in the common client that another recent thread was about. My opinion is just that I need such a functionality, wherever it is.
If the node gets the exception (or has it's own timer), as I wrote, it will shut itself down to release HDFS leases as fast as possible. If ZK is really down and it's not a network partition, then HBase is down and this is fine because it won't be able to work anyway. J-D On Wed, Jun 24, 2009 at 3:15 PM, Gustavo Niemeyer <gust...@niemeyer.net>wrote: > Hi Jean-Daniel, > > > I understand, maybe the common client is the best place. > > It sounds like something useful to have in the default API, FWIW. > > > In our situation, if a HBase region server is in the state of being > > disconnected for too long, the regions it's holding cannot be reached so > > this is a major problem. Also, if the HMaster node gets the event that an > > Out of curiosity, what do you intend to do when you get the exception? > I mean, if you didn't get the expiration exception it means that the > reconnection isn't working in any case, so how do you plan to recover? > > -- > Gustavo Niemeyer > http://niemeyer.net >