On 3/2/21 7:17 PM, Stefan Kooman wrote:
What is output of "ceph daemon osd.0 config get ms_bind_ipv4" on the
osd0 node?
ceph daemon osd.0 config get ms_bind_ipv4
{
"ms_bind_ipv4": "true"
}
And
ceph daemon mds.mds1 config get ms_bind_ipv4
{
"ms_bind_ipv4": "true"
}
for that matter.
Now I'm typing this I'm like, hmm, there was an issue with this on the
mailinglist related to this, as in where you would need to disable ipv4
explicitly. I believe it was a peering issue between PGs.
OK, so this is probably it. And up to kernel 5.11 (I'll test 5.10 as
well) this would not be a problem.
I should be able te reproduce on a couple of test clusters that are
configured similarly, and be able to test if setting ms_bind_ipv4=false
on OSDs / MDSs fixes the issue.
I would like to have the heuristic to prefer IPv6 over IPv4 when
filtering addresses (as that is default / common behavior for most if
not all dual stack systems) ;-).
Hmm, we looked up the documentation, and it seems lacking this whole
options in master / latest:
https://docs.ceph.com/en/latest/rados/configuration/ms-ref/
The ms_bind_ipv6 option states the following:
Description
Enable to bind daemons to IPv6 addresses instead of IPv4. Not
required if you specify a daemon or cluster
So, it says: _instead_. We have configured ms_bind_ipv6, so it should
not, according to documentation, bind to IPv4, but to IPv6 only. So
either the documenation is not correct, or the current behaviour of the
daemons is not correct.
Anyways, I'll come back if disabling binding to IPv4 works.
Gr. Stefan
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
