mvcc: add watch failpoints for robustness testing#22044
Conversation
Signed-off-by: darshil929 <darshilt.work29@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: darshil929 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @darshil929. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 12 files with indirect coverage changes @@ Coverage Diff @@
## main #22044 +/- ##
==========================================
- Coverage 69.66% 69.65% -0.02%
==========================================
Files 449 449
Lines 38177 38177
==========================================
- Hits 26596 26591 -5
- Misses 10149 10153 +4
- Partials 1432 1433 +1 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
/retest |
2 similar comments
|
/retest |
|
/retest |
This adds three gofail failpoints to the etcd server watch code so the robustness tests can inject slowness into the paths listed in issue #18681: watcher synchronization, victim resynchronization, and progress notification. All three sit in server/storage/mvcc/watchable_store.go, right before each function takes the store lock, so an injected sleep delays the operation without holding the lock during the sleep.
Each failpoint is registered as a gofailSleepAndDeactivate for the exploratory scenarios, following the same pattern as beforeSendWatchResponse from #17680. No build changes are needed since gofail-enable already instruments server/storage/mvcc.
Validation:
Fixes #18681