Skip to content

Conversation

@schiwekM
Copy link
Contributor

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.

@schiwekM schiwekM requested a review from a team as a code owner November 10, 2025 07:37
@schiwekM schiwekM requested a review from stefanrudi November 10, 2025 07:37
schiwekM and others added 3 commits November 12, 2025 15:17
Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>
Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>
@KoblerS
Copy link
Collaborator

KoblerS commented Nov 13, 2025

will you align logging with the new approach using LOG?

@schiwekM
Copy link
Contributor Author

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

Copy link
Collaborator

@KoblerS KoblerS left a 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

@schiwekM schiwekM closed this Nov 13, 2025
@schiwekM schiwekM deleted the fix/seperate-object-store-race-condition branch November 13, 2025 16:06
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.

3 participants