Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: timellis, Assigned: timellis)

Tracking

Details

(Assignee)

Description

8 years ago
Steps:

(1) Get Redis (http://blog.grayproductions.net/articles/setting_up_the_redis_server)
(2) Build RPM for it
(3) Install it on pm-memcache-amo* (or some staging area)

Dave Miller says he can make an RPM for it within the next day. The AMO guys say May 6th is the date they want to start using it for dev work.
(Assignee)

Updated

8 years ago
Assignee: server-ops → tellis
Reassigning to me so I don't lose it.  I'll reassign it back when the RPM is built.
Assignee: tellis → justdave

Comment 2

8 years ago
Can we also make sure the install is completely puppetized?
RPM is built and in the mozilla repo.  You should be able to specify "redis" in your package list in puppet and it'll find it.

Do you also need any client libraries by any chance?  php api I'm guessing?  Rediska, predis?
Assignee: justdave → tellis
(In reply to comment #3)
> RPM is built and in the mozilla repo.  You should be able to specify "redis" in
> your package list in puppet and it'll find it.
> 
> Do you also need any client libraries by any chance?  php api I'm guessing? 
> Rediska, predis?

Thanks Dave!  We're not going to be using redis on the PHP side for AMO, so we don't need any packages there.  The python library is pure; no C extensions yet.
How's this going?
(Assignee)

Comment 6

8 years ago
Got superceded by deadline for Firefox Sync. I think I'll have time this week to play with this.
(Assignee)

Comment 7

8 years ago
I have the Redis package appearing on the servers now. Next up, get the configuration onto the servers.
(Assignee)

Comment 8

8 years ago
Status: has been superceded by many small emergencies. I've now got an instance running on pm-memcache-amo01. Caveats-for-now: this instance is started manually (ie: won't be started at system boot). It's also configured with not-much-memory (128MB).

Can you let me know what your plan is for testing it? If we are to run Redis on pm-memcache-amo* long-term, we will need to reduce the memory memcached is using on those boxes a little to give more to Redis.
(In reply to comment #8)
> Can you let me know what your plan is for testing it? If we are to run Redis on
> pm-memcache-amo* long-term, we will need to reduce the memory memcached is
> using on those boxes a little to give more to Redis.

Thanks for getting it set up.  My redis plans so far are: distributed smart rate limiting, better cache invalidation using redis sets, and storing add-on recommendations in redis instead of the database.  I'm not sure how much memory the cache invalidation sets will need, but recommendations will probably come pretty close to the limit.

I thought we were setting this up on pm-memcache to get something up quickly, until we can get separate redis boxes provisioned?
(Assignee)

Comment 10

8 years ago
""I thought we were setting this up on pm-memcache to get something up quickly,
until we can get separate redis boxes provisioned?""

That solves the problem long-term. I am not doing any work toward provisioning the boxes. Let me know if you expected otherwise.
What's the status of this?  It sounds like we need to file a separate bug for preview/prod redis boxes and make it block this?
(Assignee)

Comment 12

8 years ago
Yes. That sounds right.
Depends on: 569631
done
Status: NEW → RESOLVED
Last Resolved: 8 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.