bdoyle0182 opened a new pull request #5058: URL: https://github.com/apache/openwhisk/pull/5058
## Description The invoker will now drop healthcheck activations read from kafka that are older than a configurable threshold. The default is 30 minutes. The max backlog of healthcheck activations backlogged in the invoker topics that will be processed are therefore # controllers * number of minutes threshold since each controller sends a healthcheck once per minute when unhealthy. The invoker also will no longer become healthy prior to eating through these old messages and processing a young enough healthcheck message at which point should be the end of the kafka backlog and safe to mark the invoker as healthy. ## Related issue and scope - [x] I opened an issue to propose and discuss this change (#5053 ) ## My changes affect the following components - [ ] API - [ ] Controller - [ ] Message Bus (e.g., Kafka) - [ ] Loadbalancer - [x] Invoker - [ ] Intrinsic actions (e.g., sequences, conductors) - [ ] Data stores (e.g., CouchDB) - [ ] Tests - [ ] Deployment - [ ] CLI - [ ] General tooling - [ ] Documentation ## Types of changes - [x] Bug fix (generally a non-breaking change which closes an issue). - [ ] Enhancement or new feature (adds new functionality). - [ ] Breaking change (a bug fix or enhancement which changes existing behavior). ## Checklist: - [x] I signed an [Apache CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md). - [x] I reviewed the [style guides](https://github.com/apache/openwhisk/wiki/Contributing:-Git-guidelines#code-readiness) and followed the recommendations (Travis CI will check :). - [ ] I added tests to cover my changes. - [ ] My changes require further changes to the documentation. - [ ] I updated the documentation where necessary. ---------------------------------------------------------------- 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: [email protected]
