LoginSign Up
← Back to all sparks
J

JuiceFS

INFRA · APIS
Velocity0.0

Distributed POSIX file system built on object storage

juicefs.com ↗

JuiceFS is spending its v1.4 cycle on metadata-engine efficiency, one transaction at a time.

distributed-filesystemobject-storagemetadata-engineperformancerelease-candidatequota
◆Current state
The v1.4 cycle is running in the open across three pre-releases — beta1 in May with 373 commits since v1.3, beta2 two weeks later, and rc1 in June. The recurring subject is the metadata layer: quota keys no longer create mass tombstones, quota lookups are batched to save a round trip, transactional key-value lookups collapse into a single transaction, and chunks commit in write order. Feature additions are narrow — custom tags in tier configuration, an upload-part stream API, and checkpoint support for multipart uploads in sync.
◆Where it's heading
This is a release cycle about cost at scale rather than new capability. Every metadata change removes a round trip, a tombstone, or a transaction from paths that run constantly, which is where a filesystem backed by object storage and an external metadata engine actually gets expensive. The sync and upload work points the same direction: multipart and streaming paths make large-object transfers resumable instead of restarting them. Contributor counts stay high across releases, so the pace is sustained rather than a push by one maintainer.
◆Prediction
With rc1 cut and the changes since beta2 already down to 50 commits, a v1.4.0 final is the likely next step rather than further feature work.

◆Recent moves

  1. 1mo ago

    v1.4.0-rc1: quota tombstone fix and upload-part stream API

    The cycle narrows to 50 commits and the metadata work continues — quota keys that were never set no longer generate mass tombstones, and quota lookups batch into fewer round trips. The upload-part stream API and custom tier tags are the only real additions, consistent with a branch stabilising toward release.

    View source ↗
  2. 2mo ago

    v1.4.0-beta2: sync checkpoints survive multipart uploads

    Checkpoint support for multipart uploads makes large-object sync resumable rather than restart-from-zero, the most user-visible change in this window. Underneath, the transactional key-value path gets a single-transaction lookup and chunks begin committing in write order.

    View source ↗
  3. 2mo ago

    v1.4.0-beta1 opens the cycle with 373 commits since v1.3

    The v1.4 branch opens carrying 373 commits from 49 contributors accumulated since v1.3 — a large backlog released as one beta rather than a stream of minors. It sets up the metadata and transfer efficiency themes the following pre-releases refine.

    View source ↗