Re: UPDATE collection's Rule-based Replica Placement

Do you look for something that would move existing collection replicas to comply with a new set of rules? I'm afraid that doesn't exist, but you can use the Collection API to move replicas "manually". Ilan On Tue, Feb 9, 2021 at 1:10 PM mosheB wrote: > > Hi community, > Using Solr 8.3, is there

Re: Identifying open segments.

Are you trying to copy the index by an external process not running in the Solr JVM? I believe this is risky if the Solr JVM is running at the same time. For example segments can be deleted by Solr. There might also be closed segments that you do not need but that are still on the disk (no longer p

Re: list of all possible values for REQUESTSTATUS

If you don't want to download the code, you can look at REQUESTSTATUS_OP in CollectionOperation (in CollectionsHandler.java). Ilan On Mon, Dec 7, 2020 at 4:57 PM elisa

Re: Unloading and loading a Collection in SolrCloud with external Zookeeper ensemble

An unelegant alternative is to back up and delete a collection in lieu of unload, restore it in lieu of load... Ilan On Sun, Nov 15, 2020 at 6:56 PM Erick Erickson wrote: > I don’t really have any good alternatives. There’s an open JIRA for > this, see: SOLR-6399 > > This would be a pretty big

Re: Solr migration related issues.

I second Erick's recommendation, but just for the record legacyCloud was removed in (upcoming) Solr 9 and is still available in Solr 8.x. Most likely this explains Modassar why you found it in the documentation. Ilan On Tue, Nov 3, 2020 at 5:11 PM Erick Erickson wrote: > You absolutely need co

Re: [EXTERNAL] Getting rid of Master/Slave nomenclature in Solr

I disagree Ishan. We shouldn't get rid of standalone mode. I see three layers in Solr: 1. Lucene (the actual search libraries) 2. The server infra ("standalone Solr" basically) 3. Cluster management (SolrCloud) There's value in using lower layers without higher ones. SolrCloud is a good

Re: Getting rid of Overseer nomenclature in Solr

Thing is, we can get a cluster wide lock when needed through zookeeper. It's collection cluster wide lock BTW most of the time (or locks on shards or replicas of a collection). We could already today (in master) have multiple Overseer and distribute (partition) the collections to them... In 8x we

Re: [EXTERNAL] Getting rid of Master/Slave nomenclature in Solr

+1 to Jan's "clustered" vs "non clustered". If we clean up terminology, I suggest we also clarify the meaning and use of Slice vs Shard vs Leader vs Replica vs Core. Here's my understanding: I consider Slice == Shard (and would happily drop Slice): a logical concept of a specific subset of a coll

Re: Getting rid of Master/Slave nomenclature in Solr

Would master/follower work? Half the rename work while still getting rid of the slavery connotation... On Thu 18 Jun 2020 at 07:13, Walter Underwood wrote: > > On Jun 17, 2020, at 4:00 PM, Shawn Heisey wrote: > > > > It has been interesting watching this discussion play out on multiple > open

Re: Lucene-Solr project split

See also https://issues.apache.org/jira/browse/SOLR-14521 On Tue, Jun 9, 2020 at 3:17 PM Ilan Ginzburg wrote: > Yes. > > > https://lists.apache.org/thread.html/raab13cabe321d12b6cda7dc6e529176f51ece31d30f00997dd36570a%40%3Cdev.lucene.apache.org%3E > > Ilan > > On Tue

Re: Lucene-Solr project split

Yes. https://lists.apache.org/thread.html/raab13cabe321d12b6cda7dc6e529176f51ece31d30f00997dd36570a%40%3Cdev.lucene.apache.org%3E Ilan On Tue, Jun 9, 2020 at 3:10 PM Dominique Bejean wrote: > Hi, > > One of my clients claims that the Lucene-Solr project will split into two > separate projects