Project

General

Profile

Actions
Copy link

Bug #8176

closed

Change target_max_objects/target_max_bytes has no immediate effect

Added by David Zafman about 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I would expect to be able to change these values and affect the balance of data in the cache/base tiers. The function agent_choose_mode() would have to be called for all primary PGs for the affected pool.

Actions
Copy link
 #1

Updated by Samuel Just about 10 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #2

Updated by Sage Weil almost 10 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #3

Updated by David Zafman almost 10 years ago

This was fixed in a97129f19789cd3a5c81667059fdac5c120bdbe6 where ReplicatedPG::on_pool_change() was added and called by PG::handle_advance_map().

Actions
Copy link

Also available in: Atom PDF