Bug 1870189: Bump v3.4.14 #65
Conversation
This makes it possible to run an etcd node for testing and development without placing lots of load on the file system. Fixes etcd-io#11930. Signed-off-by: David Crawshaw <[email protected]>
…-#11946-release-3.4 Automated cherry pick of etcd-io#11946
modify file util.
Handle negative value input which currently gives a runtime error.
Handle the related panic and clarify doc.
When an etcd instance attempts to perform service discovery, if a cluster size with negative value is provided, the etcd instance will panic without recovery because of
…-#11841-upstream-release-3.4 Automated cherry pick of etcd-io#11841
…-#11830-upstream-release-3.4 Automated cherry pick of etcd-io#11830
…-#11818-upstream-release-3.4 Automated cherry pick of etcd-io#11818
…-#11796-upstream-release-3.4 Automated cherry pick of etcd-io#11796
…-#11608-upstream-release-3.4 Automated cherry pick of etcd-io#11608
…-#11845-upstream-release-3.4 Automated cherry pick of etcd-io#11845
…-#11795-upstream-release-3.4 Automated cherry pick of etcd-io#11795
…-#11807-upstream-release-3.4 Automated cherry pick of etcd-io#11807
…-#11787-upstream-release-3.4 Automated cherry pick of etcd-io#11787
wal: add slice bound checks in decoder CHANGELOG-3.5: add wal slice bound check CHANGELOG-3.5: add "decodeRecord" Signed-off-by: Gyuho Lee <[email protected]>
Currently, watch cancel requests are only sent to the server after a message comes through on a watch where the client has cancelled. This means that cancelled watches that don't receive any new messages are never cancelled; they persist for the lifetime of the client stream. This has negative connotations for locking applications where a watch may observe a key which might never change again after cancellation, leading to many accumulating watches on the server. By cancelling proactively, in most cases we simply move the cancel request to happen earlier, and additionally we solve the case where the cancel request would never be sent. Fixes etcd-io#9416 Heavy inspiration drawn from the solutions proposed there.
…r will check File Descriptor Requirements ,and count all fds in used. And recorded some logs when in used >= limit/5*4. Just recorded message. If fds was more than 10K,It's low performance due to FDUsage() works. So need to increase it. see etcd-io#11969 for more detail.
…-#11798-upstream-release-3.4 Automated cherry pick of etcd-io#11798
…of-#12066-origin-release-3.4 Automated cherry pick of etcd-io#12066
…-#12060-upstream-release-3.4 Automated cherry pick of etcd-io#12060
…#11986-upstream-release-3.4 Automated cherry pick of etcd-io#11986
|
marketplace.. /test e2e-aws-upgrade |
|
soak /test all |
|
/retest |
|
/test e2e-aws |
|
soak /test all |
|
/retest |
1 similar comment
|
/retest |
openshift-ci-robot
removed
the
bugzilla/valid-bug
|
@hexfusion: This pull request references Bugzilla bug 1870189, which is invalid:
Comment 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 kubernetes/test-infra repository. |
openshift-ci-robot
added
the
bugzilla/invalid-bug
|
/retest |
|
@hexfusion: This pull request references Bugzilla bug 1870189, which is invalid:
Comment 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 kubernetes/test-infra repository. |
1 similar comment
|
@hexfusion: This pull request references Bugzilla bug 1870189, which is invalid:
Comment 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 kubernetes/test-infra repository. |
|
/bugzilla refresh |
|
@hexfusion: This pull request references Bugzilla bug 1870189, which is invalid:
Comment 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 kubernetes/test-infra repository. |
hexfusion
added
bugzilla/valid-bug
|
/hold cancel |
openshift-ci-robot
removed
the
do-not-merge/hold
hexfusion
added
the
staff-eng-approved
|
4.8 is open as 4.7 is GA group-lead approval should not be required I will look into why this is flagged. But I believe it is because the PR was open against 4.7 originally. |
|
/test all |
|
/test e2e-aws-upgrade |
|
I feel confident that this PR has been reasonably vetted and take responsibility for self-tagging but we need this to soak in CI. |
|
@hexfusion: All pull requests linked via external trackers have merged: Bugzilla bug 1870189 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
This PR brings
openshift/etcdto latest in release-3.4 upstream release 3.4.14. Notable changes since v3.4.9.v3.4.10
v3.4.11
v3.4.12
v3.4.13
v3.4.14