I work with Nathaniel and can answer those questions. We are using Sun's jvm.
$ java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
We also tried one node on a newer version but saw the same thing...
$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
We are running the lastest version of CentOS 5.
It looks like just the "PRI IPC Server handler" are blocked but the "IPC Server handler" are not.
What is the difference between the PRI and non-PRI handlers?
I'm not to adept at reading jstack but it seems like they are trying to lock 0x000000058f3fad08
which is held by "PRI IPC Server handler 4 on 60020" daemon prio=10 tid=0x00002aaac0e52000 nid=0x92e
in Object.wait() [0x000000004aa0e000]
Thanks,
~Jeff
On 9/5/2012 4:39 PM, Stack wrote:
On Wed, Sep 5, 2012 at 2:58 PM, Nathaniel Cook <nathani...@qualtrics.com> wrote:
We ran a jstack on the both the RS process and the hbase shell process
trying to do the scan.
Jstack log for RS:
http://pastebin.com/9Y9t5ERE
What JVM (I don't know what (20.10-b01 mixed mode) is).
I see a bunch of this:
"PRI IPC Server handler 5 on 60020" daemon prio=10
tid=0x00002aaac10a1800 nid=0x92f waiting for monitor entry
[0x000000004ab0f000]
java.lang.Thread.State: BLOCKED (on object monitor)
at .....
But when I go to look for other instances of the object monitor, I
don't find any. I see this for each instance of BLOCKED (Or at least,
the two or three I checked).
Whats your OS?
St.Ack
--
Jeff Whiting
Qualtrics Senior Software Engineer
je...@qualtrics.com
