> On 21 May 2015, at 02:25, Rajesh Kartha wrote:
>
> Thanks a lot Steve,
>
> So the suggestion is to use the AMRMClient.updateBlacklist() method to
> include *nodes where the component is running + unreliable nodes* before
> the container is requested instead of discarding allocated containers
Thanks a lot Steve,
So the suggestion is to use the AMRMClient.updateBlacklist() method to
include *nodes where the component is running + unreliable nodes* before
the container is requested instead of discarding allocated containers.
I will take a closer look and update SLIDER-82 with my approa
> On 18 May 2015, at 23:41, Rajesh Kartha wrote:
>
> Hello,
>
> One of the early requests we got for improving Slider was to have a
> way of *ensuring
> only a single process* of the given application runs on any given node. I
> have read about the ANTI-AFFINITY flag but was not fully sure abou
Hello,
One of the early requests we got for improving Slider was to have a
way of *ensuring
only a single process* of the given application runs on any given node. I
have read about the ANTI-AFFINITY flag but was not fully sure about its
implementation.
Hence have been trying to piece things tog
