Okie. So if you don't mind can you attach your logs. What is the split policy and what is the size of the region?
Its better we take a look at it and solve the problem if it is a kernel problem. Regards Ram On Fri, Feb 8, 2013 at 6:09 PM, kiran <[email protected]> wrote: > after some searching i found that main reason for regions with same keys is > splitting and it is the culprit in our case for inconsistency. But I set my > filesize to a very large size but i am unsure why still splitting is > happening > > > On Fri, Feb 8, 2013 at 1:20 PM, kiran <[email protected]> wrote: > > > Thanks samar and ramakrishna > > > > I did use option 2 and deleted /hbase from the zkcli shell. I restarted > > the cluster now there are more regions in transition. Will it take some > > time to complete since it is a new assignment ? > > > > My hase version is 0.94.1, and I have a doubt with the property > > hbase.hregion.max.filesize. I set it to a very large value of 100GB. But > > some how table regions are not splitted as per the property. > > > > > > On Fri, Feb 8, 2013 at 12:45 PM, samar kumar <[email protected] > >wrote: > > > >> May be ./bin/hbase hbck -repairHoles could be helpful.. > >> > >> > >> On 08/02/13 12:38 PM, "Samir Ahmic" <[email protected]> wrote: > >> > >> >Hi, Kiran > >> > > >> >Welcome to beautiful world of HBase transition states :) . When i face > >> >RIT issue this are steps that i use to resolve it: > >> > > >> >1. hbase hbck -fixAssignments (this depends on your version of hbase > >> >it can be also just -fix) > >> > > >> >If you don't have luck with 1. then you will need manual intervention: > >> >Remove hbase znodes from zookeeper (use hbase zkcli) and options rmr > >> >(or delete ) /hbase, and then restart cluster. > >> > > >> >This should help you resolve RITs. > >> > > >> >Regards > >> > > >> > > >> > > >> >On Fri, Feb 8, 2013 at 7:50 AM, kiran <[email protected]> > >> wrote: > >> >> PENDING_OPEN > >> >> > >> >> > >> >> On Fri, Feb 8, 2013 at 12:16 PM, samar kumar > >> >><[email protected]>wrote: > >> >> > >> >>> Can you mention the state of the region.. You can find the details > in > >> >>>you > >> >>> master status page > >> >>> > >> >>> On 08/02/13 12:09 PM, "kiran" <[email protected]> wrote: > >> >>> > >> >>> >We ran the command unassign 'REGIONNAME',true the output is > >> >>>"completed in > >> >>> >57 sec", but still region is in transition. > >> >>> > > >> >>> > > >> >>> >On Fri, Feb 8, 2013 at 12:05 PM, samar kumar > >> >>> ><[email protected]>wrote: > >> >>> > > >> >>> >> Was the unassigning successful ? > >> >>> >> > >> >>> >> If not you can force it by - unassign 'REGIONNAME', true > >> >>> >> > >> >>> >> Regards, > >> >>> >> Samar > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> On 08/02/13 12:01 PM, "kiran" <[email protected]> > wrote: > >> >>> >> > >> >>> >> >i issued unassign and close_region both but the region is still > in > >> >>> >> >transition also I deleted the .META entry for the region. Do I > >> >>>need to > >> >>> >> >restart master ? > >> >>> >> > > >> >>> >> > > >> >>> >> >On Fri, Feb 8, 2013 at 11:18 AM, samar kumar > >> >>> >> ><[email protected]>wrote: > >> >>> >> > > >> >>> >> >> Regions should never overlap > >> >>> >> >> Incase a region is in transition for a long long time, you > could > >> >>> >> >>possibly > >> >>> >> >> force Unassign a region , if you are ok to lose the region. > >> >>> >> >> Regards, > >> >>> >> >> Samar > >> >>> >> >> > >> >>> >> >> On 08/02/13 11:14 AM, "kiran" <[email protected]> > >> >>>wrote: > >> >>> >> >> > >> >>> >> >> > are always in transition ? Because of the > >> >>> >> >> >cluster is not balancing and regionservers are going down one > >> by > >> >>> >>one. > >> >>> >> >>As > >> >>> >> >> >only some regions servers are handling the requests. > >> >>> >> >> > > >> >>> >> >> >Another wierd thing is the region stuck in transition > startkey > >> >>> >>matches > >> >>> >> >> >with > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > >> >>> >> > > >> >>> >> >-- > >> >>> >> >Thank you > >> >>> >> >Kiran Sarvabhotla > >> >>> >> > > >> >>> >> >-----Even a correct decision is wrong when it is taken late > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> > > >> >>> > > >> >>> >-- > >> >>> >Thank you > >> >>> >Kiran Sarvabhotla > >> >>> > > >> >>> >-----Even a correct decision is wrong when it is taken late > >> >>> > >> >>> > >> >>> > >> >> > >> >> > >> >> -- > >> >> Thank you > >> >> Kiran Sarvabhotla > >> >> > >> >> -----Even a correct decision is wrong when it is taken late > >> > >> > >> > > > > > > -- > > Thank you > > Kiran Sarvabhotla > > > > -----Even a correct decision is wrong when it is taken late > > > > > > > -- > Thank you > Kiran Sarvabhotla > > -----Even a correct decision is wrong when it is taken late >
