Closed
Bug 981986
Opened 10 years ago
Closed 10 years ago
invalid entries for attach_id in the flags table, due to maxing out the mediumint value
Categories
(Data & BI Services Team :: DB: MySQL, task)
Data & BI Services Team
DB: MySQL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: glob, Assigned: scabral)
References
Details
something very weird is happening with the attachments and flags on bug 969117. querying the slaves i get two different attach_ids for njn's review: > select attach_id,status from flags where id=826519; > 8388607 ? > select attach_id,status from flags where id=826519; > 8388676 ? first, attachment 8388607 [details] is unrelated to this bug, which worries me. second, njn set this flag to + on [2014-03-10 15:17:49 PDT] however i don't see this change when querying the flags (as per above, they are still returning ?).
> select count(*) from flags where attach_id=8388607; > 0 > select count(*) from flags where attach_id=8388607; > 13 that attachment is from bug 860711. show_bug is displaying all those flags against that attachment, which indicates to me that there's incorrect rows in the master (that attachment shouldn't have any flags set).
nagios is currently reporting zero lag for all slaves (except bugzilla4, which is currently offline), so those different results for the queries is where i'm mostly concerned. as 8388607 is the max value of mediumint, that's probably why it's being reused, and we'll probably have to manually tidy up those rows. i'll work through the list and try to determine the correct attach_id's.
as far as i can tell: flags.id correct attach_id 826516 8388607 826521 8388680 826511 8388663 826517 8388671 826514 8388667 826519 8388676 826512 8388665 826505 8388649 826508 8388660 826520 8388677 826506 8388650 826518 8388675 826522 8388681
Comment 4•10 years ago
|
||
I'll dig into these further and fix.
Assignee | ||
Comment 5•10 years ago
|
||
The flags table has 18 differences among the slaves. Fixing those now, setting the attach_id to the value that isn't 8388607, when there's a difference among the slaves. Changed: mysql> select flags.id,bug_id,attach_id from flags where id in (826505,826508,826506,826511,826512,826514,826516,826517,826518,826519,826520,826521,826522); +--------+--------+-----------+ | id | bug_id | attach_id | +--------+--------+-----------+ | 826505 | 979489 | 8388649 | | 826506 | 981481 | 8388650 | | 826508 | 979489 | 8388660 | | 826511 | 935219 | 8388663 | | 826512 | 976082 | 8388665 | | 826514 | 960517 | 8388667 | | 826516 | 739959 | 8388670 | | 826517 | 959430 | 8388671 | | 826518 | 981636 | 8388675 | | 826519 | 969117 | 8388676 | | 826520 | 980456 | 8388677 | | 826521 | 739959 | 8388680 | | 826522 | 981728 | 8388681 | +--------+--------+-----------+ 13 rows in set (0.00 sec)
Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-database → scabral
Summary: possible replication issue with the bmo database → invalid entries for attach_id in the flags table, due to maxing out the mediumint value
Assignee | ||
Comment 6•10 years ago
|
||
Entries stable, resolving.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•