Skip to content

rs3 changes for soak workload#414

Merged
rodesai merged 3 commits intomainfrom
rs3-soak-updates
Feb 4, 2025
Merged

rs3 changes for soak workload#414
rodesai merged 3 commits intomainfrom
rs3-soak-updates

Conversation

@rodesai
Copy link
Contributor

@rodesai rodesai commented Jan 25, 2025

some rs3 changes to get it going on the soak workload:

  • adds tls support for the rs3 connection
  • adds a metric that records the average get latency. This is done via a wrapper to the RS3 client so we can add more metrics easily later on.
  • the rs3 protocol was updated to pass the pss/store id in headers, so we need to generate specific stubs for each pss (stubs are very cheap to create, and they all share a grpc channel). As such, the channel is moved into RemotePssStubsProvider, which now owns the channel and creates stubs for a given pss. When creating a stub, it adds an interceptor that adds the right headers for a given pss

- adds tls support for the rs3 connection
- adds a metric that records the average get latency. This is done via a wrapper to the RS3 client so we can add more metrics easily later on.
- the rs3 protocol was updated to pass the pss/store id in headers, so we need to generate specific stubs for each pss (stubs are very cheap to create, and they all share a grpc channel). As such, the channel is moved into RemotePssStubsProvider, which now owns the channel and creates stubs for a given pss. When creating a stub, it adds an interceptor that adds the right headers for a given pss
@rodesai rodesai merged commit 92dbc1b into main Feb 4, 2025
1 check passed
@rodesai rodesai deleted the rs3-soak-updates branch February 4, 2025 17:31
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.

1 participant