One option: use process explorer to find out the TID's of the java process ( instructions <https://superuser.com/questions/462969/how-can-i-view-the-active-threads-of-a-running-program>), screen cap that, then also run jstack against the running cassandra process out to a file a few times (instructions <https://docs.oracle.com/javase/7/docs/technotes/tools/share/jstack.html>).
We should be able to at least link up the TID to the hex thread # in the jstack output to figure out who/what is spinning on there. On Fri, Oct 16, 2015 at 1:28 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > On 10/16/2015 12:02 PM, Alaa Zubaidi (PDF) wrote: > >> No OOM in any of the log files, and NO long GC at that time. >> I attached the last 2 minutes before it hangs until we restart cassandra >> after hour an half. >> > > Your logs show gossip issues with some seed nodes. `nodetool gossipinfo` > on all nodes might be an interesting place to start. > > -- > Michael >
