Closed clement2026 closed 1 month ago
Hi @clement2026. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.
Attention: Patch coverage is 22.50000%
with 31 lines
in your changes missing coverage. Please review.
Project coverage is 68.79%. Comparing base (
2c53be7
) to head (8ab968e
). Report is 14 commits behind head on main.:exclamation: Current head 8ab968e differs from pull request most recent head ccbec07
Please upload reports for the commit ccbec07 to get more accurate results.
Files with missing lines | Patch % | Lines |
---|---|---|
client/v3/kubernetes/client.go | 0.00% | 27 Missing :warning: |
server/etcdserver/server.go | 69.23% | 3 Missing and 1 partial :warning: |
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: clement2026 Once this PR has been reviewed and has the lgtm label, please assign ahrtr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
@clement2026: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/ok-to-test
Hey @serathius, it would be great if you could check this out when you have a moment. Thanks!
18459 requires that a non-empty raft log snapshot is always available.
Can you explain this? Why a non-empty snapshot is always required? We don't have such restriction before.
Can you explain this? Why a non-empty snapshot is always required? We don't have such restriction before.
@ahrtr sure, check out this comment for more details https://github.com/etcd-io/etcd/pull/18459#issuecomment-2295388421
PR needs rebase.
After chatting with serathius, I've realized this PR isn’t needed anymore. I'll keep working on https://github.com/etcd-io/etcd/issues/17098 in a new PR. Closing this.
18459 requires that a non-empty raft log snapshot is always available. This PR creates a non-empty raft log snapshot on server startup.
Part of https://github.com/etcd-io/etcd/issues/17098
Key changes
shouldSnapshot
functiontests/integration/raft_log_snapshot_test.go
Blocked by