We currently have 1 topic (in addition to the usual discussion of recently
merged and pending PRs).
One of the authors of the MICRO 2019 paper “Architectural Implications of FaaS
Computing” [1], which used OpenWhisk, will be presenting their research results.
--dave
[1]
By "critical path" you mean the path during action invocation?
The current PR only introduces latency on that path for the case of a Paused
container changing to Running state (once per transition from Paused ->
Running).
In case it isn't clear, this change does not affect any retry (or lack
as a longer term point to consider, i think the current model of "best
effort at most once" was the wrong design point - if we embraced failure
and just retried (at least once), then failure at this level would lead to
retries which is reasonable.
if we added a third health route or introduced a
Tyson Norris wrote on 10/28/2019 11:17:50 AM:
> I'm curious to know what other
> folks think about "generic active probing from invoker" vs "docker/
> mesos/k8s specific integrations for reacting to container failures"?
>
>From a pure maintenance and testing perspective I think a single common
2019-10-28 03:16:53 UTC - Abbie Dowd: Hello, I'm new to openwhisk and am trying
to deploy using ansible. I am able to get all to way to deploying controller 0
and then it fails saying the connection is refused (see below). What's strange
is that the container is running and I can attach to it.
