Skip to main content

Fusion v2.6.12

Fusion v2.6.12 improves Spot reclamation handling in NFS service mode, adds Fusion errors to .command.log, and fixes S3 work directories whose role cannot tag objects.

How to pin this version​

fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.12-amd64.json'
}
info

For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.12-arm64.json'.

Feature updates and improvements​

NFS service mode​

  • Added early upload of task work directories when a Spot reclamation notice arrives. The fusion-nfs image turns it on with FUSION_NFS_RECLAIM_EARLY_FLUSH=true.
  • Changed the fusion-nfs image to run a new implementation of Fusion's file metadata layer.

General​

  • Added Fusion errors to the task's .command.log, so they appear in the Seqera Platform execution log.

Metrics​

  • Added the fusion_cache_refaults_total, fusion_cache_refaults_bytes_total, fusion_chunk_prefetch_wasted_total, and fusion_chunk_prefetch_wasted_bytes_total counters for cache thrashing. See The cache is thrashing.

AWS​

  • Changed the S3 anonymous-access warning to include why credentials could not be retrieved.

Bug fixes​

NFS service mode​

  • Fixed a failed NFS mount falling back to a regular mount. Fusion now exits with 173, or 172 for a malformed FUSION_NFS_SOURCE. See Exit codes 172 and 173.
  • Fixed tasks relaunched on the same host failing with exit code 174.
  • Fixed cleanup of a large previous attempt timing out and failing the task with exit code 173.

Fusion Snapshots​

  • Fixed snapshot restores in NFS service mode failing with exit code 175 or 177. Checkpoints are now uploaded while the task runs.
  • Fixed tasks that finished during a Spot reclamation notice being relaunched and failing with exit code 175. Requires fusion-snapshot 1.10.0.

AWS​

  • Fixed S3 work directories failing to mount with exit code 174 when the role lacks s3:PutObjectTagging.
  • Fixed Nextflow command files (.command.run, .command.sh, .command.stage, and .command.in) losing their FUSION_TAGS tags.

Dependencies​

  • Updated CI, build pipeline, and dependencies.

Upgrade notes​

  • Drop-in replacement for v2.6.11. No configuration changes required.
  • FUSION_NFS_RECLAIM_EARLY_FLUSH has no effect outside the fusion-nfs image.
  • S3 lifecycle rules filtered on nextflow.io/metadata=true match .command.run and .command.sh again.