Hi David

In recent versions of Thinking Sphinx (v3.1.1 definitely, and I think 3.1.0 
too) guard files are put in place while indexing occurs, to avoid an index 
being processed multiple times at once. Unfortunately, these guard files aren't 
cleared out when an exception is raised during indexing... have a look in the 
folder of your index files, should be easy enough to spot.

In the upcoming v3.1.2 release, there'll be better logging to note if these 
guard files are blocking indexing requests, and they'll also be cleared out if 
an exception is raised.

-- 
Pat

On 25 Oct 2014, at 5:49 pm, David Krmpotic <[email protected]> wrote:

> Hi, I use TS 3.1.1 and Sphinx 2.2.5 on the server and this is my index 
> definition:
> 
> ThinkingSphinx::Index.define :post, with: :active_record, delta: true do
>   indexes :text
>   indexes :tags
>   
>   has :user_id
>   has :created_at
> end
> 
> After upgrading both TS and Sphinx every few days of webapp usage, I notice 
> that new records are no longer indexed.
> 
> I checked and they are really not in the sphinx post_core or post_delta 
> indices.
> 
> After reindexing and restarting sphinx, it's ok for a few days then the same 
> happens.
> 
> How to troubleshoot this further?
> 
> thank you
> david
> 
> 
> -- 
> 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.

Reply via email to