ningyougang commented on a change in pull request #5102:
URL: https://github.com/apache/openwhisk/pull/5102#discussion_r627863269
##########
File path: core/invoker/src/main/resources/application.conf
##########
@@ -60,9 +60,13 @@ whisk {
user-memory: 1024 m
concurrent-peek-factor: 0.5 #factor used to limit message peeking: 0 <
factor <= 1.0 - larger number improves concurrent processing, but increases
risk of message loss during invoker crash
akka-client: false # if true, use PoolingContainerClient for HTTP from
invoker to action container (otherwise use ApacheBlockingContainerClient)
- prewarm-expiration-check-interval: 1 minute # period to check for prewarm
expiration
+ prewarm-expiration-check-init-delay: 10 minute # the init delay time for
the first check
+ prewarm-expiration-check-interval: 10 minute # period to check for prewarm
expiration
prewarm-expiration-check-interval-variance: 10 seconds # varies expiration
across invokers to avoid many concurrent expirations
prewarm-expiration-limit: 100 # number of prewarms to expire in one
expiration cycle (remaining expired will be considered for expiration in next
cycle)
+ prewarm-max-retry-limit: 5 # max retry limit for create prewarm
+ prewarm-promotion: false # if true, action can take prewarm container
which has bigger memory
Review comment:
Yes, but for `prewarm-promotion`, is used in
FunctionPullingContainerPool only, and the configuration is `false` which mean,
didn't take prewarm container which has bigger memory
--
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:
us...@infra.apache.org
