You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Namgyu Kim (Jira)" <ji...@apache.org> on 2021/01/20 15:57:00 UTC
[jira] [Assigned] (LUCENE-9661) Another classloader deadlock?
[ https://issues.apache.org/jira/browse/LUCENE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namgyu Kim reassigned LUCENE-9661:
----------------------------------
Assignee: Namgyu Kim
> Another classloader deadlock?
> -----------------------------
>
> Key: LUCENE-9661
> URL: https://issues.apache.org/jira/browse/LUCENE-9661
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 8.0, master (9.0)
> Reporter: Michael McCandless
> Assignee: Namgyu Kim
> Priority: Blocker
> Fix For: 8.x, master (9.0), 8.8
>
> Attachments: deadlock inspections.jpg, deadlock_test.patch, intellij inspection results.html
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> The {{java}} processes spawned by our Lucene nightly benchmarks sometimes randomly hang, apparently while loading classes across threads, under contention.
> I've opened [this {{luceneutil}} issue with some details|https://github.com/mikemccand/luceneutil/issues/89], but [~uschindler] suggested I open an issue here too since he has been seeing this in CI builds too.
> It is rare, maybe once a week in the nightly benchmarks (which spawn many {{java}} processes with many threads across 128 CPU cores). It is clearly a deadlock – when it strikes, the process hangs forever until I notice and {{kill -9}} it. I posted a coupled {{jstacks}} in the issue above.
> [~rcmuir] suggested using {{classcycle}} to maybe statically dig into possible deadlocks ... I have not tried that yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org