Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1363698 - memory critical threshold
Summary: memory critical threshold
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-03 11:52 UTC by Lubos Trilety
Modified: 2017-03-23 04:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 04:03:57 UTC


Attachments (Terms of Use)

Description Lubos Trilety 2016-08-03 11:52:38 UTC
Description of problem:
Memory critical threshold is not correctly set. It's not easy to reach it even when the memory is 'completely' used as machine starts to swap before the threshold is exceeded. 90% of memory will not be used whilst there is some space in swap.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.38-1.el7scon.x86_64
rhscon-ceph-0.0.38-1.el7scon.x86_64
rhscon-core-selinux-0.0.38-1.el7scon.noarch
rhscon-ui-0.0.51-1.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Start some memory stress command, so the whole memory should be used (e.g. 110% of memory size).
2.
3.

Actual results:
System starts to swap so around 80% of memory and around 30% of swap is used.
No critical alert about memory usage is active.

Expected results:
Critical threshold for memory utilization is set to lower number or even better admin can set it somewhere.

Additional info:

Comment 1 Jeff Applewhite 2016-08-03 12:14:40 UTC
On MONs only


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