Skip to content

[Antithesis+Robustness] Add a client that connects to all members #20052

Open
@serathius

Description

@serathius

What would you like to be added?

Currently we configure clients to connect to a single etcd member. This ensures that member will always receive traffic after it goes down. If clients were created to all of etcd they would migrate out of it and not get back due to stickiness.

Still I think it would be good to have 1 client that loadbalances. We can split ClientCount available into MemberClientCount and ClusterClientCount, where member connects to single member and cluster to all members in cluster.

/cc @joshjms @henrybear327 @nwnt

Why is this needed?

Reason is finding bugs in retry logic in cases where request failed to first member and then loadbalancer moved it to other member for a retry.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions