mirror of https://gitee.com/bigwinds/arangodb
updated documentation
This commit is contained in:
parent
cda5b0df22
commit
d582e6e75a
16
CHANGELOG
16
CHANGELOG
|
@ -49,6 +49,22 @@ edge attribute `label`.
|
|||
* process.stdout.isTTY now returns `true` in arangosh and when running arangod with the `--console` flag
|
||||
|
||||
|
||||
v3.1.6 (2016-12-20)
|
||||
-------------------
|
||||
|
||||
* fixed issue #2227
|
||||
|
||||
* fixed issue #2220
|
||||
|
||||
* agency constituent/agent bug fixes in race conditions picking up
|
||||
leadership
|
||||
|
||||
* supervision does not need waking up anymore as it is running
|
||||
regardless
|
||||
|
||||
* agents challenge their leadership more rigorously
|
||||
|
||||
|
||||
v3.1.5 (2016-12-16)
|
||||
-------------------
|
||||
|
||||
|
|
|
@ -12,6 +12,11 @@ network filesystem such as NFS. The reason is that networked filesystems
|
|||
might cause inconsistencies when there are multiple parallel readers or
|
||||
writers or they lack features required by arangod (e.g. flock()).
|
||||
|
||||
Additionally errors have been reported for some filesystems mounted
|
||||
with mount option NOEXEC. To be on the safe side, ArangoDB's database
|
||||
directory should reside in a filesystem that has not been mounted with
|
||||
the NOEXEC option.
|
||||
|
||||
`directory`
|
||||
|
||||
When using the command line version, you can simply supply the database
|
||||
|
|
Loading…
Reference in New Issue