Thanks guys, we had to restart the master for another issue an that cleaned the deadserver list too.
On 05/02/13 9:08 PM, "Bryan Beaudreault" <[email protected]> wrote: >There really should be no issue or slowdown involved with restarting the >masters. The operation only takes 1-2 seconds and is pretty much >transparent to clients. We run hundreds of M/R jobs as well as a handful >of online APIs hitting hbase and have not seen any issue restarting >masters >at will whenever we need to. > > >On Tue, Feb 5, 2013 at 4:04 AM, Nicolas Liochon <[email protected]> wrote: > >> Hi, >> >> Looking at the code, no. >> >> Nicolas >> >> >> On Tue, Feb 5, 2013 at 9:21 AM, samar kumar <[email protected] >> >wrote: >> >> > Thanks Adrien. >> > Sure , but is there any other way without stoping the masters. >>Anything >> > like cleaning the zk. Is there a time-out which cleans the dead rs or >>max >> > count . >> > Regards, >> > Samar >> > >> > On 05/02/13 12:38 AM, "Adrien Mogenet" <[email protected]> >>wrote: >> > >> > >The easiest way is to restart your HBaseMaster. The next active >>master >> > >will >> > >not register the dead RS. >> > > >> > > >> > >On Mon, Feb 4, 2013 at 1:07 PM, Samar Kumar <[email protected]> >> > >wrote: >> > > >> > >> Hi Everyone, >> > >> I did a "status 'detailed'" and found 3 dead region servers. I >>was >> > >> hoping that the dead region servers would go aways after a while >>but >> > >>they >> > >> seem to exist for a long time now. Is there a way for these to be >> > >>removed >> > >> without restarting the master. >> > >> Using hbase 0.90.4-cdh3u3 >> > >> Regards, >> > >> Samar >> > >> >> > >> ________________________________ >> > >> >> > >> The information contained in this communication is intended solely >>for >> > >>the >> > >> use of the individual or entity to whom it is addressed and others >> > >> authorized to receive it. It may contain confidential or legally >> > >>privileged >> > >> information. If you are not the intended recipient you are hereby >> > >>notified >> > >> that any disclosure, copying, distribution or taking any action in >> > >>reliance >> > >> on the contents of this information is strictly prohibited and may >>be >> > >> unlawful. If you have received this communication in error, please >> > >>notify >> > >> us immediately by responding to this email and then delete it from >> your >> > >> system. The firm is neither liable for the proper and complete >> > >>transmission >> > >> of the information contained in this communication nor for any >>delay >> in >> > >>its >> > >> receipt. >> > >> >> > > >> > > >> > > >> > >-- >> > >Adrien Mogenet >> > >06.59.16.64.22 >> > >http://www.mogenet.me >> > >> > >> > >>
