Skip to content

Latest commit

 

History

History
128 lines (100 loc) · 4.69 KB

datastores.md

File metadata and controls

128 lines (100 loc) · 4.69 KB
Raw

Datastore Configuration Options

This document describes the different possible values for the Datastore.Spec field in the ipfs configuration file.

flatfs

Stores each key value pair as a file on the filesystem.

The shardFunc is prefixed with /repo/flatfs/shard/v1 then followed by a descriptor of the sharding strategy. Some example values are:

  • /repo/flatfs/shard/v1/next-to-last/2
    • Shards on the two next to last characters of the key
  • /repo/flatfs/shard/v1/prefix/2
    • Shards based on the two character prefix of the key
{
	"type": "flatfs",
	"path": "<relative path within repo for flatfs root>",
	"shardFunc": "<a descriptor of the sharding scheme>",
	"sync": true|false
}

NOTE: flatfs must only be used as a block store (mounted at /blocks) as it only partially implements the datastore interface. You can mount flatfs for /blocks only using the mount datastore (described below).

levelds

Uses a leveldb database to store key value pairs.

{
	"type": "levelds",
	"path": "<location of db inside repo>",
	"compression": "none" | "snappy",
}

pebbleds

Uses pebble as a key value store.

{
	"type": "pebbleds",
	"path": "<location of pebble inside repo>",
}

The following options are availble for tuning pebble. If they are not configured (or assigned their zero-valued), then default values are used.

  • bytesPerSync: int, Sync sstables periodically in order to smooth out writes to disk. (default: 512KB)
  • bisableWAL: true|false, Disable the write-ahead log (WAL) at expense of prohibiting crash recovery. (default: false)
  • cacheSize: Size of pebble's shared block cache. (default: 8MB)
  • l0CompactionThreshold: int, Count of L0 files necessary to trigger an L0 compaction.
  • l0StopWritesThreshold: int, Limit on L0 read-amplification, computed as the number of L0 sublevels.
  • lBaseMaxBytes: int, Maximum number of bytes for LBase. The base level is the level which L0 is compacted into.
  • maxConcurrentCompactions: int, Maximum number of concurrent compactions. (default: 1)
  • memTableSize: int, Size of a MemTable in steady state. The actual MemTable size starts at min(256KB, MemTableSize) and doubles for each subsequent MemTable up to MemTableSize (default: 4MB)
  • memTableStopWritesThreshold: int, Limit on the number of queued of MemTables. (default: 2)
  • walBytesPerSync: int: Sets the number of bytes to write to a WAL before calling Sync on it in the background. (default: 0, no background syncing)
  • walMinSyncSeconds: int: Sets the minimum duration between syncs of the WAL. (default: 0)

Tip

Start using pebble with only default values and configure tuning items are needed for your needs. For a more complete description of these values, see: https://pkg.go.dev/github.com/cockroachdb/[email protected]#Options (where A.B.C is pebble version from Kubo's go.mod).

badgerds

Uses badger as a key value store.

Caution

This is based on very old badger 1.x, which has known bugs and is no longer supported by the upstream team. It is provided here only for pre-existing users, allowing them to migrate away to more modern datastore. Do not use it for new deployments, unless you really, really know what you are doing.

  • syncWrites: Flush every write to disk before continuing. Setting this to false is safe as kubo will automatically flush writes to disk before and after performing critical operations like pinning. However, you can set this to true to be extra-safe (at the cost of a 2-3x slowdown when adding files).
  • truncate: Truncate the DB if a partially written sector is found (defaults to true). There is no good reason to set this to false unless you want to manually recover partially written (and unpinned) blocks if kubo crashes half-way through adding a file.
{
	"type": "badgerds",
	"path": "<location of badger inside repo>",
	"syncWrites": true|false,
	"truncate": true|false,
}

mount

Allows specified datastores to handle keys prefixed with a given path. The mountpoints are added as keys within the child datastore definitions.

{
	"type": "mount",
	"mounts": [
		{
			// Insert other datastore definition here, but add the following key:
			"mountpoint": "/path/to/handle"
		},
		{
			// Insert other datastore definition here, but add the following key:
			"mountpoint": "/path/to/handle"
		},
	]
}

measure

This datastore is a wrapper that adds metrics tracking to any datastore.

{
	"type": "measure",
	"prefix": "sometag.datastore",
	"child": { datastore being wrapped }
}