We found a solution to this issue. Apparantly it only occurs when you have some crash and there is just one node left in the cluster. If you set up a cluster with 3 or more nodes and make sure that after a crash you have at least 2 nodes surviving, you will not face this issue.
I guess this is because of how the software is build. Maybe someone can elaborate on how this works exactly?
I would be interested ...