Description
Right now bootstrap for a function can happen in case of recovery scenarios. In this case bootstrapping will continue to run and will stop any subsequent rebalance.
Need a way to stop bootstrap process explicitly by a user, so that the user can undeploy the current function if they want to.
Attachments
Issue Links
- depends on
-
MB-30421 [Backport][System test]: Mitigate panic from go-couchbase when failover logs are requested post KV hard failover
- Closed
For Gerrit Dashboard: MB-30427 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
97496,4 | MB-30427 Get out of bootstrap state after STREAMREQs are fired | unstable | eventing | Status: MERGED | +2 | +1 |
97499,4 | MB-30427 Test simulating function bootstrap after losing KV vbuckets | unstable | eventing | Status: MERGED | +2 | +1 |