Project

General

Profile

Actions

Bug #45266

closed

follower monitors can grow beyond memory target

Added by Josh Durgin about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
High
Category:
Performance/Resource Usage
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The leader monitor periordically tells tcmalloc to release memory back to the OS, but follower monitors do not. This can result in follower monitors using more memory than their memory target, and potentially getting oom killed.

A workaround is to reset the mon_memory_target config option, which will cause all monitors to ask tcmalloc to release its free memory.

Alternately, mon_memory_autotune can be disabled.


Related issues 2 (0 open2 closed)

Copied to RADOS - Backport #45391: nautilus: follower monitors can grow beyond memory targetResolvedSridhar SeshasayeeActions
Copied to RADOS - Backport #45392: octopus: follower monitors can grow beyond memory targetResolvedSridhar SeshasayeeActions
Actions #1

Updated by Sridhar Seshasayee almost 4 years ago

  • Assignee set to Sridhar Seshasayee

Taking ownership of this.

-Sridhar

Actions #2

Updated by Josh Durgin almost 4 years ago

  • Pull request ID set to 34837
Actions #3

Updated by Neha Ojha almost 4 years ago

  • Status changed from New to Fix Under Review
Actions #4

Updated by Kefu Chai almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Sridhar Seshasayee almost 4 years ago

  • Copied to Backport #45391: nautilus: follower monitors can grow beyond memory target added
Actions #6

Updated by Sridhar Seshasayee almost 4 years ago

  • Copied to Backport #45392: octopus: follower monitors can grow beyond memory target added
Actions #7

Updated by Nathan Cutler almost 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF