BTW, the effort you put into creating a process to totally replace your index won't be wasted. I pretty much guarantee that you'll have to re-index everything upon occasion if for no other reason than the requirements will change. "Oh, you know that field we said never would be used for phrase searches? We changed our mind"......... "We decided to support 14 new use cases....." ;)...
On Sun, Apr 15, 2018 at 10:32 PM, Moshe Recanati | KMS <mos...@kmslh.com> wrote: > Hi Shawn, > Thank you. > I just need to run full indexing due to massive changes in the document. > > Regards, > Moshe Recanati > CTO > Mobile + 972-52-6194481 > Skype : recanati > > More at: www.kmslh.com | LinkedIn | FB > > > -----Original Message----- > From: Shawn Heisey <apa...@elyograg.org> > Sent: Sunday, April 15, 2018 8:23 PM > To: solr-user@lucene.apache.org > Subject: Re: SolrCloud indexing > > On 4/15/2018 1:22 AM, Moshe Recanati | KMS wrote: >> >> We’re using SolrCloud as part of our product solution for High >> Availability. >> >> During upgrade of a version we need to run full index build on our >> Solr data. >> > > What are you upgrading? If it's Solr, you should pause/stop indexing while > you do the upgrade. You'll have to stop Solr processes to upgrade them, and > even if you're using an external load balancer, it takes a little bit of time > for failover to occur. > > It would be up to your indexing software to handle errors in that situation. > There is nothing that Solr can do about that. If your indexing software > correctly detects and handles errors, then you might be able to restart Solr > instances without a problem. > >> I would like to know if as part of SolrCloud we can manage it and make >> sure that items are available during the index so only once specific >> item is indexed it’s changing with no affect on end-user. >> > > I can't decipher exactly what you're asking here. > > Thanks, > Shawn >
