Bug 1918792

Summary:	[BUG] Thanos having possible memory leak consuming huge amounts of node's memory and killing them
Product:	OpenShift Container Platform	Reporter:	Sergiusz Urbaniak <surbania>
Component:	Monitoring	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.6.z	CC:	alegrand, alkazako, andcosta, anowak, anpicker, bjarolim, cblecker, ccoleman, cpassare, ddelcian, dyocum, enorling, erooth, gparente, johan-fedora, juzhao, kakkoyun, knakai, lcosic, nmalik, oarribas, ocasalsa, openshift-bugs-escalate, pkrupa, ppostler, rbastos, rdomnu, rogbas, rphillips, rrackow, rugouvei, s.heijmans, skramaja, spasquie, steven.barre, surbania, trees, wking, xmorano
Target Milestone:	---	Keywords:	Reopened, ServiceDeliveryBlocker, UpcomingSprint
Target Release:	4.6.z
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1906496	Environment:
Last Closed:	2021-02-08 13:51:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1906496
Bug Blocks:

Comment 3 Junqi Zhao 2021-01-29 05:58:09 UTC

upgrade from 4.5.30 to 4.6.0-0.nightly-2021-01-28-234643, memory usage for thanos-querier does not increase too much during the whole upgrade process

Comment 7 errata-xmlrpc 2021-02-08 13:51:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:0308

Comment 8 Ryan Phillips 2021-02-09 21:32:49 UTC

*** Bug 1918827 has been marked as a duplicate of this bug. ***