You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/03/30 12:13:53 UTC

[jira] [Commented] (SLIDER-726) Different instances of the same component should run on different nodes (anti-affinity)

    [ https://issues.apache.org/jira/browse/SLIDER-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386502#comment-14386502 ] 

Steve Loughran commented on SLIDER-726:
---------------------------------------

SLIDER-799 has done a lot of work on re-requesting nodes after a failure; it can now configure a component type to wait minutes on each request for a new instance, before relaxing the placement policy from the previous node, and we do track failures better.

With that done, all that's in this JIRA is the SLIDER-84 anti-affinity need. I'm going to close this as a duplicate of that.

> Different instances of the same component should run on different nodes (anti-affinity)
> ---------------------------------------------------------------------------------------
>
>                 Key: SLIDER-726
>                 URL: https://issues.apache.org/jira/browse/SLIDER-726
>             Project: Slider
>          Issue Type: New Feature
>          Components: appmaster, client
>    Affects Versions: Slider 0.60
>            Reporter: Yang Hao
>
> To let component run on different will be very useful, for these reasons
> 1. many distributed services want to or should be run on different nodes
> 2. slider try to let yarn be a common resource OS
> If this feature is add, slider will be more popular



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)