You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2015/11/01 21:18:27 UTC

[jira] [Commented] (SOLR-6406) ConcurrentUpdateSolrServer hang in blockUntilFinished.

    [ https://issues.apache.org/jira/browse/SOLR-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984535#comment-14984535 ] 

Yonik Seeley commented on SOLR-6406:
------------------------------------

OK, so I haven't hit any hangs with this latest patch and shutdownNow() on the associated executor.  Interestingly enough though, this still results in inconsistent shard failures.  My guess is that the shutdown of the executor is done as one of the last steps in CoreContainer.shutdown(), which still gives time for streaming update requests to continue streaming.

> 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, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org