[
https://issues.apache.org/jira/browse/OMID-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811756#comment-16811756
]
Lars Hofhansl commented on OMID-143:
------------------------------------
I am not sure. :(
It sometimes happens. This is likely related to when a commit fails due to the
maximum buffer size (of the RPC to the TSO, which is limited to 10MB)
> Netty preventing HBase regionserver from exiting.
> -------------------------------------------------
>
> Key: OMID-143
> URL: https://issues.apache.org/jira/browse/OMID-143
> Project: Apache Omid
> Issue Type: Bug
> Affects Versions: 1.0.1
> Reporter: Lars Hofhansl
> Priority: Major
>
> Sorry for the barrage of issues... But once I'm on the roll...
> I found this:
> {code}
> "Hashed wheel timer #3" #10789 prio=5 os_prio=0 tid=0x00007f24c4d01800
> nid=0x915e waiting on condition [0x00007f247b166000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.jboss.netty.util.HashedWheelTimer$Worker.waitForNextTick(HashedWheelTimer.java:459)
> at
> org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:376)
> at
> org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Preventing the regionserver from exiting. HBase now uses Netty 4.1, which
> used io.netty..., so this must be due to Omid's usage of Netty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
