[
https://issues.apache.org/jira/browse/SOLR-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995429#comment-16995429
]
Ilan Ginzburg commented on SOLR-14079:
--------------------------------------
The patch is using different but constant async id's for the different stages.
Isn't there a risk of collision between these async split calls and other
concurrent async split calls that would be using the same id's?
> SPLITSHARD splitByPrefix doesn't work in async mode
> ---------------------------------------------------
>
> Key: SOLR-14079
> URL: https://issues.apache.org/jira/browse/SOLR-14079
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.3
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Priority: Major
> Fix For: 8.4
>
> Attachments: SOLR-14079.patch
>
>
> If you specify async=whatever in conjunction with splitByPrefix, the ranges
> are calculated by the shard leader, but that information does not make it
> back to the overseer and the split proceeds to just split down the middle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
