Some annoying thing has happened with me. Is this only me or it has happened with others. If so, then let’s see what best should be done to get rid of the problem. There are so many people all over the world who are strictly follow the Google maps, and logically it is right because Google maps is the best application made by Google which is an advantage as they can blindly follow the path provided. However, it is very much proved that the Google maps are technically correct. For businessmen, especially they follow these maps because due to many reasons they may need to shift the location and here comes the role of the maps. So as this application is widely used then this needs to be accurate and exact.
Now, if this is not right then we need to change this because they do not want any incorrect information on the application which is a trouble for them too:
Although, the above are simple and easy to get through the changes required but still there are times when the things don’t happen as we want or they face issues while doing the above steps and then they can easily get connected to the Google map customer service number which is provided to them and they can call and get directly in touch with the executives as they are the best people to sort the issues as they are well- trained and experienced to get instant and best solutions for them.
the realm name is not part of the period, so other clusters won't be notified about realm renames. radosgw-admin should recommend running the command on each cluster
Copied to rgw - Backport #19775: jewel: multisite: realm rename does not propagate to other clusters Resolved
Copied to rgw - Backport #19776: kraken: multisite: realm rename does not propagate to other clusters Resolved
Related to Duplicates Duplicated by Blocks Blocked by Precedes Follows Copied to Copied from Issue # Delay: days Cancel
Copied to Backport #19775: jewel: multisite: realm rename does not propagate to other clusters added
Copied to Backport #19776: kraken: multisite: realm rename does not propagate to other clusters added
I think this might be a regression issue introduced by https://github.com/ceph/ceph/commit/082e86c58f5abb93e2a912e603d86f12bc47972c. We didn't see such issue in Jewel when trying to use old balancer.
The reason should be that currently MDS's export_targets in MDSMap are empty even if they need to do rebalance because we didn't update MDSRank's export_targets according to balance state, then MDSRank's tick won't update MDSMap's export_targets to Mon.
And the new function MDBalancer::hit_targets should be aimed to do such things, but it hadn't been called at anywhere.