You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/17 00:03:00 UTC
[jira] [Commented] (SOLR-15146) Distribute Collection API command
execution
[ https://issues.apache.org/jira/browse/SOLR-15146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324132#comment-17324132 ]
ASF subversion and git services commented on SOLR-15146:
--------------------------------------------------------
Commit 4a78b458047c8803aed583d0d17ec6017d72b766 in solr's branch refs/heads/main from Ilan Ginzburg
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4a78b45 ]
SOLR-15146: Collection and Config Set API can run distributed on all nodes (#70)
When config properties distributedClusterStateUpdates and distributedCollectionConfigSetExecution are set to true, Collection API, Config Set API and cluster state updates no longer run on Overseer but on the node handling the corresponding API request.
> Distribute Collection API command execution
> -------------------------------------------
>
> Key: SOLR-15146
> URL: https://issues.apache.org/jira/browse/SOLR-15146
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Affects Versions: main (9.0)
> Reporter: Ilan Ginzburg
> Assignee: Ilan Ginzburg
> Priority: Major
> Labels: collection-api, overseer
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Building on the distributed cluster state update changes (SOLR-14928), this ticket will distribute the Collection API so that commands can execute on any node (i.e. the node handling the request through {{CollectionsHandler}}) without having to go through a Zookeeper queue and the Overseer.
> This is the second step (first was SOLR-14928) after which the Overseer could be removed (but the code keeps existing execution options so completion by no means Overseer is gone, but it could be removed in a future release).
> -There is a dependency on the distributed cluster state changes because the Overseer locking protecting same collection (or same shard) Collection API commands from executing concurrently will be replaced by optimistic locking of the collection {{state.json}} znodes (or other znodes that will eventually replace/augment {{state.json}}).-
> The goal of this ticket is threefold:
> * Simplify the code (running synchronously and not going through the Zookeeper queues and the Overseer dequeue logic is much simpler),
> * Lead to improved performance for most/all use cases (although this is a secondary goal, as long as performance is not degraded) and
> * Allow a future change (in another future Jira) to the way cluster state is cached on the nodes of the cluster (keep less information, be less dependent on Zookeeper watches, do not care about collections not present on the node). This future work will aim to significantly increase the scale (amount of collections) supported by SolrCloud.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org