We currently use a Heroku buildpack for deploying Metabase. To fix it: you can either clear the lock using the built-in release-locks command line function, or if needed you can login to your Metabase application database directly and delete the row in the DATABASECHANGELOGLOCK table. This can happen if for some reason Heroku kills your Metabase dyno at the wrong time during startup. The most likely culprit here is a stale database migrations lock that was not cleared.If your Metabase instance is getting stuck part way through the initialization process and only every shows roughly 30% completion on the loading progress.Now that you’ve installed Metabase, it’s time to set it up and connect it to your database. If this happens regularly we recommend upgrading to the standard-2x tier dyno. Sometimes Metabase may run out of memory and you will see messages like Error R14 (Memory quota exceeded) in the Heroku logs.You can resolve this by upgrading to the hobby tier or higher. This prevents things like Pulses and Metabase background tasks from running when scheduled and at times makes the app appear to be slow when really it’s just Heroku reloading your app. When using the free tier, if you don’t access the application for a while Heroku will sleep your Metabase environment.Most people don’t run into this but be aware that it’s possible. Heroku’s 30 second timeouts on all web requests can cause a few issues if you happen to have longer running database queries.You’ll also get better overall performance along with backups, which we think is worth it. The primary reason for this upgrade is to get more than the minimum number of database rows offered in the free tier (10k), which we’ve had some users exhaust within a week. Upgrade your Postgres database to the Basic package or for more peace of mind go for the Standard 0 package. The most important reason for this is that your dyno will never sleep and that allows Metabase to run all of its background work such as sending Pulses, syncing metadata, etc, in a reliable fashion. Upgrade your dyno to the Hobby tier or one of the professional Standard 1x/2x dynos. If you like what you see and decide to use Metabase as an ongoing part of your analytics workflow we recommend these upgrades which are quite affordable and will allow you to fully utilize all of Metabase’s capabilities without running into annoying limitations. Heroku is very kind and offers a free tier to be used for very small/non-critical workloads which is great if you just want to evaluate Metabase and see what it looks like. You can check on the progress by viewing the logs at or using the Heroku command line tool with the heroku logs -t -a YOUR_APPLICATION_NAME command. It should only take a few minutes for Metabase to start. This will launch a Heroku deployment using a GitHub repository that Metabase maintains. If you’ve got a Heroku account then all there is to do is follow this one-click deployment button If you’re up for it then give it a shot and let us know how we can make it better! Launching Metabaseīefore doing anything you should make sure you have a Heroku account that you can access. We’ve run Metabase on Heroku and it works just fine, but it’s not hardened for production use just yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |