History

Wilfried Goesgens b5c018cebe fix proc filesystem URL as pointed out by @ThomasWeiss; fixes #3002		2017-08-22 16:53:17 +02:00
..
Arangosh	rename .mdpp files to .md so the handling is easier.	2017-05-04 12:04:24 +02:00
Auditing	Docs: Moved Auditing and StorageEngines to appropriate categories, added highlights	2017-07-05 10:24:14 +02:00
Configuration	fix proc filesystem URL as pointed out by @ThomasWeiss; fixes #3002	2017-08-22 16:53:17 +02:00
Encryption	Added docs about encryption feature (#2500 )	2017-06-08 08:52:17 +02:00
ManagingUsers	Fix cases where the root user has access to excluded collections (#2856 )	2017-08-03 21:16:08 +02:00
Replication	fix typo	2017-08-07 07:13:05 +02:00
Sharding	rename .mdpp files to .md so the handling is easier.	2017-05-04 12:04:24 +02:00
Upgrading	updated documentation	2017-05-30 13:00:51 +02:00
WebInterface	Docs: Rework ManagingUsers	2017-07-20 05:06:53 +02:00
Arangodump.md	cluster documentation varnish (#2553 )	2017-06-12 19:02:11 +02:00
Arangoexport.md	Feature/planning 580 arangoexport with query (#2882 )	2017-07-28 08:41:53 +02:00
Arangoimp.md	updated threads documentation	2017-05-30 10:49:36 +02:00
Arangorestore.md	cluster documentation varnish (#2553 )	2017-06-12 19:02:11 +02:00
Durability.md	rename .mdpp files to .md so the handling is easier.	2017-05-04 12:04:24 +02:00
README.md	updated documentation	2017-05-30 13:00:51 +02:00

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.