Actions
Bug #57570
closedmon-stretched_cluster: Site weights are not monitored post stretch mode deployment
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Stretch Clusters
Target version:
-
% Done:
100%
Source:
Tags:
backport_processed
Backport:
reef, quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Site weights are not monitored post-stretch mode deployment.
Basically, after we successfully enabled stretch mode, the two sites can have different weights and the cluster does not throw any warning messages.
Before stretch mode is enabled, there are checks that make sure that the weights of the two sites are the same, otherwise, it does not allow for the deployment of stretch mode.
ceph mon enable_stretch_mode mon_tie_breaker stretch_rule datacenter
Error EINVAL: the 2 datacenter instances in the cluster have differing weights 25947 and 15728 but stretch mode currently requires they be the same!
We can remove the host that is causing the issue, deploy stretch mode and add back the host, without any issues.
Should there be any checks if post-deployment, hosts ( OSDs ) are added to the sites, we show warning messages suggesting to keep the weights same?
Actions