Hi Joram Apologies if this is covering stuff you already knew:
* In config/thinking_sphinx.yml for your production environment you'll want to set mysql41 to the port you prefer (or don't set it, and Sphinx will run on port 9306), and you'll need to set address to the server Sphinx is running on. * In config/database.yml for your production environment you'll want to include your database connection settings. Both of these files should be present on each server your app code is on - they're required on your app server so it knows how to talk to both the database and Sphinx, and they're required on your Sphinx server so Sphinx can bind itself to the appropriate address, and it can talk to the database using the correct credentials when indexing. Hope this helps - do let me know if you've got further questions. Cheers -- Pat On 2 Apr 2014, at 1:37 am, Joram Walekhwa Okwaro <[email protected]> wrote: > Hi Pat, > > Thanks for the reply. You mentioned this: "...and also set the address of the > Sphinx server (so it binds to that address instead of 127.0.0.1, which is the > default).". You mean the app server right? The app server is connecting to a > remote instance of searchd through MySQL so the address of the app server is > set in MySQL configs right? > > Secondly, I have opened up MySQL to accept remote connections from my app > server, but even before I tried it, I was wondering how Thinking Sphinx on my > app server will be able to connect to MySQL without the details of the user I > created and granted db privileges let alone the password. Is there an option > to declare this in thinking_sphinx.yml? Unless I've got this part all wrong. > This indeed ended up being a problem since I still don't have access. I get > thinkingSphinx:SphinxError with the message "Access denied for user > 'ubuntu'@'ip-77-77-77-77.eu-west-1.compute.internal' (using password: NO)" > > Would appreciate some help. Thanks. > > Joram. > > > > > > On Tue, Apr 1, 2014 at 2:08 AM, Pat Allan <[email protected]> wrote: > Hi Joram > > Yes, the mysql41 port is how Sphinx can be connected to. You'll need to make > sure that's set and opened up to the world, and also set the address of the > Sphinx server (so it binds to that address instead of 127.0.0.1, which is the > default). > > There was a bug with the address setting discovered recently - it's in the > Riddle gem, but you can get the latest by using the following in your Gemfile: > > gem 'riddle', '~> 1.5.10', > :git => 'git://github.com/pat/riddle.git', > :branch => 'develop', > :ref => '0dfe38063c' > > Cheers > > -- > Pat > > On 1 Apr 2014, at 12:47 am, Joram Okwaro <[email protected]> wrote: > > > Hi Pat, > > > > So we still opted for a remote sphinx server. I was able to set up the > > server and connect to the production database remotely. I can therefor > > index the production db and thus generate the indices in the sphinx server. > > Thanks for the help once again. I am now faced with another 'big picture' > > issue. > > > > 1. So now that my app server will be sending search queries to searchd on > > the sphinx server, I'm guessing I need to open up the port on which Sphinx > > runs on the sphinx server? There's a mysqld41 setting that I have set to > > the mysql port on my sphinx server. This I'm assuming is the port that I > > need to open to get to searchd? Is this all that's needed in this server as > > far as configuration is concerned? > > > > Maybe my big picture looking at it from the app server is all wrong :) > > > > On Tuesday, March 18, 2014 3:31:01 PM UTC+3, Pat Allan wrote: > > It really depends on how many records (and how much data per record) you're > > indexing... Sphinx is generally pretty well-behaved, but I guess it depends > > on how limited the resources are on your app server. Whenever indexing > > happens, it will mean there's plenty of traffic between the indexer and > > your database, so having them share a machine is not a bad idea (instead of > > adding extra external network traffic). > > > > On 18 Mar 2014, at 5:57 pm, Joram Okwaro <[email protected]> wrote: > > > >> Hi Pat, > >> > >> Thanks for the quick responses on both threads. I took on this task from a > >> colleague of mine so I don't know yet how much research he did on Sphinx > >> performance. That was the main reason why we opted for a remote server. > >> The idea was that Sphinx was too resource-heavy and therefore a risk for > >> our app server which we can't afford to be slow. I would appreciate your 2 > >> cents on this. Otherwise, thank you once again for your help. You have > >> helped a great deal. I'll let you know if I encounter any specific issues. > >> > >> Thanks! > >> > >> On Tuesday, March 18, 2014 9:18:15 AM UTC+3, Pat Allan wrote: > >> Didn't quite cover this in the other thread. > >> > >> On 18 Mar 2014, at 5:06 pm, Joram Okwaro <[email protected]> wrote: > >> > >> > Hi Guys, > >> > > >> > I've already replied to a thread that I hope Pat can reply to about this > >> > but I thought just in case he's too busy, someone here can help me out > >> > in the meantime. I'm having trouble finding concise documentation on how > >> > to set up a remote Sphinx server. My main questions are related to > >> > Sphinx 3.1.0 and maybe the answer might be that I need to go back to > >> > version 2 to set this up painlessly. > >> > > >> > 1. From my understanding, I need to set up Sphinx on my remote server > >> > and also a copy of my Rails application (with Thinking Sphinx of course) > >> > in order to index my models. Is this still the case? > >> > >> Yup. > >> > >> > 2. If point #1 is the case, how does the indexer index my database which > >> > lives on the app server. Unless I have to set up a database on the > >> > search server too which doesn't make sense. I'm pretty lost as you can > >> > see :) So please help. How would this generally work? That's the big > >> > question. > >> > >> You'll need to have your database accessible remotely - and have the > >> appropriate details in config/database.yml. > >> > >> If you're going to the effort of having Sphinx on its own server, do you > >> have the database on its own server too? Perhaps it's worth discussing why > >> you want to have Sphinx on its own server? > >> > >> Cheers > >> > >> -- > >> Pat > >> > >> -- > >> 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. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Thinking Sphinx" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/thinking-sphinx/vh51ahsbDXA/unsubscribe. > To unsubscribe from this group and all its topics, 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. -- 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.
