On 2/9/2018 8:20 PM, mmb1234 wrote:
Ran /solr/58f449cec94a2c75-core-248/admin/luke at 7:05pm PST
It showed "lastModified: 2018-02-10T02:25:08.231Z" indicating commit blocked
for about 41 mins.
Hard commit is set as 10secs in solrconfig.xml
Other cores are also now blocked.
https://jstack.review analysis of the thread dump says "Potential Deadlock"
for three 3 cores.
The deadlock is not detected by analysis on the fastthread.io website.
I don't know if that's because jstack.review is a better tool or not.
I do notice that you are using custom Solr components from Amazon and
VMWare. There is another user writing a thread on this list right now
who is also experiencing a lot of blocked threads. That user is ALSO
running custom components in Solr. I suspect there may be bugs in the
custom components.
Thread dump and top output are from that condition are available at
https://github.com/mohsinbeg/datadump/tree/master/solr58f449cec94a2c75_core_248/solr58f449cec94a2c75_core_248
Those screenshots were of the "htop" program. I very specifically said
to NOT use htop -- it must be the actual "top" program.
Thanks,
Shawn
