Hi Greg My understanding is that each mongrel is a full loaded instance of the Rails app - and so if you're making changes to indexes, then you'll need to restart the mongrels so they are aware of the changes - same as any other code changes.
Good to know you've got it figured out. Cheers -- Pat On 14/08/2010, at 8:17 AM, gjb wrote: > It turns out that all that was needed to fix the issue was restarting > the mongrels on my system. Looking at the Rails log, it appears > every mongrel loads the indexes from the models on starting up, at > least from what I can tell. Some of the mongrels must still have > been looking for the old index when I was indexing a completely > different table and basically needed this to get flushed out. > > Can anyone confirm how Thinking Sphinx and mongrels interact? > > The main issue appears to be resolved at least. > > Greg > > -- > 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. > -- 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.
