[
https://issues.apache.org/jira/browse/SOLR-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971436#comment-14971436
]
Yonik Seeley commented on SOLR-8129:
------------------------------------
{quote}
One mystery is why ConcurrentUpdateSolrClient is trying to create a new Runner
when there is obviously another runner already running (since it still accepts
and sends new updates after that point).
{quote}
Mark pointed me at this comment in ConcurrentUpdateSolrClient:
// see if queue is half full and we can add more runners
// special case: if only using a threadCount of 1 and the queue
// is filling up, allow 1 add'l runner to help process the queue
[~thelabdude] It looks like you added that comment... but it's not clear to me
how the code implements that special case. Thoughts?
> HdfsChaosMonkeyNothingIsSafeTest failures
> -----------------------------------------
>
> Key: SOLR-8129
> URL: https://issues.apache.org/jira/browse/SOLR-8129
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Attachments: fail.151005_064958, fail.151005_080319
>
>
> New HDFS chaos test in SOLR-8123 hits a number of types of failures,
> including shard inconsistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
