Skip to content

Add LB policy config message for AutoSharding - #179

Open
easwars wants to merge 3 commits into
grpc:masterfrom
easwars:slicer_lb_config
Open

Add LB policy config message for AutoSharding#179
easwars wants to merge 3 commits into
grpc:masterfrom
easwars:slicer_lb_config

Conversation

@easwars

@easwars easwars commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

As per gRFC A119 (grpc/proposal#551).

@markdroth

Copy link
Copy Markdown
Member

Please see my comments in the gRFC. There are a few changes I'd like to see here.

@easwars

easwars commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Please see my comments in the gRFC. There are a few changes I'd like to see here.

Awesome. Thanks. Will address those comments and then get back here.

@easwars easwars changed the title Add LB policy config message for Slicer Add LB policy config message for AutoSharding Aug 11, 2026
@easwars

easwars commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

@markdroth : I just updated this PR with the changes from A119. PTAL

Also, I was wondering about the two field names that we currently have:

  • slicing_target: Should this be changed to sharding_target?
  • slice_key_header_name: Should this be changed to sharding_key_header_name or just key_header_name?

Thanks

// "Locality" before sending. If a "%s" token is present, but the "Locality"
// information is not available to the LB policy, the token will be replaced
// with an empty string.
string slicing_target = 2;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, I'd call this autosharding_target.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done


// Name of the request header containing the application-defined key. This key
// is used to look up the matching key-range assigned by the sharding service.
string slice_key_header_name = 3;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yes, key_header_name seems like a good name for this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants