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

=doc #15565 improved wording in cluster-usage docs

Browse source
This commit is contained in:
Konrad 'ktoso' Malawski 2014-08-05 14:16:46 +02:00
parent e380c30400
commit 9ae039c2cf
2 changed files with 21 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

22
akka-docs/rst/java/cluster-usage.rst
View file

@ -82,22 +82,22 @@ otherwise it can take up to the configured ``seed-node-timeout`` until the nodes
can join.
Once more than two seed nodes have been started it is no problem to shut down the first
seed node. If the first seed node is restarted it will first try join the other
seed node. If the first seed node is restarted, it will first try to join the other
seed nodes in the existing cluster.
If you don't configure the seed nodes you need to join manually, using :ref:`cluster_jmx_java`
or :ref:`cluster_command_line_java`. You can join to any node in the cluster. It doesn't
have to be configured as a seed node.
If you don't configure seed nodes you need to join the cluster programmatically or manually.
Joining can also be performed programatically with ``Cluster.get(system).join``. Note that
you can only join to an existing cluster member, which means that for bootstrapping some
Manual joining can be performed by using ref:`cluster_jmx_java` or :ref:`cluster_command_line_java`.
Joining programatically can be performed with ``Cluster.get(system).join``.
You can join to any node in the cluster. It does not have to be configured as a seed node.
Note that you can only join to an existing cluster member, which means that for bootstrapping some
node must join itself.
You may also use ``Cluster.get(system).joinSeedNodes``, which is attractive when dynamically
discovering other nodes at startup by using some external tool or API. When using
``joinSeedNodes`` you should not include the node itself except for the node that is
supposed to be the first seed node, and that should be placed first in parameter to
``joinSeedNodes``.
You may also use ``Cluster.get(system).joinSeedNodes`` to join programmatically,
which is attractive when dynamically discovering other nodes at startup by using some external tool or API.
When using ``joinSeedNodes`` you should not include the node itself except for the node that is
supposed to be the first seed node, and that should be placed first in parameter to ``joinSeedNodes``.
Unsuccessful join attempts are automatically retried after the time period defined in
configuration property ``retry-unsuccessful-join-after``. When using ``seed-nodes`` this

19
akka-docs/rst/scala/cluster-usage.rst
View file

@ -76,20 +76,21 @@ otherwise it can take up to the configured ``seed-node-timeout`` until the nodes
can join.
Once more than two seed nodes have been started it is no problem to shut down the first
seed node. If the first seed node is restarted it will first try join the other
seed node. If the first seed node is restarted, it will first try to join the other
seed nodes in the existing cluster.
If you don't configure the seed nodes you need to join manually, using :ref:`cluster_jmx_scala`
or :ref:`cluster_command_line_scala`. You can join to any node in the cluster. It doesn't
have to be configured as a seed node.
If you don't configure seed nodes you need to join the cluster programmatically or manually.
Joining can also be performed programatically with ``Cluster(system).join``. Note that
you can only join to an existing cluster member, which means that for bootstrapping some
Manual joining can be performed by using ref:`cluster_jmx_scala` or :ref:`cluster_command_line_scala`.
Joining programatically can be performed with ``Cluster(system).join``.
You can join to any node in the cluster. It does not have to be configured as a seed node.
Note that you can only join to an existing cluster member, which means that for bootstrapping some
node must join itself.
You may also use ``Cluster(system).joinSeedNodes``, which is attractive when dynamically
discovering other nodes at startup by using some external tool or API. When using
``joinSeedNodes`` you should not include the node itself except for the node that is
You may also use ``Cluster(system).joinSeedNodes`` to join programmatically,
which is attractive when dynamically discovering other nodes at startup by using some external tool or API.
When using ``joinSeedNodes`` you should not include the node itself except for the node that is
supposed to be the first seed node, and that should be placed first in parameter to
``joinSeedNodes``.