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

added ":true" to "X-Arango-Allow-Dirty-Read" header (#7277)

This commit is contained in:
Omar_A 2018-11-20 13:08:15 +01:00 committed by Jan
parent 58208d32c4
commit f8eab9b7e1
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/Books/Manual/Administration/ActiveFailover/README.md
View File

@ -46,7 +46,7 @@ Reading from Follower
---------------------
Followers in the active-failover setup are in a read-only mode. It is possible to read from these
followers by adding a `X-Arango-Allow-Dirty-Read` header on each request. Responses will then automatically
followers by adding a `X-Arango-Allow-Dirty-Read: true` header on each request. Responses will then automatically
contain the `X-Arango-Potential-Dirty-Read` header so that clients can reject accidental dirty reads.
Depending on the driver support for your specific programming language, you should be able to enable this option.

4
Documentation/Books/Manual/Architecture/DeploymentModes/ActiveFailover/Architecture.md
View File

@ -52,7 +52,7 @@ In contrast to the normal behaviour of a single-server instance, the Active-Fail
mode will change the behaviour of ArangoDB in some situations.
The _Follower_ will _always_ deny write requests from client applications. Starting from ArangoDB 3.4
read requests are _only_ permitted if the requests is marked with the `X-Arango-Allow-Dirty-Read` header,
read requests are _only_ permitted if the requests is marked with the `X-Arango-Allow-Dirty-Read: true` header,
otherwise they are denied too.
Only the replication itself is allowed to access the follower's data until the
follower becomes a new _Leader_ (should a _failover_ happen).
@ -76,7 +76,7 @@ Reading from Followers
----------------------
Followers in the active-failover setup are in a read-only mode. It is possible to read from these
followers by adding a `X-Arango-Allow-Dirty-Read` header on each request. Responses will then automatically
followers by adding a `X-Arango-Allow-Dirty-Read: true` header on each request. Responses will then automatically
contain the `X-Arango-Potential-Dirty-Read` header so that clients can reject accidental dirty reads.
Depending on the driver support for your specific programming language, you should be able to enable this option.