Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.1.0
Description
Testcase: TestPersistentVolumeKillPodAndOperator
Scenario:
- Couchbase cluster of size 4 is created with default persistent volume mount
- Operator and pod 0001 is killed in parallel
Observation:
Once operator respawned, it is creating a new pod 0004 to replace the killed pod without attempting delta recovery of pod 0001
Cluster events:
Event schema validation failed:
|
NewMemberAdded | New member test-couchbase-54gn7-0000 added to cluster
|
NewMemberAdded | New member test-couchbase-54gn7-0001 added to cluster
|
NewMemberAdded | New member test-couchbase-54gn7-0002 added to cluster
|
NewMemberAdded | New member test-couchbase-54gn7-0003 added to cluster
|
RebalanceStarted | A rebalance has been started to balance data across the cluster
|
RebalanceCompleted | A rebalance has completed
|
BucketCreated | A new bucket `PVBucket` was created
|
NewMemberAdded | New member test-couchbase-54gn7-0004 added to cluster | <== no anyof members matched
|
RebalanceStarted | A rebalance has been started to balance data across the cluster
|
MemberRemoved | Existing member test-couchbase-54gn7-0001 removed from the cluster
|
RebalanceCompleted | A rebalance has completed
|
In fact we should probably let updateMembers add every node we get from ClusterInfo.Nodes to c.members since they would have all been members prior to operator crash. The operator would just continue to reconcile members based on their state.