ETCD-716: Rebase etcd 3.5.19 openshift 4.18 #316
+463
−200
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backport tools/benchmark/cmd/txn_mixed.go from commit 79b2777, pull request etcd-io#13038. Co-authored-by: Ivan Valdes <[email protected]> Signed-off-by: Ivan Valdes <[email protected]>
Signed-off-by: GitHub <[email protected]>
…-txn-mixed [3.5] backport: tools: add mixed read-write performance evaluation scripts
add learner check to readyz
Signed-off-by: Benjamin Wang <[email protected]>
Signed-off-by: Benjamin Wang <[email protected]>
Signed-off-by: Benjamin Wang <[email protected]>
Signed-off-by: Benjamin Wang <[email protected]>
Signed-off-by: Benjamin Wang <[email protected]>
[3.5] Add more info into log for learner member operations
[3.5] Bump `go.mongodb.org/mongo-driver` and `github.com/golang/glog` to address two CVEs
Signed-off-by: Marcel Franca <[email protected]>
…e-3.5 [3.5] Update golang toolchain to 1.22.12
The compaction behavior is changed in commit [02635](etcd-io@0263597) and introduces a latency issue. To be more speicific, the `ticker.C` acts as a fixed timer that triggers every 10ms, regardless of how long each batch of compaction takes. This means that if a previous compaction batch takes longer than 10ms, the next batch starts immediately, making compaction a blocking operation for etcd. To fix the issue, this commit revert the compaction to the previous behavior which ensures a 10ms delay between each batch of compaction, allowing other read and write operations to proceed smoothly. Signed-off-by: Miancheng Lin <[email protected]>
…e-latency [release-3.5] Fix a performance regression due to uncertain compaction sleep interval
Signed-off-by: joshjms <[email protected]> change go directive to 1.23 Signed-off-by: joshjms <[email protected]>
…-3.5 [3.5] Update golang toolchain to 1.23.6
To address CVE-2025-22869. Signed-off-by: Ivan Valdes <[email protected]>
…org-x-crypto-to-0.35.0 [3.5] dependency: Bump golang.org/x/crypto from v0.32.0 to v0.35.0
Signed-off-by: Ivan Valdes <[email protected]>
Signed-off-by: Ivan Valdes <[email protected]>
….23.7 [3.5] Bump go toolchain to 1.23.7
…org-x-net-to-v0.36.0 [3.5] dependency: bump golang.org/x/net from v0.34.0 to v0.36.0
Signed-off-by: Ivan Valdes <[email protected]>
…ry-pick-19520-to-release-3.5 [3.5] Add verify release assets GitHub workflow
Signed-off-by: Ivan Valdes <[email protected]>
…tore This PR will add the notion of cluster ID into the initial cluster discovery process. This allows us to automatically archive a data directory when we detect the cluster identifier changing. The cluster identifier will only change when we are running a restore operation. The detection requires that the revision.json (created by the revision monitor sidecar) contains the cluster id. The cluster identifier is also stored in the local WAL, which is much more expensive to parse. We're going to only fallback to it when we could not get the cluster id from the revision.json for any reason. Otherwise the WAL stays untouched, no repair operations are attempted when it is found corrupted. Signed-off-by: Thomas Jungblut <[email protected]>
Konflux is replacing RH's internal build system OSBS. OSBS supported a build-time dependency injection system called "cachito". Konflux replaces this with "cachi2" which works differently. REMOTE_SOURCES no longer need to be copied into place and there is no need to source cachito's environment information (Konflux automatically rewrites the Dockerfile to source cachi2/cachi2.env before running the original RUN commands). Additionally, cachito appears to have provided go.sum dependencies whereas cachi2 requires all build-time dependencies in go.mod. Missing dependencies are added to go.mod as // indirect in this change.
force-new-cluster seems to have similar watch cache issues as the ordinary snapshot restore. This PR introduces the already existing utl logic as a separate package into the server-side code. This will only introduce a revbump flag, but under the hood implement both rev bumping and compaction markers. Signed-off-by: Thomas Jungblut <[email protected]>
This adds the min and max TLS version support from etcd-io#13506 and etcd-io#15156 to the grpc proxy. Signed-off-by: Thomas Jungblut <[email protected]>
…tcd-3.5.19-openshift-4.18
|
/payload 4.18 nightly blocking |
|
@Elbehery: trigger 11 job(s) of type blocking for the nightly release of OCP 4.18
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b10ac490-fa08-11ef-8ac1-4e1013300a84-0 |
|
/payload 4.18 nightly informing |
|
@Elbehery: trigger 65 job(s) of type informing for the nightly release of OCP 4.18
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b5065c30-fa08-11ef-97d0-e560f27c9b96-0 |
openshift-ci
bot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dusk125, Elbehery The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold for @sdodson and team to finish kernel 9.6 testing |
openshift-ci
bot
added
the
do-not-merge/hold
Elbehery
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@Elbehery: This pull request references ETCD-716 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.z" version, but no target version was set. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@Elbehery: This pull request references ETCD-716 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.z" version, but no target version was set. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@Elbehery: This pull request references ETCD-716 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@joepvd we need go1.23 base image for this 👍🏽 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR rebases etcd 3.5.19 into openshift-4.18.
running
makelocallycc @openshift/openshift-team-etcd @sdodson