[
https://issues.apache.org/jira/browse/SOLR-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995428#comment-16995428
]
Ilan Ginzburg commented on SOLR-14079:
--------------------------------------
[~ysee...@gmail.com], is there a fundamental reason this can't work async, or
is it rather an issue in the async call/response pairing that make such calls
fail under some conditions? (for example a "dangling" non consumed response
from a previous call that is then returned in error in a future async call)
As you know, we've observed these async calls to sometimes work, and sometimes
fail. I'd rather fix issues in the async calling logic that might benefit other
areas than work around them and switch to synchronous calls. Plus, there's a
value to async calls (if they can be made in parallel, which is not the case in
current split code) because a single thread can do multiple things at the same
time.
> 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
