In production, I have a cron job set to run rake ts:index (we are not
currently using delta indexes). The rake task never results in an
error, but new records that should have been indexed are not showing
up when searched for. I have found, however, that if I run rake
ts:restart after ts:index, the search results are accurate after the
restart.

Is this the expected TS behaviour? I noticed on
http://freelancing-god.github.com/ts/en/deployment.html that ts:index
is the command suggested to be put in the cronjob.

I've noticed that running ts:rebuild instead of ts:index does work as
expected (since ts:rebuild restarts the daemon too), but this results
in downtime while the index is rebuilt.

Is there a way to properly reindex and restart the daemon without
losing search functionality while the index is occuring and without
missing records?

(We're using Sphinx 2.0.3-release and TS 2.0.11.)

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to