[
https://issues.apache.org/jira/browse/SOLR-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley reopened SOLR-6406:
--------------------------------
Reopening... something is wrong.
Overview of what happened:
- I tested my update to DistributedUpdateProcessor in SOLR-8203 alone, and
verified that there were no shard inconsistency failures
- Mark tested his change to use shutdownNow on the updateExecutor alone (w/o my
change), and reported no shard inconsistency failures, but he did hit hangs,
which led to me to tackle this issue
- I tested this issue w/o my fix in SOLR-8203, to more easily reproduce the
hang, and to verify it had been fixed - I was not looking for shard
inconsistency failures
- Now that both patches are committed, I'm seeing shard inconsistency failures
again!
Either:
- I messed up this patch somehow, causing updates to be further reordered
- This idea of this patch is somehow incompatible with SOLR-8203 (unlikely)
- Something else in trunk has changed (unlikely)
First, I'm going to go back to trunk w/o both of these patches and start with
just the check in the DistributedUpdateProcessor, and move on from there until
I find out what reintroduced the problem.
> 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]