sven-lange-last opened a new pull request #4537: Add action timeout limit to invoker assignment message in load balancer URL: https://github.com/apache/incubator-openwhisk/pull/4537 * Add information whether the action memory / time limits are standard, i.e. default, or not. * Restructure message and shorten it to make log volume smaller despite adding information. * The code uses the term "scheduling an activation to an invoker". Change message to use this term. * Also add more information to message that indicates that an activation could not be scheduled to an invoker because no usable invokers are available. The additional information helps to identify which particular activation was affected. ## Description * The proposed message changes are meant to help operators with understanding the effects of overloading an invoker with more activations than it can process in parallel from a user memory perspective. This can happen in an overload situation - i.e. no invoker has enough free memory available - or when activations time out with a forced acknowledgement. * If operators want to debug overloaded invokers, the time limit information gives an upper bound for how long an activation may occupy the invoker. * If actions use standard (default) memory and time limits, it's probably hard to draw conclusions regarding actual invoker load. Whenever non-standard limits are set, conclusions regarding actual invoker load are more meaningful. That's why this proposal adds information whether limits are set to standard values or not. ## My changes affect the following components <!--- Select below all system components are affected by your change. --> <!--- Enter an `x` in all applicable boxes. --> - [ ] API - [ ] Controller - [ ] Message Bus (e.g., Kafka) - [x] Loadbalancer: only message enhancements - [ ] Invoker - [ ] Intrinsic actions (e.g., sequences, conductors) - [ ] Data stores (e.g., CouchDB) - [ ] Tests - [ ] Deployment - [ ] CLI - [ ] General tooling - [ ] Documentation ## Types of changes <!--- What types of changes does your code introduce? Use `x` in all the boxes that apply: --> - [ ] Bug fix (generally a non-breaking change which closes an issue). - [x] Enhancement or new feature (adds new functionality): only message enhancements - [ ] Breaking change (a bug fix or enhancement which changes existing behavior). ## Checklist: <!--- Please review the points below which help you make sure you've covered all aspects of the change you're making. --> - [x] I signed an [Apache CLA](https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md). - [x] I reviewed the [style guides](https://github.com/apache/incubator-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] With regards, Apache Git Services
