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 2018/11/02 14:06:31 UTC

[GitHub] mrutkows commented on issue #4082: Rename prewarmed containers

mrutkows commented on issue #4082: Rename prewarmed containers
URL: https://github.com/apache/incubator-openwhisk/pull/4082#issuecomment-435390886
 
 
   @dgrove-oss Even understanding the use case, it seems wrong to track state via name (especially given the concurrency/locking concerns Rodric raised despite appearing to be asynchronous). My main concern is that there is nothing actionable an operator can do from seeing a collection of named containers which may indicate some resource consumption state.  At best, this approach seems to be an attempt at a stop-gap measure for "container watchers", but would require deeper analysis via log/monitoring tools to be actionable. Is it worth going down this road and raising the expectations of operators that name will reflect the actual state with fidelity?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services