etcd
etcd copied to clipboard
raft loop prober with counter
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
cc @ahrtr
This approach depends on the liveness probe's frequency / interval, the principle is the instance is alive as long as there is at least one tick event since last liveness check
.
Overall looks good. Please feel free to reuse (might need minor update) the test case in https://github.com/etcd-io/etcd/pull/16710.
Discussed during sig-etcd triage meeting. This is still an important pr for etcd, @chaochn47 do you have some time to rebase and continue this effort?
Yeah, I will take a look and drive to the resolution next week.
@chaochn47: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-etcd-verify | d126728781dc6ee1d41e500e9cacd4b65df638c9 | link | true | /test pull-etcd-verify |
pull-etcd-unit-test-amd64 | d126728781dc6ee1d41e500e9cacd4b65df638c9 | link | true | /test pull-etcd-unit-test-amd64 |
pull-etcd-unit-test-arm64 | d126728781dc6ee1d41e500e9cacd4b65df638c9 | link | true | /test pull-etcd-unit-test-arm64 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
Instructions 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. I understand the commands that are listed here.