Bug 1028795 - There should be no downtime for a scaled app
Summary: There should be no downtime for a scaled app
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-10 19:57 UTC by Oleg Fayans
Modified: 2016-12-01 00:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 03:12:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Oleg Fayans 2013-11-10 19:57:17 UTC
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:
always

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: 
https://tcms.engineering.redhat.com/case/318063/?from_plan=4962

Comment 1 Meng Bo 2013-11-11 03:12:59 UTC
@ofayans

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.