[
https://issues.apache.org/jira/browse/SOLR-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-6406:
-------------------------------
Attachment: SOLR-6406.patch
OK, how about this patch?
It's probably hard to read as an actual patch file, so basically what I did was:
- pull out the "while (!queue.isEmpty())" loop into sendUpdateStream() method.
- added a for(;;) loop around the call to sendUpdateStream() and the associated
error handling.
- stayed in the outer loop if we're the last runner and something else was
added to the queue.
- removed runnerLock and the code to resubmit ourselves to the executor.
This shouldn't change any behavior except for the hypothetical buggy behavior,
but it's completely untested at this point.
> ConcurrentUpdateSolrServer hang in blockUntilFinished.
> ------------------------------------------------------
>
> Key: SOLR-6406
> URL: https://issues.apache.org/jira/browse/SOLR-6406
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Fix For: 5.0, Trunk
>
> Attachments: CPU Sampling.png, 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]
