mirror of https://gitee.com/bigwinds/arangodb
4d4135d25c
* add "DBSERVER" as an alias for "PRIMARY"
This allows specifying the value "DBSERVER" for `--cluster.my-role`.
"DBSERVER" is only treated as an alias for "PRIMARY", because several
other parts of the code and APIs use the string "PRIMARY".
Changing these from "PRIMARY" to "DBSERVER" would make the change
downwards-incompatible, which we do not want.
The downside of this alias-only solution is that even when specifying
a role value of "DBSERVER", the server will still report its role as
"PRIMARY", which may be a bit confusing. The server will also generate
its id as "PRMR-XXXX" as before:
2018-08-03T15:23:09Z [9584] INFO {cluster} Starting up with role PRIMARY
2018-08-03T15:23:09Z [9584] INFO {cluster} Cluster feature is turned on. Agency version: {"server":"arango","version":"3.4.devel","license":"enterprise"}, Agency endpoints: http+tcp://[::]:4001, server id: 'PRMR-f655b728-4cea-44ac-88e9-8b34baa80958', internal address: tcp://[::1]:8629, role: PRIMARY
* adjusted documentation to use "DBSERVER" instead of "PRIMARY"
* api doc
- secondary role not used anymore. stated.
- primary database is not clear. replaced with dbserver
- brief referenced only dbserver and coordinator - better to provide wider description, in line with what is described below, as other roles can be returned
* typo
* typo
* added starting from 3.4
* additional warning
* cited in the release note
|
||
|---|---|---|
| .. | ||
| 21.md | ||
| 22.md | ||
| 23.md | ||
| 24.md | ||
| 25.md | ||
| 26.md | ||
| 27.md | ||
| 28.md | ||
| 30.md | ||
| 31.md | ||
| 32.md | ||
| 33.md | ||
| 34.md | ||
| KnownIssues32.md | ||
| NewFeatures21.md | ||
| NewFeatures22.md | ||
| NewFeatures23.md | ||
| NewFeatures24.md | ||
| NewFeatures25.md | ||
| NewFeatures26.md | ||
| NewFeatures27.md | ||
| NewFeatures28.md | ||
| NewFeatures30.md | ||
| NewFeatures31.md | ||
| NewFeatures32.md | ||
| NewFeatures33.md | ||
| NewFeatures34.md | ||
| README.md | ||
| UpgradingChanges23.md | ||
| UpgradingChanges24.md | ||
| UpgradingChanges25.md | ||
| UpgradingChanges26.md | ||
| UpgradingChanges27.md | ||
| UpgradingChanges28.md | ||
| UpgradingChanges30.md | ||
| UpgradingChanges31.md | ||
| UpgradingChanges32.md | ||
| UpgradingChanges33.md | ||
| UpgradingChanges34.md | ||
README.md
Release Notes
What's New
For a high level list of changes, please refer to one of the following sections:
- What's New in 3.x: 3.4, 3.3, 3.2, 3.1, 3.0
- What's New in 2.x: 2.8, 2.7, 2.6, 2.5, 2.4, 2.3, 2.2, 2.1
Changelogs
For a detailed list of changes to the ArangoDB core programs and tools, please refer to the version specific changelogs:
Additional changelogs for tools not included in the main repository:
Incompatible changes
For a list of incompatible changes, please refer to one of the following sections. Also see Version Specific Upgrade Information in the Upgrading chapter.
- Incompatible changes in 3.x: 3.4, 3.3, 3.2, 3.1, 3.0
- Incompatible changes in 2.x: 2.8, 2.7, 2.6, 2.5, 2.4, 2.3
Known Issues
For a list of known issues, please refer to one of the following sections: