# Limiting multicast cluster membership

**URL:** <https://discuss.elastic.co/t/limiting-multicast-cluster-membership/11289>\
**Category:** Elasticsearch\
**Created:** [March 25, 2013, 10:08am UTC](https://discuss.elastic.co/t/limiting-multicast-cluster-membership/11289 "2013-03-25T10:08:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabian\_Lange](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fabian_lange/32/1847_2.png) [@Fabian\_Lange](https://discuss.elastic.co/u/Fabian_Lange)\
**Post date:** [March 25, 2013, 10:08am UTC](https://discuss.elastic.co/t/limiting-multicast-cluster-membership/11289/1 "2013-03-25T10:08:58Z")

</div>

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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![q42jaap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/q42jaap/32/2241_2.png) [@q42jaap](https://discuss.elastic.co/u/q42jaap)\
**Post date:** [March 25, 2013, 3:39pm UTC](https://discuss.elastic.co/t/limiting-multicast-cluster-membership/11289/2 "2013-03-25T15:39:03Z")

</div>

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](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](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:44am UTC](https://discuss.elastic.co/t/limiting-multicast-cluster-membership/11289/3 "2017-07-06T02:44:44Z")

</div>

Closed on July 6, 2017, 2:44am UTC


