-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Riddle::ResponseError: No response from searchd" with seperate Sphinx and MySQL servers #528
Comments
Hi Dan Guessing we can close this issue, given #529 - but also, your stack trace has TS v2, but your gem list says TS v3, so not quite sure what's going on here. Let me know if this is a separate problem and we can re-open it. |
@pat Thanks for your help with this. You've definitely given me enough info to track the issue down. 🍔 |
been seeing the same issue at seemingly random times in our production environment only (separate app / sphinx / mysql servers) for the last few weeks.
I was able to run a rails console in our production environment when this started occuring, and noted that it happened for some but not all indexes.. so Model1.search() failed as above, Model2.search() succeeded, and ThinkingSphinx.search() failed. Then suddenly all was well again. Any suggestions or ideas (besides upgrading to TS 3)? |
I'd recommend upgrading to 2.1.0 - this has connection pooling which will reset connections and retry searches a few times when these errors crop up. On 30/05/2013, at 1:28 AM, Ben Mishkin wrote:
|
I'm getting at
Riddle::ResponseError: No response from searchd
when trying to communicate with a seperate remote Sphinx instance and a remote MySQL server using the latest versions thinking-sphinx,Everything works perfectly when testing in our local and staging environments (which both have
searchd
and a local instance of MySQL running). It's only the remote configuration that breaks.What's weird about our setup is that we have Sphinx and MySQL running on a seperate boxes from the web application server. Somehow Sphinx is supposed to use the generated
production.sphinx.conf
to know how to talk to the Sphinx instance seperately from the MySQL instance, I'm assuming.GEM VERSIONS + ENV
STACKTRACE
sphinx.conf on Sphinx instance
Any ideas????
The text was updated successfully, but these errors were encountered: