Closed
Bug 410098
Opened 18 years ago
Closed 17 years ago
Replication failed because the sessions table ran out of space
Categories
(support.mozilla.org :: General, defect)
support.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 415306
People
(Reporter: justdave, Unassigned)
Details
We just got paged because replication failed on mrdb81 (the slave database for sumo).
The error message reported was:
Error 'The table 'sessions' is full' on query. Default database: 'support_mozilla_org'.
We ran into this on Bugzilla a long time ago, and the fix was to alter the table definition to set the maximum table size larger. We fixed this by running the following on both the master and the slave (had to do the slave first because replication wouldn't restart without it)
ALTER TABLE sessions AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;
based on documentation at
http://www.bugzilla.org/docs/tip/html/configuration.html#AEN502
This sets the maximum size of the table to 20 GB instead of the default 4 GB.
I see other tables in the database that are already set to 40 GB and 60 GB and so forth, so this must be an issue you've already been prepared to deal with and just weren't expecting it on this table. So we figured we should let you know in case any setup scripts need to be fixed for a reminder of how it was set up, or if you have a different size you'd rather it be set to.
Comment 1•17 years ago
|
||
I'm fairly convinced this will be solved by
https://bugzilla.mozilla.org/show_bug.cgi?id=415306
Duping.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•