[
https://issues.apache.org/jira/browse/SOLR-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995263#comment-14995263
]
Yonik Seeley commented on SOLR-6406:
------------------------------------
The other variants:
4) trunk with only client changes reverted (i.e. DUH check enabled,
shutdownNow used)
5) trunk with client + DUH changes reverted (i.e. only shutdownNow enabled)
6) trunk with alternate client changes (only changes to blockUntilFinished)
7) trunk with alternate client changes 2 (only changes to blockUntilFinished,
but using former isTerminated instead of isShutdown)
I managed to get inconsistent shard runs with all of these.
The common element is shutdownNow being used on the shard update executor.
> ConcurrentUpdateSolrServer hang in blockUntilFinished.
> ------------------------------------------------------
>
> Key: SOLR-6406
> URL: https://issues.apache.org/jira/browse/SOLR-6406
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Yonik Seeley
> Fix For: 5.0, Trunk
>
> Attachments: CPU Sampling.png, SOLR-6406.patch, SOLR-6406.patch,
> SOLR-6406.patch
>
>
> Not sure what is causing this, but SOLR-6136 may have taken us a step back
> here. I see this problem occasionally pop up in ChaosMonkeyNothingIsSafeTest
> now - test fails because of a thread leak, thread leak is due to a
> ConcurrentUpdateSolrServer hang in blockUntilFinished. Only started popping
> up recently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
