Rodric Rabbah <rod...@gmail.com> wrote on 11/28/2018 07:09:12 AM: > > I think it would be a mistake to blindly merge two container pools - > docker actions as run today are pulled as needed and can take a long > time, they’re subject to different kinds of attacks, and can affect > performance of other tenants (higher noisy neighbors). > > If you want to allow more overlap, it should be at least done as a > configuration parameter which allows different pools to continue to > exist (note that for small N as in local dev they’re allowed to > overlap today). Or, used for overflow only as a way of providing > more elasticity. >
Note that if we are using the KubernetesContainerFactory (or I believe the MesosContainerFactory) the separation at the invoker level is not really necessarily effective at avoiding noisy neighbors since there is no longer a 1:1 match from invoker to docker daemons. --dave
