History

jsteemann 72420495c1 fixed documentation issue #5325		2018-05-11 14:47:42 +02:00
..
Arangosh	Doc - added documentation for ArangoShell `print` function (#4397 )	2018-01-23 13:56:30 +00:00
Auditing	…
Configuration	fixed documentation issue #5325	2018-05-11 14:47:42 +02:00
Encryption	added encryption key generator (#3348 )	2017-09-30 14:59:27 +02:00
ManagingUsers	Refactor Authentication Layer (3.3) (#4588 )	2018-02-28 13:24:18 +01:00
Replication	Active Failover for Foxx Services (3.3) (#4593 )	2018-02-15 09:36:25 +01:00
Sharding	…
Upgrading	3.3 release notes (#4107 )	2017-12-20 15:33:09 +01:00
WebInterface	…
Arangodump.md	some more release notes (#4145 )	2017-12-22 11:23:45 +01:00
Arangoexport.md	Feature/planning 580 arangoexport with query (#2882 )	2017-07-28 08:41:53 +02:00
Arangoimp.md	add `--ignore-missing` option to arangoimp (#4128 )	2017-12-22 11:09:03 +01:00
Arangorestore.md	issue #3504 : export database name with dump for easier restore (#4215 )	2018-01-15 22:47:03 +01:00
Durability.md	…
README.md	…

README.md

Administration

Most administration can be managed using the arangosh.

Filesystems

As one would expect for a database, we recommend a locally mounted filesystems.

NFS or similar network filesystems will not work.

On Linux we recommend the use of ext4fs, on Windows NTFS and on MacOS HFS+.

We recommend to not use BTRFS on Linux. It is known to not work well in conjunction with ArangoDB. We experienced that ArangoDB faces latency issues on accessing its database files on BTRFS partitions. In conjunction with BTRFS and AUFS we also saw data loss on restart.