Huntarr updates to v5

A few weeks ago, we announced the addition of Huntarr, a tool to "hunt" missing movies/episodes, to the Aars. In the intervening period, the project has had 2 major version releases and a rebrand, and seems to be finding its footing with a sustained and rapid development pace.

We're rolling out the latest (Huntarr v5.2) in today's glowup, which includes a UI for all configuration activities (no more ENV vars). Without any interaction, huntarr will start "hunting" with some conservative defaults (one missed movie/episode every 15 minutes), so you can just ignore it and let it do its thing.

If, however, you like to tinker (who doesn't?), you'll find that Huntarr's UI forces you to setup user auth before you can see its dashboard. When the planned feature to bypass auth becomes available, we'll opt into this, since our SSO makes it redundant and it just adds friction.

Arr DBs seem stable

The Aarr Postgresql DB migration for our early adopters has been stable and we've seen significant performance improvements reported, especially on larger libraries. Barring any yet-to-be-discovered bugs, we'll roll this migration out to all users in the coming week (not on the weekend!).

If you've got a "plus-sized" Aarr library, the migration can take about an hour, possibly longer if multiple users are migrating at once.

With this in mind, if you care about downtime on your Aars, you'd be smart to trigger the migration at a time which suits you best, rather than waiting for a bulk migration. You can trigger your Aarr DB migrations with ElfBot, by running (for example) "elfbot env radarr USE_POSTGRESQL=true", and (again, if you're particularly geeky) watch the migration progress by looking at the pod logs in Kubernetes Dashboard.

Leave a Reply