First replica set member is not adding to existing replica set after failure

[sclorg]

First replica set member is not adding to existing replica set after failure

[lehmeyer]

The pull request #305 solves the problem.

[omron93]

The error can be simulated if the first POD and the corresponding PVC is deleted.

@lehmeyer Understand that deleting PVC will cause the issue. But did you have the problem with restarting primary in production usage? (without manually deleting a volume)

Kubernetes should remount the volume to restarted pod, so mongod in container should successfully reconnect to replicaset.

[lehmeyer]

The error can be simulated if the first POD and the corresponding PVC is deleted.

@lehmeyer Understand that deleting PVC will cause the issue. But did you have the problem with restarting primary in production usage? (without manually deleting a volume)

Kubernetes should remount the volume to restarted pod, so mongod in container should successfully reconnect to replicaset.

The problem exists if the data of the first replicaset (memberid = 0) no longer exists. Then a splitbrain situation arises with two independent replicasets that cannot be connected.

[omron93]

The problem exists if the data of the first replicaset (memberid = 0) no longer exists.

Agree that it might be an issue - although I don't know how this situation can happen.

But I think it's quite edge case - and it might be a bug in Kubernetes.
If it's worth fixing, then #305 looks good.

[hhorak]

mongodb container is not maintained any more in this org. closing.