Bug 1028795 - There should be no downtime for a scaled app
There should be no downtime for a scaled app
Product: OpenShift Online
Classification: Red Hat
Component: Containers (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Jhon Honce
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-11-10 14:57 EST by Oleg Fayans
Modified: 2016-11-30 19:27 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-10 22:12:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Oleg Fayans 2013-11-10 14:57:17 EST
Description of problem:

When I restart or git push the scaled app during the load, there are several seconds when the app is unavalable. In fact, it happens even without any load

Version-Release number of selected component (if applicable):
reproduced on devenv-stage_562

How reproducible:

Steps to Reproduce:
1. rhc app create myphp php-5.3 -s
2. scale up the app. Make sure the app has 2 gears
3. create some local content, git commit and push
4. During git push constantly check the app's url for availability

Actual results:

there are several moments when I get 503 - service unavailable

Expected results:
the app url should be available always

Additional info:
tcms testcase: 
Comment 1 Meng Bo 2013-11-10 22:12:59 EST

If we want to restart the app without down time, we should have at least two haproxies.

The case is out of date.

In your step, the app should have a small downtime to restart the haproxy cartridge. But you can see the web gears are rolling restart.

Note You need to log in before you can comment on or make changes to this bug.