[jira] [Commented] (SOLR-14928) Remove Overseer ClusterStateUpdater

["Mike Drob (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-14928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278475#comment-17278475 ] 

Mike Drob commented on SOLR-14928:
----------------------------------

[~ilan] - those performance numbers are against a non PRS version, right? Can you run a similar test with PRS and share the results?

> Remove Overseer ClusterStateUpdater
> -----------------------------------
>
>                 Key: SOLR-14928
>                 URL: https://issues.apache.org/jira/browse/SOLR-14928
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Ilan Ginzburg
>            Assignee: Ilan Ginzburg
>            Priority: Major
>              Labels: cluster, collection-api, overseer
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Remove the Overseer {{ClusterStateUpdater}} thread and associated Zookeeper queue at {{<_chroot_>/overseer/queue}}.
> Change cluster state updates so that each (Collection API) command execution does the update directly in Zookeeper using optimistic locking (Compare and Swap on the {{state.json}} Zookeeper files).
> Following this change cluster state updates would still be happening only from the Overseer node (that's where Collection API commands are executing), but the code will be ready for distribution once such commands can be executed by any node (other work done in the context of parent task SOLR-14927).
> See the [Cluster State Updater|https://docs.google.com/document/d/1u4QHsIHuIxlglIW6hekYlXGNOP0HjLGVX5N6inkj6Ok/edit#heading=h.ymtfm3p518c] section in the Removing Overseer doc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org