Hi team,
We have ~1000 production databases, and we had periodic syncs with the DB metadata to allow our users to have query interfaces other than SQL (for example, models or other means of exploring)
After the update to the latest version, v0.51.3.3, we've discovered that the MB tries to sync many databases at the start, which blocks the start until it eventually timeouts.
We're happy with the period sync, which happens outside of the startup, but we don't understand how to set it up. At the moment to mitigate the issue, our DBs are defined with metabase_sync_scheduler, and cache_field_values_schedulers are set to some inadequate date 0 11 11 11 11 2200
Is there a way we can change the sync behaviour so as not to run on the startup?