Skip to content

Arkindex 1.8.2

A new Arkindex release is available.

To upgrade a development instance, follow this documentation.

To upgrade a production instance, you need to:

  • Deploy this release’s Docker image: registry.gitlab.teklia.com/arkindex/backend:1.8.2
  • Run the database migrations: docker exec ark-backend arkindex migrate
  • Update the system workers: docker exec ark-backend arkindex update_system_workers

The release notes for Arkindex 1.8.2 are available here.

The main changes impacting developers and system administrators are detailed below.

Removal of worker versions from worker results

The removal of worker versions, started in the previous release, is now complete. The database migrations in this release will remove the old data from the database. The arkindex generate_missing_worker_runs command is no longer available.

On large or old Arkindex instances with many worker results that had a worker version but no worker run, we recommend migrating to Arkindex 1.8.1 first. Skipping from 1.8.0 or earlier to 1.8.2 directly may require a significant downtime or prevent workers from creating any worker results until the database migration is complete, while version 1.8.1 will provide the arkindex generate_missing_worker_runs command which enables a smooth transition.

Multiple database indexes have been updated. If you see any drops in performance after the migrations, run an ANALYZE command on the PostgreSQL database to let it learn about those indexes and use them properly.

New IIIF job queue

A new iiif queue has been added in our RQ worker setup. You may need to update your deployments to add this queue to the arkindex rqworker or arkindex rqworker-pool commands, or to add new workers.

This new queue allows for a new asynchronous validation of IIIF images, which can improve performance on large imports. The CreateIIIFURL API endpoint will use an asynchronous validation, instead of the regular synchronous one, under the following conditions:

This mode is only meant for advanced cases where imports are using images from trusted IIIF servers and closely monitored. This is not used by any import within Arkindex itself.

This change does not affect developers, as our development setup has been updated to include this queue in the local RQ worker.