Bug #42485
closedverify_upmaps can not cancel invalid upmap_items in some cases
0%
Description
We can not cancel in verify_upmap if remap an osd to different root bucket,
cluster topology:
osd.0 ~ osd.29 belongs to datacenter 1
osd30 ~ osd.59 belongs to datacenter 2
crush rule:
take datacenter 1
chooseleaf 2 host
emit
take datacenter 2
chooseleaf 2 host
emit
The pg's primary osd in datacenter 1.
We should cancel the pgid from upmap_items like below
from [26,12,54,46] to [30,12,54,46]
pg_upmap_items [26,30]
from [16,25,53,31] to [40,25,53,0]
pg_upmap_items [16,20,31,0]
Updated by Sage Weil over 4 years ago
- Status changed from New to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42546: mimic: verify_upmaps can not cancel invalid upmap_items in some cases added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42547: nautilus: verify_upmaps can not cancel invalid upmap_items in some cases added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42548: luminous: verify_upmaps can not cancel invalid upmap_items in some cases added
Updated by David Zafman over 4 years ago
- Status changed from Pending Backport to Resolved
Updated by Nathan Cutler over 4 years ago
NOTE: https://github.com/ceph/ceph/pull/31131 was merged to master and backported to nautilus and luminous, before it was found to be problematic, and needed to be reverted.
For nautilus, both the backport and its revert were merged for 14.2.5.
For luminous, both the backport and its revert were merged for 12.2.13.
For mimic, no backport was undertaken.