2019-12-12 13:03:43 UTC - Alvaro Lopez: Hello, we are trying to leverage Mesos for the OpenWhisk Invoker, i.e. to launch tasks on a Mesos Cluster, but there are some things that are not working as expected (or at least are not clear to us) https://openwhisk-team.slack.com/archives/C6C7NRQKE/p1576155823001900 ---- 2019-12-12 13:04:19 UTC - Alvaro Lopez: When the invoker is spawned it registers the framework, but then it only uses the resources from one agent, it seems as the other offers are being simply dropped https://openwhisk-team.slack.com/archives/C6C7NRQKE/p1576155859003000 ---- 2019-12-12 13:04:42 UTC - Alvaro Lopez: I was expecting to have 1 invoker able to use all the resources offered through Mesos, am I right? https://openwhisk-team.slack.com/archives/C6C7NRQKE/p1576155882003600 ---- 2019-12-12 16:46:37 UTC - Tyson Norris: By “it only uses the resources from one agent” you mean “one invoker”? This is the default config in OpenWhisk, to allow invokers to run docker containers directly instead of via mesos, but as you can see this doesn’t allow you to consume more resources in the cluster. https://openwhisk-team.slack.com/archives/C6C7NRQKE/p1576169197005700 ---- 2019-12-12 16:47:46 UTC - Tyson Norris: What we do, is set the the `whisk.container-pool.user-memory` config artificially large, so that a single invoker can “see” the entire capacity of the cluster https://openwhisk-team.slack.com/archives/C6C7NRQKE/p1576169266006500 ----
