Skip to content
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

High MTTR with many tenants #4634

Open
1 task done
etiennedi opened this issue Apr 9, 2024 · 1 comment
Open
1 task done

High MTTR with many tenants #4634

etiennedi opened this issue Apr 9, 2024 · 1 comment
Labels

Comments

@etiennedi
Copy link
Member

How to reproduce this bug?

  • Have many tenants, 100s of thousands
  • Restart node

What is the expected behavior?

Startup time should be more or less instant (with lazy shard loading)

What is the actual behavior?

We see one write operation per tenant that slows down restarting. It took about 8 minutes on a clsuter with between 100k-200k tenants

Supporting information

No response

Server Version

1.24.x

Code of Conduct

@etiennedi etiennedi added the bug label Apr 9, 2024
@etiennedi
Copy link
Member Author

My guess is that the motivation behind the many writes is that we write back the schema after startup in case there was a migration. Could probably be optimized by checking if anything was actually changed. If not, don't store the schema back.

Possible Steps to reproduce:

  • Import 200k tenants, they need to be cold otherwise you run out of file descriptors on a single node
  • restart server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant