Bug 987447 - App can't auto scale down when the HAproxy processes running on the head gear are terminated
App can't auto scale down when the HAproxy processes running on the head gear...
Product: OpenShift Online
Classification: Red Hat
Component: Pod (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Rajat Chopra
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-07-23 07:58 EDT by Jianwei Hou
Modified: 2015-05-14 20:19 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-23 15:55:31 EDT
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 Jianwei Hou 2013-07-23 07:58:00 EDT
Description of problem:
Given a scalable application is scaled up to 2 gears, when the haproxy processes running on the head gear(first gear) is terminated(killed), the app can not successfully auto scale down after a certain time if there is no traffic to the app.

Version-Release number of selected component (if applicable):
On devenv_3540

How reproducible:

Steps to Reproduce:
1. Create a scalable application, scale it up to 2 gears
2. ssh into the first gear(head gear) of the app, kill all haproxy processes
3. Do not access the app, wait for some time, then check that the app is auto scaled down

Actual results:
The app won't auto scale down

Expected results:
The app should auto scale down now that multiple load balancers are implemented.

Additional info:
The app will scale down if we don't terminate the haproxy processes on the head gear.
Comment 1 Jianwei Hou 2013-07-23 08:05:06 EDT
Also can not auto scale up when haproxy processes on head gear are killed.
Comment 2 Abhishek Gupta 2013-07-23 14:00:23 EDT
Multiple load balancers are not automatically implemented. The support is now there in the platform but the cartridge needs to be changed for that.

Based on the work being done in this release, we are now HA capable, just that HA is not provided out of the box.

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