Support Atomicity

CubeFS supports atomic operation. After turning on the atomic function, the metadata atomicity of the file operation is met, and the metadata uses the final consistency, that is, the metadata modification of the file operation is ether successfully committed, or rolled back.

Fuse interface supported by atomicity

  • Create
  • Mkdir
  • Remove
  • Rename
  • Mknod
  • Symlink
  • Link


Atomicity supports the Fuse interface, and S3 interface is not supported for now.

atomicity switch

CubeFS implements part of the characteristics of transaction, but it is different from the traditional strict sense of transaction. For the convenience, the operation of files is referred to as transaction.

The transaction is effective in the volume, and a cluster can have multiple volumes. Each volume can switch on or off transaction separately. The client get configuration of transaction from the master when started.

The switch can control all supported interfaces, or only open some interfaces, the default transaction time out is 1 minute.

curl ""


After modifying the parameter of the transaction, new config will be synchronized from Master within 2 minutes.

enableTxMaskStringValue can be: Create, MKDIR, Remove, RENAME, MKNod, Symlink, Link, off, all. off and all and other values are mutually exclusive
txtimeoutuint32the default transaction time out is 1 minute, the maximum 60 minutes
txForceResetboolThe difference from enableTxMask is that value of enableTxMask will be merged, and txForceReset is forced to reset to the specified value
txConflictRetryNumuint32Value range [1-100], defaults to 10
txConflictRetryIntervaluint32Unit: milliseconds, the range of value [10-1000], the default is 20ms

You can check transaction config by getting the volume information

curl ""

You can also specify transaction parameters when creating the volume

curl ""
Edit on GitHub