#2147: buildslave losing connection to buildmaster
----------------------------+--------------------
Reporter: mariamarcano | Owner:
Type: support-request | Status: new
Priority: major | Milestone: 0.8.3
Version: 0.8.3 | Resolution:
Keywords: |
----------------------------+--------------------
Changes (by dustin):
* type: defect => support-request
Comment:
I suspect that your master is very busy, and is not able to reply to the
slave's keepalives for > 600 seconds.
We've seen other similar problems, and it turns out that bailing out if
you don't hear back from a keepalive is actually a bad idea, so this has
been removed in newer versions. That said, if this only occurred with
additional slaves, you could probably fix it by:
* increasing the timeouts on the slave side
* not using the waterfall, which is ridiculously CPU and IO intensive
* looking at master performance in general
--
Ticket URL: <http://trac.buildbot.net/ticket/2147#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits