[
https://issues.apache.org/jira/browse/SLIDER-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248216#comment-14248216
]
Steve Loughran commented on SLIDER-726:
---------------------------------------
bq. There would be a conflit with the YARN configuration that YARN won't return
the container on the same node
We remember where nodes where and ask for it back on the same location (though
if that request fails, put that location at the end of list of nodes to ask for)
Normally this is a best-effort request; you can set "yarn.placement.policy" to
request "strict" placement, in which the AM says the component *must* be on a
specific host. If this cannot be satisfied (As when the host is down), the
request remains outstanding. This is for use by applications like Kafka where
it is better to have an unsatisifed request than restart elsewhere.
see {{org.apache.slider.providers.PlacementPolicy}}
> To run on different nodes
> -------------------------
>
> 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)
