# Unicast discovery options?

**URL:** <https://discuss.elastic.co/t/unicast-discovery-options/6812>\
**Category:** Elasticsearch\
**Created:** [February 26, 2012, 4:54pm UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812 "2012-02-26T16:54:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![project2501](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@project2501](https://discuss.elastic.co/u/project2501)\
**Post date:** [February 26, 2012, 4:54pm UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812/1 "2012-02-26T16:54:18Z")

</div>

Hi,  
I've hunted through the guides and group but can't seem to get  
unicast discovery to work.

I run ES on one server with no options.

On a second server I run:  
bin/elasticsearch -Ddiscovery.zen.ping.unicast.enabled=true -  
Ddiscovery.zen.ping.unicast.hosts=["192.168.0.7"]

Is this right?  
I get various results. Sometimes exception in the master log.  
Sometimes nothing at all.

thanks!

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 26, 2012, 7:52pm UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812/2 "2012-02-26T19:52:27Z")

</div>

You need to prefix the settings if provided using -D using es, for example, -Des.discovery.zen.ping…. . I don't know where you found the unicast.enabled flag in the docs… . Here are the settings to configure unicast: [https://github.com/elasticsearch/elasticsearch/blob/master/config/elasticsearch.yml#L313](https://github.com/elasticsearch/elasticsearch/blob/master/config/elasticsearch.yml#L313).

On Sunday, February 26, 2012 at 6:54 PM, project2501 wrote:

> Hi,  
> I've hunted through the guides and group but can't seem to get  
> unicast discovery to work.
> 
> I run ES on one server with no options.
> 
> On a second server I run:  
> bin/elasticsearch -Ddiscovery.zen.ping.unicast.enabled=true -  
> Ddiscovery.zen.ping.unicast.hosts=["192.168.0.7"]
> 
> Is this right?  
> I get various results. Sometimes exception in the master log.  
> Sometimes nothing at all.
> 
> thanks!

---

<div class="post-metadata">

**Author:** ![project2501](https://avatars.discourse-cdn.com/v4/letter/p/41988e/32.png) [@project2501](https://discuss.elastic.co/u/project2501)\
**Post date:** [February 26, 2012, 8:10pm UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812/3 "2012-02-26T20:10:18Z")

</div>

Thanks for the quick reply Shay. It works now.

Oh, I guess I 'made up' the unicast.enabled property. Probably deduced  
it. Silly me.

On Feb 26, 2:52 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> You need to prefix the settings if provided using -D using es, for example, -Des.discovery.zen.ping…. . I don't know where you found the unicast.enabled flag in the docs… . Here are the settings to configure unicast:[https://github.com/elasticsearch/elasticsearch/blob/master/config/ela](https://github.com/elasticsearch/elasticsearch/blob/master/config/ela)....
> 
> On Sunday, February 26, 2012 at 6:54 PM, project2501 wrote:
> 
> > Hi,  
> > I've hunted through the guides and group but can't seem to get  
> > unicast discovery to work.
> 
> > I run ES on one server with no options.
> 
> > On a second server I run:  
> > bin/elasticsearch -Ddiscovery.zen.ping.unicast.enabled=true -  
> > Ddiscovery.zen.ping.unicast.hosts=["192.168.0.7"]
> 
> > Is this right?  
> > I get various results. Sometimes exception in the master log.  
> > Sometimes nothing at all.
> 
> > thanks!

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 26, 2012, 8:42pm UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812/4 "2012-02-26T20:42:07Z")

</div>

Cool 🙂

On Sunday, February 26, 2012 at 10:10 PM, project2501 wrote:

> Thanks for the quick reply Shay. It works now.
> 
> Oh, I guess I 'made up' the unicast.enabled property. Probably deduced  
> it. Silly me.
> 
> On Feb 26, 2:52 pm, Shay Banon \<[kim...@gmail.com](mailto:kim...@gmail.com) ([http://gmail.com](http://gmail.com))\> wrote:
> 
> > You need to prefix the settings if provided using -D using es, for example, -Des.discovery.zen.ping…. . I don't know where you found the unicast.enabled flag in the docs… . Here are the settings to configure unicast:[https://github.com/elasticsearch/elasticsearch/blob/master/config/ela](https://github.com/elasticsearch/elasticsearch/blob/master/config/ela)....
> > 
> > On Sunday, February 26, 2012 at 6:54 PM, project2501 wrote:
> > 
> > > Hi,  
> > > I've hunted through the guides and group but can't seem to get  
> > > unicast discovery to work.
> > 
> > > I run ES on one server with no options.
> > 
> > > On a second server I run:  
> > > bin/elasticsearch -Ddiscovery.zen.ping.unicast.enabled=true -  
> > > Ddiscovery.zen.ping.unicast.hosts=["192.168.0.7"]
> > 
> > > Is this right?  
> > > I get various results. Sometimes exception in the master log.  
> > > Sometimes nothing at all.
> > 
> > > thanks!

---

<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, 3:38am UTC](https://discuss.elastic.co/t/unicast-discovery-options/6812/5 "2017-07-06T03:38:10Z")

</div>


