You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/11/16 15:46:09 UTC

[GitHub] [openwhisk] tysonnorris commented on issue #4727: Config option to return 502 on blocking activation timeout

tysonnorris commented on issue #4727: Config option to return 502 on blocking activation timeout
URL: https://github.com/apache/openwhisk/issues/4727#issuecomment-554648591
 
 
   RE: waitTimeout - is there a case in blocking activations where someone would care whether wait/init/duration timeout was hit, vs the single overall response timeout? This may be more interesting for non-blocking?
   
   RE: sequences/compositions - I would expect at least the top activation to get a failure when timeout for blocking - you can end up with partially executed. I'm not sure how much timing info is currently available on the sub-activations at the invoker, to determine whether the top most has timed out, but we could add it, in which case the sub activation would get dropped at invoker. This may be a more useful case of storing failure activation before executing the action, so that a sequence can be tracked to a particular piece that took longer than expected.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services