my-rook-config

Files

T

Travis Nielsen 234877e7c0 ceph: skip first mon health check at startup

At startup there is a race condition between the goroutine checking
for mon health and the first reconcile of the mons. There is a lock
that ensures only one of them will check the mon health at a time.
The issue is that if the wrong one gets there first, it will not
have the desired mon count initialized from the cluster CR as expected
and the healther checker will use a desired mon count of 0.
The desired count of 0 leads the health checker to remove
a mon since there are extra mons. Only one mon is allowed
to be removed at a time, and adjusting to fewer than two mons is
disallowed once there are at least two mons.

After the health checker is completed, the main reconcile of the mons
will proceed with the correct desired mon count of 3 and attempt
to restore to the real desired quorum size.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

2020-07-22 08:23:09 -06:00

cassandra

Cassandra: fixes unhandled type assertions

2020-04-04 14:00:39 +05:30

ceph

ceph: skip first mon health check at startup

2020-07-22 08:23:09 -06:00

cockroachdb

Cockroachdb: fixes unhandled type assertions

2020-04-04 14:00:42 +05:30

discover

crds: pick up the rook types in the v1 package