Hi Stack, I think you are right. the multiple queue change was introduced by HBASE-11355(0.98.4). if there is only 1 queue, the stuck will not happen. some handlers are gone but still some left to service the request(all handlers gone looks a rare case)... so the problem might have been there for some time, the change just exposes it.
On Sun, Aug 24, 2014 at 7:51 AM, Stack <[email protected]> wrote: > On Sat, Aug 23, 2014 at 4:06 PM, Stack <[email protected]> wrote: > > > ... > > If you were looking for something to try, set > hbase.ipc.server.callqueue.handler.factor > > to 0. Multiple queues is what is new here. It should not make a > difference > > but... > > > > > Hmm. Ignore above I'd say. I can't see how it would trigger this issue. > Let me make a patch to give us more info and will have the handler keep > going.... > > St.Ack >
