Skip to content
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

release-3.3: bump gRPC to 1.23 #10984

Closed
wants to merge 11 commits into from

Conversation

hexfusion
Copy link
Contributor

#9956 has been very disruptive and while I am looking forward to the new balancer backport for 3.3 it seems practical to cut a release patching 3.3 with the old balancer then backporting the new balancer after it is stable. This would give folks an option to use the old or new balancers while having a patched release.

Backports to release-3.3 :

TODO

Fixes #9956

/cc @gyuho @jpbetz @xiang90 @spzala @jingyih @wenjiaswe

mbrannock and others added 11 commits July 29, 2019 18:20
gRPC has moved the transport package to an internal-only directory. This
eliminates direct use of the transport package in the stress test in
favor of the error code from gRPC that represents a connection problem.

https://godoc.org/google.golang.org/grpc/internal/transport is the new
location for the package, which says it's not intended to be imported
directly. Instead, the maintainers suggested to use the code Unavailable
to detect a connection problem.

This change slightly reorganizes the stresser test error handling.
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Otherwise, grpc.DialContext would just return before
connection is up.

Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
These changes were originally fixed in etcd-io#9860 commit 9304d1a

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
@hexfusion
Copy link
Contributor Author

/cc @retroflexer @alaypatel07

@gyuho
Copy link
Contributor

gyuho commented Aug 6, 2019

cut a release patching 3.3 with the old balancer then backporting the new balancer after it is stable

We are already backporting new balancer + new gRPC later #10980. Given 3.4 time-frame, it doesn't make sense to support two balancer implementation. If we find a bug in gRPC, we should fix based on latest balancer implementation, not on the old ones.

Defer to @jpbetz @xiang90

@xiang90
Copy link
Contributor

xiang90 commented Aug 6, 2019

Yea... Let us just maintain one balancer.

@hexfusion hexfusion closed this Aug 6, 2019
@hexfusion
Copy link
Contributor Author

Yea... Let us just maintain one balancer.

While this does seem pragmatic, bumping a dependency to a patch release does not add additional support. The plan is to upgrade to new balancer once stable. At that time we would only be supporting a single balancer, not two. Introducing a new balancer to two versions does add risk. I will close this but if we find a flaw in the new balancer we should consider this as an alternative as it does not change balancer functionality for 3.3. Thanks for the review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants