keunseob commented on issue #2482: Add container pool health status in invoker URL: https://github.com/apache/incubator-openwhisk/pull/2482#issuecomment-315289900 @markusthoemmes current containerpool scheduling and sending health scheduling are separated. So i'm curious why you can guarantee that the invoker environment status can be checked. Of course i knows the controller unhealthy mark process, but it doesn't cover all unexpected error by docker environment on invoker vm(pod or pm) I tried to many heavy test on k8s environment. when i request heavy request similar to ddos as blocking request. It returns activationId only till several days pass. And never get real result with waiting logs above. It is bad invoker case. The heavy request test is necessary to confirm various unexpected result and check OW reliability So i think that the bad invoker should be founded and excluded honestly. It would be better policy in terms of users. Current mechanism doesn't concern about this, so OW operator is very hard to know the each invoker status at a glance. It would be minor factor of OW reliability. So this PR is to exclude bad invoker clearly and if it will be changed to fine, it will be included in invoker pool. ---------------------------------------------------------------- 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: [email protected]
With regards, Apache Git Services
