Bug 1013512
Summary: | [deploy][origin_runtime_210]It will take too long to restart scalable app with multi gears when there are some traffics passed in | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Meng Bo <bmeng> |
Component: | Containers | Assignee: | Andy Goldstein <agoldste> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | bmeng, nmone, xtian |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-17 13:33:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Meng Bo
2013-09-30 09:07:38 UTC
I just tested on what will soon be fork_ami_deploy_888 (I tested on 887 after fixing the errors that made 887 fail) and see much better results. My app was using the php-5.3 cartridge, fyi: time rhc app restart ps ps restarted real 0m42.282s user 0m1.162s sys 0m0.333s Please retest when >= 888 is available and let me know the results. Thanks! Also, please note that 'rhc app restart' will restart the entire application, including the haproxy cartridge, so there will be some # of tests in the 'ab' run that fail while the haproxy cartridge is restarting. If you want to do a rolling restart of just the web cartridge, you can do 'rhc cartridge restart -a <app> <cartridge>' (support for restarting all gears for a specific cartridge is still in development and will be ready soon - I'll update this when it's ready). I have retested on fork_ami_889, it will still cost to much time to restart the app during the ab is running. # time rhc app restart php1s RESULT: php1s restarted real 2m50.007s user 0m1.150s sys 0m0.707s And this condition only happens when the ab is running, if restart the app without benchmark the app, it will restart very fast. # time rhc app restart php1s RESULT: php1s restarted real 0m26.580s user 0m0.750s sys 0m0.400s Using devenv_3873, I am running the ab command you listed above, using a scalable php-5.3 application with 3 gears, and this is the result I get: [root@ip-10-166-61-99 ~]# time rhc cartridge restart -a p3 php-5.3 Restarting php-5.3 ... done real 0m22.864s user 0m0.850s sys 0m0.461s Note that 'rhc cartridge restart' now supports rolling restarts of the cartridge across all the application's gears. I'm running ab on the devenv itself - is that what you're doing? I'm unable to reproduce the slowdown you're seeing. Is your application anything more than the default template that comes with the PHP cartridge? Tested on devenv_3874, with php cartridge and 3 gears in the scalable app. The issue is gone. [root@ip-10-145-147-198 ~]# time rhc app restart php1s RESULT: php1s restarted real 0m53.123s user 0m0.741s sys 0m0.434s [root@ip-10-145-147-198 ~]# time rhc cartridge-restart php-5.3 -a php1s Restarting php-5.3 ... done real 0m53.056s user 0m0.948s sys 0m0.527s And I just found the fork_ami_889 is not a deploy ami... so maybe the last comment is useless. The current behaviour is acceptable, please help move the bug to ON_QA, and I will close it. Thanks. Checked on devenv_3880, issue cannot be reproduced. Move bug to verified. |