1
0
Fork 0
arangodb/Documentation/Books/Manual/Administration/Durability.mdpp

77 lines
2.0 KiB
Plaintext

!CHAPTER Durability Configuration
!SECTION Global Configuration
There are global configuration values for durability, which can be adjusted by
specifying the following configuration options:
@startDocuBlock databaseWaitForSync
@startDocuBlock databaseForceSyncProperties
@startDocuBlock WalLogfileSyncInterval
!SECTION Per-collection configuration
You can also configure the durability behavior on a per-collection basis.
Use the ArangoDB shell to change these properties.
@startDocuBlock collectionProperties
!SECTION Per-operation configuration
Many data-modification operations and also ArangoDB's transactions allow to specify
a *waitForSync* attribute, which when set ensures the operation data has been
synchronized to disk when the operation returns.
!SECTION Disk-Usage Configuration
The amount of disk space used by ArangoDB is determined by a few configuration
options.
!SECTION Global Configuration
The total amount of disk storage required by ArangoDB is determined by the size of
the write-ahead logfiles plus the sizes of the collection journals and datafiles.
There are the following options for configuring the number and sizes of the write-ahead
logfiles:
<!-- arangod/Wal/LogfileManager.h -->
@startDocuBlock WalLogfileReserveLogfiles
<!-- arangod/Wal/LogfileManager.h -->
@startDocuBlock WalLogfileHistoricLogfiles
<!-- arangod/Wal/LogfileManager.h -->
@startDocuBlock WalLogfileSize
<!-- arangod/Wal/LogfileManager.h -->
@startDocuBlock WalLogfileAllowOversizeEntries
<!-- arangod/Wal/LogfileManager.h -->
@startDocuBlock WalLogfileSuppressShapeInformation
When data gets copied from the write-ahead logfiles into the journals or datafiles
of collections, files will be created on the collection level. How big these files
are is determined by the following global configuration value:
<!-- arangod/RestServer/ArangoServer.h -->
@startDocuBlock databaseMaximalJournalSize
!SECTION Per-collection configuration
The journal size can also be adjusted on a per-collection level using the collection's
*properties* method.