=doc #15565 improved wording in cluster-usage docs

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

View file

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

View file

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