Closed Bug 617302 Opened 15 years ago Closed 15 years ago

Fixing the SQL sharding

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

x86_64
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tarek, Assigned: tarek)

References

Details

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
Blocks: 608039
Severity: normal → major
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.
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
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.
Status: NEW → ASSIGNED
I found the issue for 2. and work on a fix now. That'll take me 2/3 hours then we can redeploy everything.
2. is now fixed at http://hg.mozilla.org/services/server-storage/rev/e46b6e8156f6 Building RPMs and deploying to -dev
validated on web01. Richard, I am creating a new bug with the configurations changes to puppetize
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified er last comment
Status: RESOLVED → VERIFIED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.