Several openwhisk users recently have hit a bug using serverless framework
(sls) and openwhisk to deploy a function/api. I've hit the same bug when
using the standalone controller + api gateway.
The symptom is failure to create an API and this error:
Failed to deploy API Gateway route due to
> Instead of resending the message to the pool immediately, it just waits
in the runbuffer, and the runbuffer is processed in reaction to any
potential change in resources: NeedWork, ContainerRemoved, etc. This may
add delay to any buffered message(s), but seems to avoid the catastrophic
crash in
Related to the "Rescheduling Run message", one problem we have encountered in
these cases is that the invoker becomes unstable due ( I think) to a tight
message loop, since the message that couldn't run is immediately resent to the
pool to be run, which fails again, etc. We saw CPU getting
2019-07-07 16:21:18 UTC - Pepi Paraskevoulakou: Good afternoon can anyone tell
me if I can deploy whisk with kubernetes and docker in a Linux vm without using
IBM cloud and get data from a source such as a database or twitter api and
write machine learning action in python ? I am starting
