tysonnorris commented on issue #2833: MesosContainerFactory URL: https://github.com/apache/incubator-openwhisk/pull/2833#issuecomment-369376482 Thanks @glikson - 1. Marathon has a different notion of lifecycle for containers than openwhisk, so I don't think that using it is a good option; although it was discussed amongst my colleagues at Adobe. Generally marathon adds a layer of container durability, so that if a container stops it will be restarted indefinitely, but this is not really something openwhisk action containers do at all - they are started, and then explicitly stopped. 2. I think it depends on what you mean exactly by "pooling resource offers" - do you mean "holding resource offers"? FWIW, we haven't thoroughly tested the mesos-actor library in a multi-framework deployment, but our deployment is multi-framework (marathon, kafka, and openwhisk), so we need the frameworks to be good citizens that don't agressively hold resources without using them. So that is where we start. It may be good to make this tunable for different envs, where if someone does NOT have other frameworks in play, they could turn up the retention of offers, or use dynamic reservations at startup to preemptively reserve resources - but using the prewarm containers in openwhisk will already accomplish this indirectly, so it hasn't been a priority to expose it at the framework level.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
