Limiting multicast cluster membership

Hi,
just wanted to check the best practice for limiting membership of nodes in
a cluster running multicast discovery.

Is it expected to configure this by configuring the underlying network
layer to restrict multicast across networks, or can I configure the Zen
Discovery to accept only nodes from certain subnets.

Fabian

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Did you consider changing the clustername in the configuration? Or is
it a security feature you're looking for?
Jaap Taal

[ Q42 BV | tel 070 44523 42 | direct 070 44523 65 | http://q42.nl |
Waldorpstraat 17F, Den Haag | Vijzelstraat 72 unit 4.23, Amsterdam |
KvK 30164662 ]

On Mon, Mar 25, 2013 at 11:08 AM, Fabian Lange
fabian.lange@codecentric.de wrote:

Hi,
just wanted to check the best practice for limiting membership of nodes in a
cluster running multicast discovery.

Is it expected to configure this by configuring the underlying network layer
to restrict multicast across networks, or can I configure the Zen Discovery
to accept only nodes from certain subnets.

Fabian

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.