[
https://issues.apache.org/jira/browse/SLIDER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-600.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: Slider 2.0.0)
Slider 0.80
Assignee: Steve Loughran
> RoleHistory to support reloads with different # of roles from current set
> -------------------------------------------------------------------------
>
> Key: SLIDER-600
> URL: https://issues.apache.org/jira/browse/SLIDER-600
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: Slider 0.80
>
> Time Spent: 6h
> Remaining Estimate: 0h
>
> The role history won't reload historical placement data if the no. of roles
> doesn't match what it saved. It only persists numeric values and can't
> rebuild the information.
> This means if you add a new role to a cluster: no recovery of any previous
> placement
> It could persist the names -> priorities of each role, and reload the
> positions of those roles about which there are currently records, ignoring
> the rest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
