-Clusters:
- uuid_prefix:
- Volumes:
- uuid_prefix-nyw5e-000000000000000:
+ Volumes:
+ ClusterID-nyw5e-000000000000000:
AccessViaHosts:
- "http://keep0.uuid_prefix.example.com:25107": {}
- Driver: Directory
+ "http://keep0.ClusterID.example.com:25107": {}
+ Driver: Directory
DriverParameters:
# The directory that will be used as the backing store.
- Root: /mnt/local-disk
-
- # When true, read and write operations (for whole 64MiB
- # blocks) on an individual volume will queued and issued
- # serially. When false, read and write operations will be
- # issued concurrently.
- #
- # May improve throughput if you experience contention when
- # there are multiple requests to the same volume.
- #
- # When using SSDs, RAID, or a shared network filesystem, you
- # probably don't want this.
- Serialize: false
+ Root: /mnt/local-disk
# How much replication is performed by the underlying
# filesystem. (for example, a network filesystem may provide
@@ -53,28 +39,34 @@ Note that each volume has an AccessViaHosts section indicating that (for example
# reads.
ReadOnly: false
- # Storage classes to associate with this volume. See "Storage
- # classes" in the "Admin" section of doc.arvados.org.
+ # Storage classes to associate with this volume.
StorageClasses: null
- uuid_prefix-nyw5e-000000000000001:
+ ClusterID-nyw5e-000000000000001:
AccessViaHosts:
- "http://keep1.uuid_prefix.example.com:25107": {}
- Driver: Directory
+ "http://keep1.ClusterID.example.com:25107": {}
+ Driver: Directory
DriverParameters:
- Root: /mnt/local-disk
+ Root: /mnt/local-disk
-In the case of a network-attached filesystem accessible by all keepstore servers, the AccessViaHosts section is omitted.
+In the case of a network-attached filesystem, the @AccessViaHosts@ section can have multiple entries. If the filesystem is accessible by all keepstore servers, the AccessViaHosts section can be empty, or omitted entirely. In this example, the underlying storage system performs replication, so specifying @Replication: 2@ means a block is considered to be stored twice for the purposes of data integrity, while only stored on a single volume from the perspective of Keep.