[
https://issues.apache.org/jira/browse/AURORA-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Burg updated AURORA-582:
------------------------------
Affects Version/s: 1.0.0
> Slave attributes cached incorrectly by scheduler
> ------------------------------------------------
>
> Key: AURORA-582
> URL: https://issues.apache.org/jira/browse/AURORA-582
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 1.0.0
> Reporter: Kevin Burg
> Priority: Critical
>
> I would like to be able to update the attributes being offered by a 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
