Closed
Bug 275280
Opened 20 years ago
Closed 20 years ago
Saved Searches not refreshing
Categories
(mozilla.org Graveyard :: Server Operations, task, P1)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Bugzilla-alanjstrBugs, Assigned: justdave)
Details
Attachments
(1 file)
|
35.96 KB,
image/gif
|
Details |
I have a search to return all bugs in the Update Listings category that are open. I resolved bug 274863. Any time I re-execute that saved search, the bug is still listed as being New. So either the report isn't being re-executed, or the query only db isn't getting updated.
| Assignee | ||
Comment 2•20 years ago
|
||
This would be the shadow database not replicating, and has nothing to do with the recent upgrade, and is also mozilla.org-specific. The replication process died yesterday because mecha ran out of disk space (ironically because I was trying to compress a backup in order to create more space, and the size of the compressed copy of said backup filled up the remaining disk space before the original could be deleted). Replication did get restarted, but it's quite possible that it lost changes that happened while it was crashed (since there was no space to add them to the replication log). If this turns out to be the case, we'll have to re-sync the databases, which will involve taking Bugzilla offline for about 10 minutes in order to make a backup of the production database to re-seed the slave with.
Assignee: gerv → justdave
No longer blocks: bmo-regressions-0412
Component: Reporting/Charting → Server Operations
OS: Windows 2000 → All
Product: Bugzilla → mozilla.org
QA Contact: mattyt-bugzilla → myk
Hardware: PC → All
Version: 2.19.1 → other
Comment 3•20 years ago
|
||
I've experienced rather long (2-5 minute) delays between when a bug was resolved and when the query showed the change. Same issue?
| Assignee | ||
Comment 4•20 years ago
|
||
(In reply to comment #3) > I've experienced rather long (2-5 minute) delays between when a bug was resolved > and when the query showed the change. Same issue? No, different issue. Looking at that bug, the status change timestamp does appear to line up with when that replication failure happened, and that bug is indeed out of sync in the shadow database. :( Looks like time to re-sync the databases. :(
Severity: normal → critical
Priority: -- → P1
| Assignee | ||
Comment 5•20 years ago
|
||
Done.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•