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

Merge pull request #21503 from jgordijn/wip-fix-typo-in-dd-doc

Browse source 
doc - Change WeaklyUp is used in DD #21502
This commit is contained in:
Patrik Nordwall 2016-09-30 14:25:44 +02:00 • committed by GitHub
commit 13974c7358
2 changed files with 13 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

8
akka-docs/rst/java/distributed-data.rst
View file

@ -41,8 +41,12 @@ with a specific role. It communicates with other ``Replicator`` instances with t
``akka.cluster.ddata.DistributedData`` extension. ``akka.cluster.ddata.DistributedData`` extension.
Cluster members with status :ref:`WeaklyUp <weakly_up_java>`, if that feature is enabled, Cluster members with status :ref:`WeaklyUp <weakly_up_java>`, if that feature is enabled,
will currently not participate in Distributed Data, but that is something that should be possible to will participate in Distributed Data. This means that the data will be replicated to the
add in a future release. :ref:`WeaklyUp <weakly_up_java>` nodes with the background gossip protocol. Note that it
will not participate in any actions where the consistency mode is to read/write from all
nodes or the majority of nodes. The :ref:`WeaklyUp <weakly_up_java>` node is not counted
as part of the cluster. So 3 nodes + 5 :ref:`WeaklyUp <weakly_up_java>` is essentially a
3 node cluster as far as consistent actions are concerned.
Below is an example of an actor that schedules tick messages to itself and for each tick Below is an example of an actor that schedules tick messages to itself and for each tick
adds or removes elements from a ``ORSet`` (observed-remove set). It also subscribes to adds or removes elements from a ``ORSet`` (observed-remove set). It also subscribes to

10
akka-docs/rst/scala/distributed-data.rst
View file

@ -41,8 +41,12 @@ with a specific role. It communicates with other ``Replicator`` instances with t
``akka.cluster.ddata.DistributedData`` extension. ``akka.cluster.ddata.DistributedData`` extension.
Cluster members with status :ref:`WeaklyUp <weakly_up_scala>`, if that feature is enabled, Cluster members with status :ref:`WeaklyUp <weakly_up_scala>`, if that feature is enabled,
will currently not participate in Distributed Data, but that is something that should be possible to will participate in Distributed Data. This means that the data will be replicated to the
add in a future release. :ref:`WeaklyUp <weakly_up_scala>` nodes with the background gossip protocol. Note that it
will not participate in any actions where the consistency mode is to read/write from all
nodes or the majority of nodes. The :ref:`WeaklyUp <weakly_up_scala>` node is not counted
as part of the cluster. So 3 nodes + 5 :ref:`WeaklyUp <weakly_up_scala>` is essentially a
3 node cluster as far as consistent actions are concerned.
Below is an example of an actor that schedules tick messages to itself and for each tick Below is an example of an actor that schedules tick messages to itself and for each tick
adds or removes elements from a ``ORSet`` (observed-remove set). It also subscribes to adds or removes elements from a ``ORSet`` (observed-remove set). It also subscribes to
@ -526,4 +530,4 @@ Configuration
The ``DistributedData`` extension can be configured with the following properties: The ``DistributedData`` extension can be configured with the following properties:
.. includecode:: ../../../akka-distributed-data/src/main/resources/reference.conf#distributed-data .. includecode:: ../../../akka-distributed-data/src/main/resources/reference.conf#distributed-data