Hi Charles You could try `rake ts:index ts:restart` - the index task will generate the new configuration, process new index files, and only overwrite the existing ones when it’s all done. Sphinx may complain briefly about not understanding the new files’ unexpected schemas, but the restart should take care of that.
But certainly worth testing this a few times to be sure :) — Pat > On 28 May 2015, at 12:33 pm, Charles Cooke <[email protected]> wrote: > > We have a need to rebuild the Sphinx index after deployment. We want to > minimize the downtime for the service. > > Currently we are using ts:rebuild, which I understand does a ts:stop, > ts:index, and ts:start. We do need to do tnis since we are asding fields to > the tables. > > Would it be equivalent to do a ts:stop, ts:start, ts:index - so we would > restart with the new configuration and THEN reindex, rather than indexing > while the service is offline? > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/thinking-sphinx. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/thinking-sphinx. For more options, visit https://groups.google.com/d/optout.
