982422 - Opening my dashboard fails with "Failed to load bug list from Bugzilla: 8514859 is not a valid comment id."

Status: RESOLVED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[Tim Taubert [:ttaubert] (inactive)]

When trying to load the "my dashboard" page I see an alert that says:

"Failed to load bug list from Bugzilla: 8514859 is not a valid comment id."

This used to work yesterday I think. Could this somehow be related to the recent maintenance work / schema changes?

Comment 1

[:glob ✱]

this looks like a database replication issue.

when querying the slaves:

> select comment_id,bug_when from longdescs where comment_id=8514859;
> 0 results
> select comment_id,bug_when from longdescs where comment_id=8514859;
> 8514859,2014-03-10 13:43:28

given the age of that comment i suspect we're not seeing database replication lag (bug 974338).

> select count(*) from longdescs;
> 8510945
> select count(*) from longdescs;
> 8515318

Comment 2

[:glob ✱]

given the size of the discrepancy between bugzilla2 and the other slaves, and that this is a end-user affecting issue, i'm bumping the priority.

Comment 3

[Sheeri Cabral [:sheeri]]

Checked the slaves, and indeed of the slaves in the load balancer pool, bugzilla2 is the only one with an issue. Taking it out of the pool and re-syncing.

Comment 4

[Sheeri Cabral [:sheeri]]

We are working on syncing the data. Attachments and cc's may not be showing up correctly until this work is completeed.

Comment 5

[Sheeri Cabral [:sheeri]]

attachments are sync'd up, working on cc's, and then doing a full check of everything to double-check that all is good.

Comment 6

[Sheeri Cabral [:sheeri]]

Brandon Johnson went over this with a fine toothed comb and found no further data discrepancies. Thanks Brandon! Data should be working normally, if there are any new issues, please report by making a bug in the mozilla.org Product, Component Server Operations:Database, and set the importance to "critical". This will page the oncall DBA.

In the case Bugzilla isn't happy, let the DB team know in #db, or have the MOC page the oncall DBA if nobody's there to help.