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
[fast-client][server] Throw 403 for metadata request that does not have storage read quota enabled #975
Conversation
...s/venice-server/src/main/java/com/linkedin/venice/listener/ServerReadMetadataRepository.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me overall. Just have one nit. And for my curiosity, have we ensured all fast client would have storage read quota enabled? Like, when they onboard, will this config be turned on automatically?
This is done manually for now but later it can and will be automated/self serve. |
4d5ced4
to
3244fe2
Compare
…ve storage read quota enabled 1. The idea is to block new fast-client traffic that do not have storage node read quota enabled. New client version will fail fast and have a clear error message to direct the user on what's missing. Old client versions will keep failing the metadata request and the user will also see the error message once dig deeper into the error trace.
e6b1a48
to
699081e
Compare
699081e
to
21ff7d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
- Fix tests failures due to [fast-client][server] Throw 403 for metadata request that does not have storage read quota enabled #975 - Extracting the test fixes from [internal][client] Support GRPC port discovery for non-local environment #987 - Reset storage node read quota enabled flag prior to each test in FastClientIndividualFeatureConfigurationTest Co-authored-by: Bharath Kumarasubramanian <bkumarasubramanian@linkedin.com>
…ent (#987) - [Functional] Introduce logic to use fallback Grpc port for netty server address -> Grpc server mapping - [Refactor] Modularize request handling and remove boiler plate in GrpcTransportClient - [Bug fix] Fix integration tests that was failing due to [fast-client][server] Throw 403 for metadata request that does not have storage read quota enabled #975 - [Clean up] Remove some validations, added few invariants check and reorganize some depending on the mode (local vs integration/production) - [Clean up] Rename fields to remove type information - [Test] Add unit tests for GrpcTransportClient class Co-authored-by: Bharath Kumarasubramanian <bkumaras@linkedin.com>
[fast-client][server] Throw 403 for metadata request that does not have storage read quota enabled
How was this PR tested?
Unit test and integration test
Does this PR introduce any user-facing changes?