Thanks Josh. But what do you mean my jstack'ing? I'm unfamiliar with
that term. A better question would be how can one troubleshoot such a
thing?
btw
I am the sole user on this cluster.
On Tue, Oct 7, 2014 at 4:18 PM, Josh Elser josh.el...@gmail.com wrote:
Ok, this record:
tcp0
Jstack is a tool which can be used to tell a java process to dump the
current stack traces for all of its threads. It's usually included with the
JDK. `kill -3 $pid` also does the same. If the output can't be respected
automatically to your shell, check the stdout for the process you gave as
an
Just for the record, I finally got to the bottom of things. One of my
Tservers was running out of memory. I hadn't noticed. I had my SA
allocate a lttle more--each node now has 6G up from 2G--and things are
working better.
On Oct 8, 2014 10:09 AM, Josh Elser josh.el...@gmail.com wrote:
Did you find the message in the tserver*.out, terver*.err or the monitor
page?
(Thanks for the follow-up message.)
On Wed, Oct 8, 2014 at 6:39 PM, Geoffry Roberts threadedb...@gmail.com
wrote:
Just for the record, I finally got to the bottom of things. One of my
Tservers was running out of
