#2652: [nine] Coordinate Messages and Data
-------------------+-------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: | Keywords:
-------------------+-------------------
We currently have a DB API which may use a backend DB without read-after-
write consistency, due to replication delay.
And we have an MQ API which introduces an unbounded propagation delay in
messages.
So it's possible to receive a message about a change, say a build
finishing, after which a DB query still shows the build as unfinished.
Likewise, it's possible to see an updated value from a DB query long
before the corresponding message arrives.
This causes problems.
For example, a user might want an event for every build triggered for a
particular buildset.
The naive approach is to get the list of current builds for that buildset,
and subscribe to builds with that buildset in the future.
Given the timing discrepancies, though, this approach may either miss
builds for which a message has already been sent but which is not in the
DB yet; or double-report a build which is already in the DB but for which
the message has not yet been delivered.
I don't have any good solutions to this.
--
Ticket URL: <http://trac.buildbot.net/ticket/2652>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
