Skip to content

Conversation

@creamsoup
Copy link
Contributor

FYI, the proto is not updated yet.

@creamsoup creamsoup requested a review from zhangkun83 December 18, 2019 23:54
if (typeCase != LoadBalanceResponseTypeCase.SERVER_LIST) {
if (typeCase == LoadBalanceResponseTypeCase.FALLBACK_RESPONSE) {
useFallbackBackends();
maybeUpdatePicker();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to call cancelFallbackTimer()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

verify(subchannelPool)
.returnSubchannel(eq(subchannel2), eq(ConnectivityStateInfo.forNonError(READY)));

// verify fallback (no backends)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The more common case is that there are fallback backends.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@creamsoup
Copy link
Contributor Author

although this change is backward compatible, waiting for the proto to be published.

@creamsoup creamsoup merged commit 641d74f into grpc:master Jan 10, 2020
@creamsoup creamsoup deleted the grpclb_fallback branch January 10, 2020 21:54
ejona86 added a commit to ejona86/grpc-java that referenced this pull request Feb 10, 2020
This noticed that load_balancer.proto had local changes introduced
in grpc#6549. This was not noticed by Bazel because grpclb was not using
the io_grpc_grpc_proto repository. These issues have been fixed.
ejona86 added a commit that referenced this pull request Feb 10, 2020
This noticed that load_balancer.proto had local changes introduced
in #6549. This was not noticed by Bazel because grpclb was not using
the io_grpc_grpc_proto repository. These issues have been fixed.
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants