Re: Backpressure for slow activation storage in Invoker

I think this sounds good, but want to be clear I understand the consumers and producers involved - is this summary correct? Controller: * consumes "completed-" topic (as usual) Invoker: * in case of logs NOT in db: when queue full, publish non-blocking to "completed-non-blocking" *in case of

PRs ready to merge

There are at least 4 PRs ready to merge and now have the ready label. https://github.com/apache/openwhisk/pulls?q=is%3Aopen+is%3Apr+label%3Aready I know Chetan was generating github digest messages briefly (that was really useful I thought, thanks for the initiative!) and I'd be happy to add a

optionally skip kafka/zookeeper pulls

This PR from Bill Zong removes the explicit zookeeper pull task and uses the 'pull' attribute on 'docker_container' instead. See https://github.com/apache/openwhisk/pull/4619. I will merge this by the end of the week unless there's an objection. -r

[slack-digest] [2019-09-11] #general

2019-09-11 06:13:43 UTC - Sven Lange-Last: @Misha Iesiev using the openwhisk kube container factory to use kube itself to manage action containers is no option for you? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1568182423126500?thread_ts=1566336101.068200=C3TPCAQG1