Bug 1062573 - abused gear will not be throttled
Summary: abused gear will not be throttled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks: 1018342 1057734
TreeView+ depends on / blocked
 
Reported: 2014-02-07 10:58 UTC by Meng Bo
Modified: 2015-05-14 23:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-26 19:11:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Meng Bo 2014-02-07 10:58:22 UTC
Description of problem:
Create gear on the node, make sure the watchman is running.
Use some shell script to use high cpu on the gear, check the /var/log/messages
and cannot find the gear being throttled.

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

How reproducible:
always

Steps to Reproduce:
1. Create a gear on the node
2. Use shell script to burn the cpu
$ dd of=/dev/null if=/dev/zero
3. Check if the gear is throttled

Actual results:
The gear will not be throttled here

Expected results:
The gear should be throttled since abuse

Additional info:
# tailf /var/log/messages
Feb  7 05:01:40 ip-10-235-6-7 watchman[1962]: Starting throttler => throttle at: 30.00%, restore at: 70.00%, period: 120, check_interval: 5.00
Feb  7 05:01:40 ip-10-235-6-7 watchman[1962]: Starting Watchman => delay: 20s

Comment 1 openshift-github-bot 2014-02-11 00:15:24 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/d67f4f8d2283fcd515a61ead5ff90dab97ba30d0
Bug 1062573 -  abused gear will not be throttled

Comment 2 Meng Bo 2014-02-11 05:29:48 UTC
Feb 11 00:26:02 ip-10-16-155-161 watchman[1969]: Throttler: throttle => 52f99837c7ca5d728c00003e (118.487)
Feb 11 00:26:22 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (337.283))
Feb 11 00:26:42 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (511.151))
Feb 11 00:27:02 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (619.986))
Feb 11 00:27:22 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (613.412))
Feb 11 00:27:42 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (613.597))
Feb 11 00:28:02 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (417.352))
Feb 11 00:28:22 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (244.617))
Feb 11 00:28:42 ip-10-16-155-161 watchman[1969]: Throttler: REFUSED restore => 52f99837c7ca5d728c00003e (still over threshold (72.721))
Feb 11 00:29:02 ip-10-16-155-161 watchman[1969]: Throttler: restore => 52f99837c7ca5d728c00003e (7.327)


Issue fixed on devenv_4357.


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