[users at bb.net] 0.9.0rc1/2, multi-master, and schedulers.

[Pierre Tardy]

>
>
> I'm not a database guy, per se, but wouldn't any database you'd want to
> run multi-master on be able to notify the other masters? Postgres, for
> example, has NOTIFY and LISTEN. I'm not much of a SQLAlchemy guy, either,
> but a cursory search shows an Event API.
>

Indeed, modern databases have rudimentary realtime capability, but not at
the level of what mq can propose.
mq is not only used in nine to provide synchro between masters, but this is
also used to make real time UI possible.

That is some of the reason we designed nine with separate db and mq
components.


>
> If you don't configure a multimaster capable mq, then build will not start
> instantly on the second master. If will only start when other event happen
> on that second master (like a new worker (dis)connection or build finish)
>
>
> That may be acceptable. With the volume we have, things finish pretty
> often. And with some of these builds taking a long time, the wait may be
> insignificant to us.
>

Without a multimaster capable mq, you would also loose realtime feature of
the UI.
Depending on the master the users are connected to, they will only see some
builds updated, and the other master's builds will seem inactive unless you
reload the page like in eight.


Thanks for the update on the other topics,
Please keep us in touch if you have any update. This is good to have team
like you to test buildbot nine, and report problems, so that we have
oportunity to fix hard-to-reproduce bugs.

Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20160825/5a357aba/attachment.html>