raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

Clarified the failure conditions for Read/WriteLocal

Browse source
This commit is contained in:
James Roper 2019-03-19 14:59:31 +11:00
parent 3ef7bf5ef5
commit 71084b4c96
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
akka-docs/src/main/paradox/distributed-data.md
View file

@ -212,6 +212,10 @@ from other nodes might not be visible yet.
When using @scala[`WriteLocal`]@java[`writeLocal`] the update is only written to the local replica and then disseminated When using @scala[`WriteLocal`]@java[`writeLocal`] the update is only written to the local replica and then disseminated
in the background with the gossip protocol, which can take few seconds to spread to all nodes. in the background with the gossip protocol, which can take few seconds to spread to all nodes.
When using `ReadLocal`, you will never receive a `GetFailure` response, since the local replica is always available to
local readers. `WriteLocal` however may still reply with `UpdateFailure` messages, in the event that the `modify` function
threw an exception, or, if using durable storage, if storing failed.
`WriteAll` and `ReadAll` is the strongest consistency level, but also the slowest and with `WriteAll` and `ReadAll` is the strongest consistency level, but also the slowest and with
lowest availability. For example, it is enough that one node is unavailable for a `Get` request lowest availability. For example, it is enough that one node is unavailable for a `Get` request
and you will not receive the value. and you will not receive the value.