[
https://issues.apache.org/jira/browse/SOLR-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468871#comment-17468871
]
Gus Heck commented on SOLR-15892:
---------------------------------
I'd like to understand the use case that generates the large number of delete
requests if you can share some details. There's a lot of ways that could be bad
design and only a few that come to mind where it would be necessary (i.e. cases
with nested documents that are tricky to delete correctly by query and easy to
delete by id). When I can look at code I'll still consider your patch of course.
> RoutedAliasUpdateProcessor not distributing delete and commit requests.
> -----------------------------------------------------------------------
>
> Key: SOLR-15892
> URL: https://issues.apache.org/jira/browse/SOLR-15892
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, main (9.0), 8.9,
> 8.10, 8.11
> Reporter: Ankur Gupta
> Priority: Minor
> Fix For: main (9.0), 8.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the RoutedAliasUpdateProcessor is not distributing and forwarding
> all delete and commit requests for a RoutedAlias to a fixed shard leader.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
