[AURORA-582] Slave attributes cached incorrectly by scheduler

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.5.0
• Component/s: Scheduler
• Assignee: Bill Farner
• Reporter: Kevin Burg
• Created: 14/Jul/14 20:33
• Updated: 24/Jul/14 02:36
• Resolved: 17/Jul/14 21:15

Description

I would like to be able to update the attributes being offered by a mesos slave after the cluster has been setup. The cluster was initialized with two slaves reporting two attributes - 'host' and 'rack'. I was able to assign task with constraints involving these two attributes and everything works. Any third attribute I add shows up in the '/offers' endpoint of the aurora process, but not in the '/slaves' endpoint. Modifications to existing attributes are similarly not reflected. I am not able to schedule tasks involving a constraint on the third attribute or on any modified attributes. The schedule requests just end in vetoes from both slaves unable to resolve the constraints.

It's been suggested that I delete the slave's 'meta' directory before bouncing the slave, but this has not helped to solve the issue. The only way I have been able to modify the attributes so that aurora can see them is by deleting the entire AURORA_ROOT and rebuilding the cluster.

Issue Links

• relates to: AURORA-328 Scheduler should key slaves off slaveID, not hostname