Actions
Bug #7875
closedosd: pg_pool_t hitset fields incompat
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If the hitset fields get used in pg_pool_t the encoding is marked as incompatible. This breaks old clients that don't care about hitsets (include any kernel client).
I can't figure out why this was added. Is there any harm done if one OSD is tracking hitsets and another doesn't? We can add checks on the mon so that you can't enable hitsets until all osds support it (that would be friendlier), but I'm not sure it's even worth the effort.
Updated by Sage Weil about 10 years ago
- Status changed from In Progress to Resolved
Updated by Greg Farnum about 10 years ago
If you have a mix of OSDs tracking hitsets in the cluster, your data tracking isn't going to make any sense...what did you do to resolve this?
Actions