I’ve read through pretty much all the other “under-replicated” topics here and don’t see a resolution to the following issue. Which I’ve seen on 2 clusters so far.
In both clusters I’m seeing ranges that report existing twice on the same node, where one is the follower and the other is the leader and reports itself as underreplicated. Even after manually enqueueing the range and a rolling restarting the situation doesn’t change. See screenshots of an example range below.
In both cases it happened after a rolling restart, though the circumstances of that restart were different. One involved adding locality flags to the cluster, the other was decommissioning of a dead node and replacing it.
Any input on what to investigate in this kind of situation would be great.