Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1622212

Summary:	[free-int] no podAntiAffinity set on cassandra pods
Product:	OpenShift Container Platform	Reporter:	Justin Pierce <jupierce>
Component:	Hawkular	Assignee:	John Sanda <jsanda>
Status:	CLOSED WONTFIX	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, jupierce, yufchang
Target Milestone:	---	Keywords:	OnlineStarter
Target Release:	3.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-24 17:43:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Justin Pierce 2018-08-24 18:20:50 UTC

Description of problem:
One of our 3 infrastructure nodes was scheduled with all three hawkular-cassandra pods which had the consequence of consuming the majority of the memory on the box and effectively disabling logging.  

Version-Release number of selected component (if applicable):
v3.11.0-0.21.0

Actual results:
See attachment for problematic pod distribution.


Expected results:
pods should distribute evenly across HA infra nodes. Logging uses podAntiAffinity in the pod spec to achieve this.

Comment 2 John Sanda 2018-08-27 17:50:13 UTC

How are you checking memory usage? Seeing high memory usage is normal and expected for something like Cassandra which relies heavily on mmap for I/O. Most writes in Cassandra go to the operating system file cache, and Cassandra defers to the OS to decide when something should be written out to disk. I explained this in a little more detail at https://bugzilla.redhat.com/show_bug.cgi?id=1596327#c11.