By configuration you can have different combinations.
Blackbox actions on blackbox invoker only, and regular actions on normal invoker types only (ie. today) Blackbox actions on blackbox invoker only, and regular actions on any invoker type Any actions on any invoker type On Wed, Nov 28, 2018 at 7:09 AM Rodric Rabbah <rod...@gmail.com> wrote: > 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. > > -r > > > On Nov 28, 2018, at 5:56 AM, Christian Bickel <cbic...@apache.org> > wrote: > > > > Hi, > > > > in the past we divided the invokers into blackbox and whitebox invokers. > > This has the effect that one of these two types could be overloaded while > > the other type still has free capacity. > > > > Does anyone see issues on using every invoker for everything? > > Or does anyone see any action items that need to be addressed before we > > invoke every action-type on every invoker? > > > > If not I'll open a PR to not differentiate between these types anymore. > > > > Greetings > > Christian Bickel > -- Carlos Santana <csantan...@gmail.com>
