You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "kyungwan nam (JIRA)" <ji...@apache.org> on 2017/05/10 07:17:04 UTC
[jira] [Updated] (SLIDER-1225) the Anti-Affinity placement policy
should respect the role-history
[ https://issues.apache.org/jira/browse/SLIDER-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kyungwan nam updated SLIDER-1225:
---------------------------------
Description:
the Anti-Affinity placement policy guarantee that there are no multiple instances on the same node.
but, the role history is ignored.
It makes tricky for upgrading the slider app, which need data-local allocation.
for example, the kafka on slider store data to local disk.
when upgrading the kafka on slider, it need to allocate the host of which was released recently.
otherwise, unnecessary network traffic will be triggered for recovery.
the behavior of the Anti-Affinity could be improved as follows.
* If there are the role history for a component, allocate to the host of which was released recently.
** escalation: if the host is not available for the escalation time, allocate to the hosts of which the component has not been allocated yet.
* If there are no role history for a component, allocate to the hosts of which the component has not been allocated yet. ( no escalation )
was:
the Anti-Affinity placement policy guarantee that there are no multiple instances on the same node.
but, the role history is ignored.
It makes tricky for upgrading the slider app, which need data-local allocation.
for example, the kafka on slider store data to local disk.
when upgrading the kafka on slider, it need to allocate the hosts of which was released recently.
otherwise, unnecessary network traffic will be triggered for recovery.
the behavior of the Anti-Affinity could be improved as follows.
* If there are the role history for a component, allocate to the host of which was released recently.
** escalation: if the host is not available for the escalation time, allocate to the hosts of which the component has not been allocated yet.
* If there are no role history for a component, allocate to the hosts of which the component has not been allocated yet. ( no escalation )
> the Anti-Affinity placement policy should respect the role-history
> ------------------------------------------------------------------
>
> Key: SLIDER-1225
> URL: https://issues.apache.org/jira/browse/SLIDER-1225
> Project: Slider
> Issue Type: Improvement
> Affects Versions: Slider 0.92
> Reporter: kyungwan nam
>
> the Anti-Affinity placement policy guarantee that there are no multiple instances on the same node.
> but, the role history is ignored.
> It makes tricky for upgrading the slider app, which need data-local allocation.
> for example, the kafka on slider store data to local disk.
> when upgrading the kafka on slider, it need to allocate the host of which was released recently.
> otherwise, unnecessary network traffic will be triggered for recovery.
> the behavior of the Anti-Affinity could be improved as follows.
> * If there are the role history for a component, allocate to the host of which was released recently.
> ** escalation: if the host is not available for the escalation time, allocate to the hosts of which the component has not been allocated yet.
> * If there are no role history for a component, allocate to the hosts of which the component has not been allocated yet. ( no escalation )
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)