Thanks Shrijeet Thanks for the information! We have seen this couple times recently. Last week, it was very long(like 40+ minutes before we restart). I will follow up on that discuss thread. Thanks a lot!!
Tian-Ying -----Original Message----- From: Shrijeet Paliwal [mailto:[email protected]] Sent: Friday, January 25, 2013 11:02 AM To: Ted Yu Cc: Async HBase; [email protected] Subject: Re: AsynchBase client holds stale dead region server for long time even after the META has already been update. This has been raised earlier https://groups.google.com/d/topic/asynchbase/xE2lYE6CbmQ/discussion , https://groups.google.com/d/topic/asynchbase/nfLTwjdqq9M/discussion . It does look like a bug but a hard one to reproduce. We have been seeing this it our production environment, efforts are on to reproduce this in testing environment. -- Shrijeet On Fri, Jan 25, 2013 at 10:58 AM, Ted Yu <[email protected]> wrote: > Tianying: > I moved user@ to Cc. > > There is a google group for asynchbase. > Please subscribe to that group. > > Can you clarify the version of asynchbase you're using ? > > Cheers > > On Fri, Jan 25, 2013 at 10:54 AM, Tianying Chang <[email protected]>wrote: > >> Hi >> >> One machine crashed in our cluster. After 3 minutes, the master >> detect it and re-assign the regions to other region servers. The >> regions are back online on other RS within one minute. But the >> asynchbase client still hold old dead regionserver for 50 minutes and >> cause data loss. We have to restart the AsynchBase client and that fixed the >> problem. >> >> It seems there is a bug in AsyncBase client code. Has anyone else >> seen this? If I want to open a bug for Asynchbase, should I use Hbase >> jira? or is there a dedicated one for Asynchbase? I seems cannot find >> dedicated AsynchBase jira. >> >> Thanks >> Tian-Ying >> > > -- > > >
