[Buildbot-commits] [Buildbot] #962: handle the case of duplicate slaves better
Buildbot
buildbot-devel at lists.sourceforge.net
Sun Aug 15 21:52:22 UTC 2010
#962: handle the case of duplicate slaves better
------------------------+---------------------------------------------------
Reporter: dustin | Owner: dustin
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.2
Version: 0.8.1 | Keywords:
------------------------+---------------------------------------------------
For various reasons, we at Zmanda often see two slaves running on the same
machine. Needless to say, these slaves continually boot one another off
the master, wasting lots of resources.
The current buildmaster code
({{{master.buidlbot.buildslave.AbstractBuildSlave.attached}}}) doesn't
handle this very well.
I think that the best approach is to ping the old slave and reject the new
slave. If the old slave really is gone, then the ping should time out,
and the new slave will eventually reconnect without any conflict. If the
old slave isn't gone, then the new slave will just bang away endlessly at
the master until someone reads the logs and notices -- which is better
than interrupting builds!
--
Ticket URL: <http://buildbot.net/trac/ticket/962>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list