-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Plans for v3.4.20 release #14232
Comments
Nice to backport: #12335 |
Thanks for the feedback. I just had a quick review on the PR, and it's a minor change and should be safe to backport. Please feel free to deliver a PR for this. |
Thanks for the feedback. I agree the PR can improve the performance/throughput, but it also added a new flag Please read #14169 (comment) if you want to quickly understand the context of the PR. Personally, I incline to backporting it to 3.4. |
I added 14169 into the list, please let me know if anyone have any concerns. @serathius @spzala @ptabor |
I pinged the original author of PR 12846, but got no response so far. |
- Backporting: etcd-io#12846 - Reference: etcd-io#14232
@ahrtr #14246 - have backported the requested PR. I maybe lacking understanding, but from the looks of it, this function isn't called anywhere (even in the original PR), am I doing this correctly? Thanks. @ptabor @spzala @serathius |
- Backporting: etcd-io#12846 - Reference: etcd-io#14232 Signed-off-by: vivekpatani <[email protected]>
Thanks @vivekpatani for the PR. Are you talking about |
- Backporting: etcd-io#12846 - Reference: etcd-io#14232 Signed-off-by: vivekpatani <[email protected]>
- Backporting: etcd-io#12846 - Reference: etcd-io#14232 Signed-off-by: vivekpatani <[email protected]>
@ahrtr I think I had some misunderstanding, the PR is now fixed/mergeable, please feel free to review when you have a minute, thank you! |
Can we also consider backporting PR #12871? |
@ahrtr #12762 is fix for #12680, in the end the solution was done in one, but three PRs:
As all of them change how pending requests are handled during leader election I would prefer to merge all of them to avoid this logic to diverge between branches. Partial backport means that we could end up not really fixing it. |
@ramses you'll need to make a "fork" on GitHub, then push to that, and open the PR across repos. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request |
Thanks @endocrimes , realized that immediately after :-) |
This is a backport of etcd-io#13435 and is part of the work for 3.4.20 etcd-io#14232. The original change had a second commit that modifies a changelog file. The 3.4 branch does not include any changelog file, so that part was not cherry-picked. Local Testing: - `make build` - `make test` Both succeed.
Thanks @serathius for the reminder. I will take care of all of them myself later. |
This is a backport of etcd-io#13435 and is part of the work for 3.4.20 etcd-io#14232. The original change had a second commit that modifies a changelog file. The 3.4 branch does not include any changelog file, so that part was not cherry-picked. Local Testing: - `make build` - `make test` Both succeed. Signed-off-by: Ramsés Morales <[email protected]>
- Backporting: etcd-io#12846 - Reference: etcd-io#14232 Signed-off-by: vivekpatani <[email protected]>
I saw the following errors multiple times in 3.4 pipeline, but never get time to have a deep dive,
Any help is welcome! Thanks! |
Although there are still some issues which need further investigation, we have already finished backporting all existing PRs. @endocrimes Do you have bandwidth to run Jepsen test on release-3.4? |
@ahrtr sure 👍 |
I may release 3.4.20 sometime next week when all remaining tasks(see below) are done,
@serathius @spzala @ptabor @hexfusion Please kindly let me know if you have any comments or concerns. |
@ahrtr thank you! No concerns, and sounds great. |
@endocrimes any update on the Jepsen test on release-3.4? |
#14256 isn't a blocker any more, please see my comment #14256 (comment) |
@ahrtr running them now :) |
Hi @ahrtr @lavacat @serathius found one last one that may need to be back ported? #13824 Please let me know if that is the case. Thanks. |
Thanks @vivekpatani . etcd 3.5.4 (and main) is using DialContext, while etcd 3.4.19 (and release-3.4 latest code) is using Dial. So release-3.4 doesn't have the issue #13810. I agree |
Talked to @endocrimes , no any new issue found during the Jepsen test. Will release 3.4.20 soon. |
3.4.20 is just released, https://github.com/etcd-io/etcd/releases/tag/v3.4.20 . Thanks everyone in the CC list. It's really the result of great team work! Thanks again !!! |
Thanks for doing this.
etcd-3.5 latest release is not using |
@vivekpatani The reason is the PR #13824 has been cherry picked to release-3.5 yet. Please feel free to deliver a PR for that. thx In release-3.5, DialContext is used in the transport, but Dial is used in the In release-3.4, both places are using |
- Backporting: etcd-io#12846 - Reference: etcd-io#14232 Signed-off-by: vivekpatani <[email protected]>
This is a backport of etcd-io#13435 and is part of the work for 3.4.20 etcd-io#14232. The original change had a second commit that modifies a changelog file. The 3.4 branch does not include any changelog file, so that part was not cherry-picked. Local Testing: - `make build` - `make test` Both succeed. Signed-off-by: Ramsés Morales <[email protected]>
We intentionally skipped back-porting some bug fixes in 3.4.19 in order to minimize the impact. Since 3.4.19 is already released and validated to be working well, so we can consider to release 3.4.20 to backport some PRs.
Pipelines/test
There are still some flaky test failures from time to time. As previous release, any fix to stabilize the pipeline is welcome.
Issues/PRs that should be included in 3.4.20
MaxConcurrentStreams
for http2 #14169Issues/PRs not considered in 3.4.20
See etcdserver: significantly reduces start-up time #11779 (comment)
Please feel free to chime in if you think any PR/issues need to be investigated or included in 3.4.20. Please also feel free to let us know if anyone has any concerns or comment. cc @ptabor @serathius @spzala @hexfusion @mitake @lavacat @endocrimes @dims @liggitt @neolit123
The text was updated successfully, but these errors were encountered: