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

xds: CHANNEL_ID hash should be random for the channel #9453

Merged
merged 2 commits into from
Aug 19, 2022

Conversation

ejona86
Copy link
Member

@ejona86 ejona86 commented Aug 17, 2022

The log id is an incrementing value starting from 0. That means the same
binary on two different machines will have the same hashes for each
consecutive Channel. That was not at all the intension of CHANNEL_ID.
From gRFC A42:

This can be used in similar situations to where Envoy uses
connection_properties to hash on the source IP address.

CC @apolcyn

The log id is an incrementing value starting from 0. That means the same
binary on two different machines will have the same hashes for each
consecutive Channel. That was not at all the intension of CHANNEL_ID.
From gRFC A42:

> This can be used in similar situations to where Envoy uses
> connection_properties to hash on the source IP address.
@ejona86 ejona86 added the TODO:backport PR needs to be backported. Removed after backport complete label Aug 17, 2022
@ejona86
Copy link
Member Author

ejona86 commented Aug 17, 2022

b/242896928

@ejona86 ejona86 enabled auto-merge (squash) August 19, 2022 00:07
@ejona86 ejona86 merged commit 618a4de into grpc:master Aug 19, 2022
@ejona86 ejona86 deleted the xds-channel-id-is-random branch August 19, 2022 15:51
@ejona86 ejona86 removed the TODO:backport PR needs to be backported. Removed after backport complete label Aug 19, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 19, 2022
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