mirror of https://gitee.com/bigwinds/arangodb
5165155ed1
* do not use V8 variant of AQL functions in early optimization stage when a C++ variant is available * additionally, simplify AQL function definitions and aliases * warn when more than 90% of max mappings are in use * added C++ variant of replication catchup * added `--log.role` option * updated CHANGELOG * removed non-existing scheduler.threads option from config * removed useless __FILE__, __LINE__ invocations * updated CHANGELOG * allow a priority V8 context * remove TRI_CORE_MEM_ZONE * try to fix Windows errors & warnings * cleanup * removed memory zones altogether * exclude system collections from collection tests |
||
|---|---|---|
| .. | ||
| Arangosh | ||
| Auditing | ||
| Configuration | ||
| Encryption | ||
| ManagingUsers | ||
| Replication | ||
| Sharding | ||
| Upgrading | ||
| WebInterface | ||
| Arangodump.md | ||
| Arangoexport.md | ||
| Arangoimp.md | ||
| Arangorestore.md | ||
| 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.