This one's tricky - my understanding is that Sphinx applies changes within the current connection (and perhaps new connections), but Thinking Sphinx persists connections per thread, so the connection on server two isn't ever getting reconnected and thus becoming aware of the new results.
Perhaps it's worth asking on the Sphinx forum how they recommend handling persistent connections and real-time index updates with multiple web servers? -- Pat On 08/10/2013, at 9:23 PM, Duy Vo <[email protected]> wrote: > Hi, > I have 2 web server for balancing which have thinking sphinx run on them. The > problem is I use realtime index, so if a request was handle by server 1, ts > on server 1 got new record. But ts on server 2 don't get callback where > record created so I can't search it on server 2. How can I solve this? > > -- > 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/groups/opt_out. -- 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/groups/opt_out.
