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 2021/07/25 16:36:15 UTC

[GitHub] [openwhisk] chiru091096 opened a new issue #5143: Controlling termination time for warm containers.

chiru091096 opened a new issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143


   I'm using standalone openwhisk with functions running inside container. I created actions in python referring https://github.com/apache/openwhisk/blob/master/docs/actions-python.md
   When the action is invoked first time, the container starts in cold mode and then continues to run for some time (around 10 mins) without exiting. If any request comes within this time then request is served by the warm container.
   How can I make the container exit immediately after it serves each request i.e how can I make this container always start in cold mode for each and every request.
   Additionally I tried using ttl field in runtimes.json file for python to control when the warm container terminates but it doesnt seem to work. ttl of 5 mins and 2 mins are not making any difference on when the warm container terminates. 
   
   ## Environment details:
   
   * local deployment
   * ubuntu 18.04
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 edited a comment on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 edited a comment on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-888260447


   > This would likely need to be a new feature - “run and done” actions. Would not be hard to implement.
   > You can also try changing the idle container timeout - I don't know off hand if `0 minutes` will work but you can try and let us know.
   > 
   > ```
   >   container-proxy {
   >     timeouts {
   >       # The "unusedTimeout" in the ContainerProxy,
   >       #aka 'How long should a container sit idle until we kill it?'
   >       idle-container = 10 minutes
   >       pause-grace = 150 milliseconds
   >     }
   >   }
   > ```
   
   tried changing idle container timeout to 1 minutes and it works. But changing it to 0 minutes didn't work and was reset to 1 minutes. 
   I tried with 10 seconds, even that gets reset to 1 minutes.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] rabbah commented on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-893483596


   Are you interested in implementing a run-and-done feature? I think it's compelling and would be happy to help you if you need help pursuing the feature.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 removed a comment on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 removed a comment on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-888260194


   tried changing idle container timeout to 1 minutes and it works. But changing it to 0 minutes didn't work and was reset to 1 minutes. 
   I tried with 10 seconds, even that gets reset to 1 minutes.
   Is there any way to further decrease idle-container timeout ?


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 commented on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 commented on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-894207994


   I'd love to implement it.  Thanks


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] rabbah commented on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-887644467


   This would likely need to be a new feature - “run and done” actions. Would not be hard to implement.
   You can also try changing the idle container timeout - I don't know off hand if `0 minutes` will work but you can try and let us know.
   ```
     container-proxy {
       timeouts {
         # The "unusedTimeout" in the ContainerProxy,
         #aka 'How long should a container sit idle until we kill it?'
         idle-container = 10 minutes
         pause-grace = 150 milliseconds
       }
     }
   ```


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 commented on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 commented on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-888103823


   sure, will try that. Thanks


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 edited a comment on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 edited a comment on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-888103823


   sure, will try that and let you know. Thanks


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] chiru091096 commented on issue #5143: Controlling termination time for warm containers.

Posted by GitBox <gi...@apache.org>.
chiru091096 commented on issue #5143:
URL: https://github.com/apache/openwhisk/issues/5143#issuecomment-888260194






-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org