is there a way to probe whats going on in HMaster exceptions at a lower level? For example, a snippet of hbase client code which might tease out whats wrong with my hmaster at a lower level?
Right now, because the exception is just returned as result of an unset variable, the "hmaster still initializing" exception doesnt return much useful information. Also there arent many logs up to the point where the initialized field is set to true, and i beleive, there are alot of processes which start up to that point. -- Jay Vyas http://jayunit100.blogspot.com <http://jayunit100.blogspot.com>
