Thanks for your prompt reply. Just now I have restarted the whole cluster to continue my testing, and I will do as you suggested when the lock repeats.
Best, Arber On Wed, Sep 30, 2009 at 11:31 AM, stack <[email protected]> wrote: > Do you know the region? If so, find which server by grepping region in > master log. Once you have that, thread dump the locked up regionserver. > Make an issue and attach the thread dump then lets chat on it over there? > Thanks, > St.Ack > > On Tue, Sep 29, 2009 at 8:26 PM, Yabo-Arber Xu > <[email protected]>wrote: > >> Seems not a row locked, but the whole region. As any data request to a >> particular block was suspended. Same thing happened on the other two >> tables. Likely a dead lock happened somewhere, but i have no clue >> where to find it... >> >> Best, >> Arber >> >> >> >> On Wed, Sep 30, 2009 at 11:19 AM, stack <[email protected]> wrote: >> > So, a row was locked? What do your programs do? Do they take out a row >> > lock? They do not free it? Maybe an error? >> > St.Ack >> > >> > On Tue, Sep 29, 2009 at 6:59 PM, Yabo-Arber Xu <[email protected]> wrote: >> > >> >> Hi there: >> >> >> >> I was running a shell ( in parallel on multiple machines) that >> >> encloses a few programs accessing HBase. At some point all the >> >> programs are all suspended, and later I found the reason was because >> >> some region in HBase is locked. Any program that accesses that regions >> >> was suspended immediately ( in the call of getScanner ). >> >> >> >> Anybody have ideas what might be the causes? >> >> >> >> Best, >> >> Arber >> >> >> > >> >
