-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.4] Support linearizable renew lease for 3.4 #14177
Conversation
LGTM, the only diff seams to be
everything else is the same |
the test TestV3CurlAuthClientTLSCertAuth also failed here recently. Another flake? |
Yes, let me take care of this one. |
bd9e9dd
to
c84ef43
Compare
cc @serathius @spzala @ptabor PTL, thx. |
I decided not to cherry pick this PR. We should only backport security fix and major/critical bug fixes. |
Cherry pick etcd-io#13932 to 3.4. When etcdserver receives a LeaseRenew request, it may be still in progress of processing the LeaseGrantRequest on exact the same leaseID. Accordingly it may return a TTL=0 to client due to the leaseID not found error. So the leader should wait for the appliedID to be available before processing client requests. Signed-off-by: Benjamin Wang <[email protected]>
c84ef43
to
07d2b1d
Compare
Moved this PR from 3.4.19 to 3.4.20. Part of #14232 |
@serathius @ptabor @spzala PTAL, thx. |
Cherry pick 13932 to 3.4.
Part of 14105
When etcdserver receives a LeaseRenew request, it may be still in
progress of processing the LeaseGrantRequest on exact the same
leaseID. Accordingly it may return a TTL=0 to client due to the
leaseID not found error. So the leader should wait for the appliedID
to be available before processing client requests.
Signed-off-by: Benjamin Wang [email protected]
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.