Pardon my limited knowledge of asynchbase internals, Benoit. HBASE-3777 is big. It is not specific to RegionServer operations.
It is now easy to see a good design (M. C. Srivas<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=srivas>disagrees) which wasn't in 0.90 or trunk. w.r.t. M. C. Srivas<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=srivas>'s comments, the way connection-specific properties were chosen has historical reason. It has to cover all use cases from both server, client and unit test code where developer(s) expected new connection to be made. One of my initial goals was to make TableOutputFormat more user friendly. After HBASE-3777 gets checked in, we will continue listening to user feedback and see if my goal has been achieved. Thanks On Fri, Apr 29, 2011 at 12:56 AM, tsuna <[email protected]> wrote: > On Thu, Apr 28, 2011 at 7:59 PM, Ted Yu <[email protected]> wrote: > > I would be happy to know that solution. > > If that solution exists, Karthick and I wouldn't have spent 2 weeks on > > HBASE-3777 :-) > > I haven't had time to read through this gigantic issue, so sorry if my > question is stupid. Is this problem specific to the RegionServer, or > does it also affect regular HBase clients? Your blog post refers to > HBASE-3734, which seems specific to RegionServer operations, but I see > that the v6 of the patch on HBASE-3777 also touches a lot of code that > relates to regular HBase clients. > > I'm having trouble understanding why this is such a big issue. > asynchbase maintains exactly one connection per RegionServer you need > to interact with, and it does NOT maintain any ZooKeeper connection at > all, except when it needs to find -ROOT- (which typically happens only > when your application starts, and then very rarely as servers hosting > .META. and -ROOT- fail). > > -- > Benoit "tsuna" Sigoure > Software Engineer @ www.StumbleUpon.com >
