You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
How to reproduce this bug?
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
The text was updated successfully, but these errors were encountered: