617302 - Fixing the SQL sharding

Status: VERIFIED FIXED

Description

[Tarek Ziadé (:tarek)]

Things to fix in server-storage:

1. the python creates automatically the table in case it does not exists yet in the DB - to be deactivated for us
2. the host-specific config fails, all goes in the default db/base - see if HTTP_HOST is OK
3. the modulo on the wbo table misses

Comment 1

[Tarek Ziadé (:tarek)]

1. is now fixed

  - http://hg.mozilla.org/services/server-storage/rev/fb2c77e35cc6 
  - http://hg.mozilla.org/services/server-core/rev/1b334cee1792

  For our server, we jsut need to add a new option in [auth] and [storage], 
  that is "created_tables = false"

  with that option, the server will fail if case the tables does not already exists and not attempt to create new tables.

Comment 2

[Tarek Ziadé (:tarek)]

3. is now fixed in http://hg.mozilla.org/services/server-storage/rev/e53b1039dbcb

  For our server, we just need to add a new option in [storage] that is "shard = true"
  
  with that option, all wbo queries will be done in the right table by doing a user_id modulo 10

Comment 3

[Tarek Ziadé (:tarek)]

I am now finding out why HTTP_HOST fails on the dev servers, then will fix 2. and deploy everything back with the new configuration on -dev.

Comment 4

[Tarek Ziadé (:tarek)]

I found the issue for 2. and work on a fix now. That'll take me 2/3 hours then we can redeploy everything.

Comment 5

[Tarek Ziadé (:tarek)]

2. is now fixed at http://hg.mozilla.org/services/server-storage/rev/e46b6e8156f6

Building RPMs and deploying to -dev

Comment 6

[Tarek Ziadé (:tarek)]

validated on web01. 

Richard, I am creating a new bug with the configurations changes to puppetize

Comment 7

[Tracy Walker [:tracy]]

Verified er last comment