You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 1.29.2, I am observing a problem with preserving the number of replicas. Previously, we were using version 1.24. In it, we added a controller that monitored the number of replicas and added a TieBreaker if there were fewer than 3 replicas.
According to the changelog in version 1.29.2, the number of replicas should increase automatically. But I see from my tests that this is not the case.
I add a resource with 2 replicas.
I delete the diskless replica, if it exists.
I expect a TieBreaker to be added, but this does not happen.
If our custom controller attempts to add a TieBreaker, it immediately goes into the Deleting state and gets stuck there until the resource definition is completely removed or the node with the TieBreaker is rebooted.
Manipulations with the DrbdOptions/auto-add-quorum-tiebreaker parameter do not change the situation, and the controller forcefully sets it to true after the restart.
Is this expected behavior?
The text was updated successfully, but these errors were encountered:
In version 1.29.2, I am observing a problem with preserving the number of replicas. Previously, we were using version 1.24. In it, we added a controller that monitored the number of replicas and added a TieBreaker if there were fewer than 3 replicas.
According to the changelog in version 1.29.2, the number of replicas should increase automatically. But I see from my tests that this is not the case.
If our custom controller attempts to add a TieBreaker, it immediately goes into the Deleting state and gets stuck there until the resource definition is completely removed or the node with the TieBreaker is rebooted.
Manipulations with the DrbdOptions/auto-add-quorum-tiebreaker parameter do not change the situation, and the controller forcefully sets it to true after the restart.
Is this expected behavior?
The text was updated successfully, but these errors were encountered: