Project

General

Profile

Actions
Copy link

Bug #17414

open

multisite: handle runtime changes to number of mdlog/datalog shards

Added by Casey Bodley over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Casey Bodley
Target version:
-
% Done:

0%

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

Description

After starting sync, restarting a gateway with a different value of rgw_md_log_max_shards or rgw_data_log_num_shards can cause a segmentation fault.

Radosgw should only consult these values if it has not yet initialized its sync status. Furthermore, rgw_md_log_max_shards should only be consulted by the metadata master zone, and all other zones should query that value from the metadata master when initializing its mdlog sync status.

Related issues 1 (0 open — 1 closed)

Related to rgw - Bug #18488: multisite: segfault after changing value of rgw_data_log_num_shardsResolvedCasey Bodley01/11/2017

Actions
Actions
Copy link
 #1

Updated by Casey Bodley over 7 years ago

  • Related to Bug #18488: multisite: segfault after changing value of rgw_data_log_num_shards added
Actions
Copy link

Also available in: Atom PDF