Project

General

Profile

Feature #43071

sync modules could not sync buckets with custom placement

Added by Chang Liu over 4 years ago. Updated over 4 years ago.

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

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

if a bucket uses a placement that does not exist in the target zone, es module could not sync this bucket to the target zone. error logging shows as flowing :

meta sync: ERROR: can't store key: bucket.instance: *
data sync: ERROR: failed to fetch bucket instance info for *
ERROR: select_bucket_placement() returned -22

History

#1 Updated by Abhishek Lekshmanan over 4 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from the elastic search sync module could not sync buckets with custom placement to sync modules could not sync buckets with custom placement

Currently you'd require all the target zones also containing these pools, there is discussion in ceph-devel if we can relax this behaviour for the future.

#2 Updated by Abhishek Lekshmanan over 4 years ago

  • Priority changed from Urgent to Normal

Also available in: Atom PDF