633364 - slavealloc: scrape masters' /buildslaves page

Status: RESOLVED WONTFIX

(Release Engineering :: General, enhancement, P5)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

The allocator can have a much better idea of which slaves are up and which are down if it checks the /buidlslaves URI of each master.  The weakness with the current arrangement is that if slave X is assigned to master M, and subsequently reboots and fails, the allocator will never see a new allocation request from the slave, and thus will assume it is still connected to M - starving M of one slave in the balancing algorithm.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

This is not something I'm planning to work on soon

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

So I had to implement this in an ad-hoc fashion for the ix work (bug 668395), and discovered that our masters do not correctly represent a disconnected slave, which is the most important information we'd hope to glean here.

So, until the masters are upgraded and/or fixed, this is not really worth doing.

Comment 3

[Aki Sasaki (not active)]

Inaccurate information + added buildbot master load + no one planning on working on this sounds like a WONTFIX to me.