[
https://issues.apache.org/jira/browse/PHOENIX-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729169#comment-16729169
]
Lars Hofhansl edited comment on PHOENIX-5082 at 12/27/18 11:37 AM:
-------------------------------------------------------------------
5. It looks like the region server now is longer cleanly shutting down. After I
stop HBase it lingers around - I'll verify that this is related!
Edit: Yep... I see this in jstack:
{code}
"omid-completor-0" #525 prio=5 os_prio=0 tid=0x00005558f70bc800 nid=0x24bc waiti
ng on condition [0x00007f7c75fb0000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x000000055022a9d8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at
java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
at
org.apache.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:307)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
{code}
Note that this is not daemon thread.
Looks like as soon as any data is inserted into a transactional table, the
region server will not shut off.
Why is the server updating the commit table (as a client)?!
Filed OMID-124
was (Author: lhofhansl):
5. It looks like the region server now is longer cleanly shutting down. After I
stop HBase it lingers around - I'll verify that this is related!
Edit: Yep... I see this in jstack:
{code}
"omid-completor-0" #525 prio=5 os_prio=0 tid=0x00005558f70bc800 nid=0x24bc waiti
ng on condition [0x00007f7c75fb0000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x000000055022a9d8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at
java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
at
org.apache.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:307)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
{code}
Note that this is not daemon thread.
Looks like as soon as any data is inserted into a transactional table, the
region server will not shut off.
Why is the server updating the commit table (as a client)?!
> Observations about the Phoenix-Omid integration
> -----------------------------------------------
>
> Key: PHOENIX-5082
> URL: https://issues.apache.org/jira/browse/PHOENIX-5082
> Project: Phoenix
> Issue Type: Task
> Reporter: Lars Hofhansl
> Priority: Major
> Attachments: Omid-profile.png, Omid-sample.png
>
>
> Filing this issue to track my observations and perhaps some fixes.
> [~ohads]
> [~jamestaylor]
> [~yonigo]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
