Venky,
Please think about this in terms of resources ("capable of handling"). YARN
controls memory and CPU and you define how much memory and CPU your
operator needs. The scheduler uses that information to find a suitable node
and it is already clear how many containers of an operator fit on a node.
Maybe you are thinking of another resource that is not managed by YARN?
Thomas
On Wed, Aug 10, 2016 at 11:27 AM, Venkatesh Kottapalli <
venkat...@datatorrent.com> wrote:
> Hi team,
>
> On the anti-affinity rules while deploying containers, do we have a
> feature which can control the number of containers of the same operator
> that get deployed on the same node. If the environment is capable of
> handling, then this will be a good feature to have as it is possible that
> certain operators could be resource hungry and this would distribute the
> load uniformly on all the nodes.
>
> Please share your thoughts on this.
>
> -Venkatesh.
