Actions
Fix #39071
openmonclient: initial probe is non-optimal with v2+v1
Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
MonClient
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When we are probing both v2 and v1 addrs for mons, we treat them as separate mons, which means we might be probing N endpoints but only N/2 mons if we happen to pick the v2 and v1 endpoints on the same mons. If enough mons are down this can lead to slow delays for CLI commands.
Instead, we should pick distinct mons, and if we don't know whether they are v2 or v1, we should probe both.
I think this means we should get rid of the idea of probing via a fake monmap, and instead do the probing in a more explicit way that let's us check both the v2 and v1 ports.
Actions