Launchpad itself

Feeds lag is way too long

Bug #356671 reported by Martin Erik Werner
8
Affects Status Importance Assigned to Milestone
EeeBotu
Invalid
Critical
Unassigned
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Atom feeds use the slave DB, which lags behind the main Launchpad database. When that lag becomes longer than ~1-2h the feeds are out of date and tools that use them break.

For example, Eeebotu uses /ubuntu/latest-bugs.atom to announce new bugs for triaging, and the expectation is that it closely follows the real-time Launchpad.

We should either make sure that the replicated database never incurs a lag of more than 1-2 hours, or switch the feeds to use the main database.

See original description
Revision history for this message
Michael Rooney (mrooney) wrote :

Yes quite true, let's see about this!

Changed in eeebotu:
status: New → Confirmed
Revision history for this message
Michael Rooney (mrooney) wrote :

Actually the problem is that launchpad's atom feed is not updating, I'll triage appropriately.

Changed in eeebotu:
importance: Undecided → Critical
status: Confirmed → Triaged
summary: - Bot is down
+ launchpad bug atom feed is not updating
description: updated
Revision history for this message
Tim Penhey (thumper) wrote : Re: launchpad bug atom feed is not updating

Moving to malone as it is a bug feed.

affects: launchpad → malone
Eleanor Berger (intellectronica)
summary: - launchpad bug atom feed is not updating
+ Feeds lag is way too long
description: updated
affects: malone → launchpad-foundations
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Fortunately, it's not an either-or solution. We can use the replicated DB by default and switch to the master when we detect the lag is greater than 2 hours.

Setting to Low as our lag is within that limit most of the time.

Changed in launchpad-foundations:
importance: Undecided → Low
status: New → Triaged
Diogo Matsubara (matsubara)
tags: added: feeds
Stuart Bishop (stub)
Changed in eeebotu:
status: Triaged → Fix Released
Revision history for this message
Michael Rooney (mrooney) wrote :

Actually I'll mark Invalid in EeeBotu as it wasn't an issue with EeeBotu. Did someone have to reset the feed manually to get it working again, once it lagged behind enough?

Changed in eeebotu:
status: Fix Released → Invalid
Revision history for this message
Stuart Bishop (stub) wrote : Re: [Bug 356671] Re: Feeds lag is way too long

On Wed, Apr 8, 2009 at 7:45 AM, Michael Rooney <email address hidden> wrote:
> Actually I'll mark Invalid in EeeBotu as it wasn't an issue with
> EeeBotu. Did someone have to reset the feed manually to get it working
> again, once it lagged behind enough?

Nothing about the feed needed to be reset. It started producing current results as soon as current data was in the database it was using.

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/

Revision history for this message
C de-Avillez (hggdh2) wrote :

so the problem is basically synchronisation between the DBs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.