Closed Bug 468820 Opened 16 years ago Closed 16 years ago

Need help installing Sphinx on load test cluster

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: laura, Assigned: chizu)

References

Details

I need to run load tests on the new SUMO search.  To do that I need to install Sphinx on the load test cluster.  Right now I can't ssh into these VZs to do this.  I'm not even sure whether I should be able to do that or whether that is an IT task.  One way or the other, I need help :)
Blocks: 460216
btw, info in bug 463708 is useful
Sounds like there are a couple of issues here:

1.  I think I *should* be able to ssh into these boxes but it just times out, which only IT can do something about.

2. Trevor made sphinx packages for use in prod, where might I find those with instructions on how to install them?  Obviously we want the load test configuration to be as close to prod as possible.
PS if Trevor wants to go ahead and repeat the install on these boxes that would be just dandy ;)
I should also add, load testing blocks the release, so upping importance of this bug.
Severity: major → critical
Assignee: server-ops → thardcastle
Ping?  The release is intended for Tuesday.  We need time to load test beforehand, which means we need to be able to get to these boxes.
Started up all the virtual environments.

Here's the current production Sphinx install, this will need some changes for clustering before it goes live:
rpm -i sphinx-0.9.8.1-r1533.i386.rpm
mkdir -p /usr/local/sphinx/index
mkdir -p /usr/local/sphinx/bin
chown apache /usr/local/sphinx/*
Place attachment 346955 [details] at /etc/sphinx.conf
Place attachment 346957 [details] at /usr/local/sphinx/index/stopwords.txt

I've installed it on the loadtest cluster. To properly test what we'll be doing for production, sphinx should run on a subset of the cluster (2-4 webheads) with all of them talking to that subset.

To start searchd:
sudo -c apache /usr/bin/searchd
Oops, should be:
sudo -u apache /usr/bin/searchd
This is done, thank you Trevor, I forgot to close it.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.