Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

renamed parameter in Documentation after change in code

This commit is contained in:
Jan Steemann 2016-04-22 13:47:44 +02:00
parent 07d1eeb68d
commit 4ed6fdc872
5 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/Books/Users/ConfigureArango/README.mdpp
View File

@ -32,8 +32,8 @@ version of the application
Prints the version of the server and exits.
!SUBSECTION Upgrade
`--upgrade`
!SUBSECTION Database Upgrade
`--database.upgrade`
Specifying this option will make the server perform a database upgrade at start. A database upgrade will first compare the version number stored in the file VERSION in the database directory with the current server version.

6
Documentation/Books/Users/FirstSteps/GettingFamiliar.mdpp
View File

@ -37,7 +37,7 @@ If there is no such process, check the log file
like
2012-12-03T11:35:29Z [12882] ERROR Database directory version (1) is lower than server version (1.2).
2012-12-03T11:35:29Z [12882] ERROR It seems like you have upgraded the ArangoDB binary. If this is what you wanted to do, please restart with the --upgrade option to upgrade the data in the database directory.
2012-12-03T11:35:29Z [12882] FATAL Database version check failed. Please start the server with the --upgrade option
2012-12-03T11:35:29Z [12882] ERROR It seems like you have upgraded the ArangoDB binary. If this is what you wanted to do, please restart with the --database.upgrade option to upgrade the data in the database directory.
2012-12-03T11:35:29Z [12882] FATAL Database version check failed. Please start the server with the --database.upgrade option
make sure to start the server once with the *--upgrade* option.
make sure to start the server once with the *--database.upgrade* option.

2
Documentation/Books/Users/Installing/Compiling.mdpp
View File

@ -288,5 +288,5 @@ system, e. g. `/etc` and `/var/lib`.
When upgrading from a previous version of ArangoDB, please make sure you inspect
ArangoDB's log file after an upgrade. It may also be necessary to start ArangoDB
with the *--upgrade* parameter once to perform required upgrade or
with the *--database.upgrade* parameter once to perform required upgrade or
initialization tasks.

2
Documentation/Books/Users/Installing/Upgrading.mdpp
View File

@ -8,7 +8,7 @@ To upgrade an existing ArangoDB database to a newer version of ArangoDB
* Check the *CHANGELOG* and the [list of incompatible changes](../Upgrading/UpgradingChanges28.md) for API or other changes in the new version of ArangoDB and make sure your applications can deal with them
* Stop the "old" arangod service or binary
* Copy the entire "old" data directory to a safe place (that is, a backup)
* Install the new version of ArangoDB and start the server with the *--upgrade* option once. This might write to the logfile of ArangoDB, so you may want to check the logs for any issues before going on.
* Install the new version of ArangoDB and start the server with the *--database.upgrade* option once. This might write to the logfile of ArangoDB, so you may want to check the logs for any issues before going on.
* Start the "new" arangod service or binary regularly and check the logs for any issues. When you're confident everything went well, you may want to check the database directory for any files with the ending *.old*. These files are created by ArangoDB during upgrades and can be safely removed manually later.
If anything goes wrong during or shortly after the upgrade:

2
Documentation/Books/Users/Installing/Windows.mdpp
View File

@ -109,7 +109,7 @@ database, and vice versa.
To upgrade an EXISTING database created with a previous version of ArangoDB,
please execute the server *arangod.exe* with the option
*--upgrade*. Otherwise starting ArangoDB may fail with errors.
*--database.upgrade*. Otherwise starting ArangoDB may fail with errors.
Note that there is no harm in running the upgrade. So you should run this
batch file if you are unsure of the database version you are using.