We are dropping Metabase into our test environment and have noticed a few things…

install guides all say “give Metabase user All privs” this is not good, though working our way through we’ve realised that the privs it needs means it should run against a slave replica, not a writeable DB…

once we got the right privs assigned, it became stuck on migration…
03-08 00:12:03 INFO metabase.db :: Database has unrun migrations. Waiting for migration lock to be cleared…
03-08 00:12:05 WARN metabase.util :: auto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__20186@6c83c686: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.