-
Notifications
You must be signed in to change notification settings - Fork 10
Fix separate object store race condition #294
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
Conversation
Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>
Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>
|
will you align logging with the new approach using LOG? |
I aligned it now in the services and would open another PR to align it in the remaining files |
KoblerS
left a comment
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.
I did not included all suggestions for all object store provider implementations of the createClient function but I think you'll get the point
When using MTX + separate Object Store mode there is a chance for a race condition because the Object store bucket is stored as a property on the service which is however shared across all tenants.
The PR addresses this by introducing getBucket / getClient methods and within these the tenant-specific cache lookup is performed / a new client is created.