[ https://issues.apache.org/jira/browse/SOLR-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya updated SOLR-12940: ---------------------------------------- Fix Version/s: (was: 8.1) 8.2 > Optimize and expunge deletes should execute only on the leader instead of all > replicas of the collection > -------------------------------------------------------------------------------------------------------- > > Key: SOLR-12940 > URL: https://issues.apache.org/jira/browse/SOLR-12940 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud > Reporter: Shalin Shekhar Mangar > Priority: Major > Fix For: master (9.0), 8.2 > > > Optimize and expunge deletes are broadcasted to all replicas of the > collection (even to replicas of inactive shards!) but they don't need to be. > We can optimize by only executing such commands on the leader and have the > replicas pull the index over the network when ready. > Synchronizing replication recovery to happen after optimize completes was > trickier in the past when all we had was HTTP requests but now we have the > terms mechanism which goes via ZK and can be relied on. > This gives us a nice way to index/update fully and then call optimize/expunge > deletes only on the leader while replicas continue to serve query traffic > without disruption. This use-case will also need the ability to route queries > only to replicas and not to the leader. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org