# Marvel config for 3 nodes on the same machine (dev)

**URL:** https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471
**Category:** Elasticsearch
**Created:** [August 26, 2014, 7:44pm UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471 "2014-08-26T19:44:58Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Tommy\_Bollhofer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tommy_bollhofer/32/45762_2.png) [@Tommy\_Bollhofer](https://discuss.elastic.co/u/Tommy_Bollhofer)
#### Post date: [August 26, 2014, 7:44pm UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471/1 "2014-08-26T19:44:58Z")

</div>

I have 3 nodes running on my local machine for development purposes (9200,  
9201, 9202) with the marvel plugin installed on all 3. Cluster and Node  
data doesn't seem to be reporting correctly so I'm suspecting I have  
something dorked up (head is reporting everything OK).

elasticsearch.yml config:

cluster.name : elasticsearch  
marvel.agent.exporter.es.hosts:  
["localhost:9200","localhost:9201","localhost:9202"]

node1 (/node1/data):  
transport.tcp.port: 9300  
http.port: 9200

node2 (/node2/data):  
transport.tcp.port: 9301  
http.port: 9201

node3 (/node3/data):  
transport.tcp.port: 9302  
http.port: 9202

Any ideas?  
Thanks -

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5d5a3c70-89ea-4fd0-abe3-658f7af19f1d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5d5a3c70-89ea-4fd0-abe3-658f7af19f1d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)
#### Post date: [August 28, 2014, 8:42pm UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471/2 "2014-08-28T20:42:40Z")

</div>

That _should_ work as far as I can tell. Anything in the logs from the  
marvel.agent? you can enable debug logging for the marvel.agent log if need  
be...

Boaz

On Tuesday, August 26, 2014 9:44:58 PM UTC+2, Tommy Bollhofer wrote:

> I have 3 nodes running on my local machine for development purposes (9200,  
> 9201, 9202) with the marvel plugin installed on all 3. Cluster and Node  
> data doesn't seem to be reporting correctly so I'm suspecting I have  
> something dorked up (head is reporting everything OK).
> 
> elasticsearch.yml config:
> 
> cluster.name : elasticsearch  
> marvel.agent.exporter.es.hosts:  
> ["localhost:9200","localhost:9201","localhost:9202"]
> 
> node1 (/node1/data):  
> transport.tcp.port: 9300  
> http.port: 9200
> 
> node2 (/node2/data):  
> transport.tcp.port: 9301  
> http.port: 9201
> 
> node3 (/node3/data):  
> transport.tcp.port: 9302  
> http.port: 9202
> 
> Any ideas?  
> Thanks -

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/64138724-b425-4abd-92a8-73d2a0cc7c0c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/64138724-b425-4abd-92a8-73d2a0cc7c0c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Tommy\_Bollhofer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tommy_bollhofer/32/45762_2.png) [@Tommy\_Bollhofer](https://discuss.elastic.co/u/Tommy_Bollhofer)
#### Post date: [August 29, 2014, 3:57am UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471/3 "2014-08-29T03:57:17Z")

</div>

Thanks for the reply Boaz. Enabled debug logging for marvel....haven't come  
across anything suspect just yet. All of the data for the indices in marvel  
report just fine. It's just the cluster and node data; presumably because  
all 3 nodes are on the same host....

[2014-08-28 23:49:14,860][INFO][node] [the Living  
Darkness Null] version[1.3.1], pid[13752],  
build[2de6dc5/2014-07-28T14:45:15Z]  
[2014-08-28 23:49:14,860][INFO][node] [the Living  
Darkness Null] initializing ...  
[2014-08-28 23:49:14,931][INFO][plugins] [the Living  
Darkness Null] loaded [transport-couchbase, marvel, jdbc-1.3.0.0-c49372f],  
sites [marvel, head]  
[2014-08-28 23:49:17,485][DEBUG][marvel.agent.exporter] [the Living  
Darkness Null] initialized with targets: [localhost:9200], index prefix  
[.marvel], index time format [YYYY.MM.dd]  
[2014-08-28 23:49:17,757][DEBUG][marvel.agent.exporter] [the Living  
Darkness Null] initialized with targets: [localhost:9200], index prefix  
[.marvel], index time format [YYYY.MM.dd]  
[2014-08-28 23:49:17,757][DEBUG][marvel.agent.exporter] [the Living  
Darkness Null] initialized with targets: [localhost:9200], index prefix  
[.marvel], index time format [YYYY.MM.dd]  
[2014-08-28 23:49:17,768][INFO][node] [the Living  
Darkness Null] initialized  
[2014-08-28 23:49:17,768][INFO][node] [the Living  
Darkness Null] starting ...  
[2014-08-28 23:49:18,349][INFO][org.eclipse.jetty.server.Server]  
jetty-8.1.0.v20120127  
[2014-08-28 23:49:18,457][INFO  
][org.eclipse.jetty.server.AbstractConnector] Started  
SelectChannelConnector@0.0.0.0:9091  
[2014-08-28 23:49:18,457][INFO][transport.couchbase] [the Living  
Darkness Null] bound\_address {inet[0.0.0.0/0.0.0.0:9091]}, publish\_address  
{inet[/192.168.0.40:9091]}  
[2014-08-28 23:49:18,695][INFO][transport] [the Living  
Darkness Null] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address  
{inet[/192.168.0.40:9300]}  
[2014-08-28 23:49:19,149][INFO][discovery] [the Living  
Darkness Null] vp-es-dba/GKZAEAe-RZGSmvrQzzLYvw  
[2014-08-28 23:49:22,162][INFO][cluster.service] [the Living  
Darkness Null] new\_master [the Living Darkness  
Null][GKZAEAe-RZGSmvrQzzLYvw][laptop][inet[/192.168.0.40:9300]], reason:  
zen-disco-join (elected\_as\_master)  
[2014-08-28 23:49:22,596][DEBUG][action.search.type] [the Living  
Darkness Null] All shards failed for phase: [query\_fetch]  
[2014-08-28 23:49:22,812][INFO][http] [the Living  
Darkness Null] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address  
{inet[/192.168.0.40:9200]}  
[2014-08-28 23:49:22,813][INFO][node] [the Living  
Darkness Null] started  
[2014-08-28 23:49:23,431][INFO][gateway] [the Living  
Darkness Null] recovered [28] indices into cluster\_state  
[2014-08-28 23:49:27,750][INFO][cluster.service] [the Living  
Darkness Null] added {[Gin  
Genie][ju46OWj-QLiJDdTd5G\_Vrw][laptop][inet[/192.168.0.40:9301]],}, reason:  
zen-disco-receive(join from node[[Gin  
Genie][ju46OWj-QLiJDdTd5G\_Vrw][laptop][inet[/192.168.0.40:9301]]])  
[2014-08-28 23:49:28,185][DEBUG][marvel.agent.exporter] [the Living  
Darkness Null] accepting existing index template (version [5], needed [5])  
[2014-08-28 23:49:47,481][INFO][cluster.service] [the Living  
Darkness Null] added {[Dum-Dum  
Dugan][1svv\_mTcTQmIuJAnR\_Ldtg][laptop][inet[/192.168.0.40:9302]],}, reason:  
zen-disco-receive(join from node[[Dum-Dum  
Dugan][1svv\_mTcTQmIuJAnR\_Ldtg][laptop][inet[/192.168.0.40:9302]]])

> 

On Thursday, August 28, 2014 4:42:41 PM UTC-4, Boaz Leskes wrote:

> That _should_ work as far as I can tell. Anything in the logs from the  
> marvel.agent? you can enable debug logging for the marvel.agent log if need  
> be...
> 
> Boaz
> 
> On Tuesday, August 26, 2014 9:44:58 PM UTC+2, Tommy Bollhofer wrote:
> 
> > I have 3 nodes running on my local machine for development purposes  
> > (9200, 9201, 9202) with the marvel plugin installed on all 3. Cluster and  
> > Node data doesn't seem to be reporting correctly so I'm suspecting I have  
> > something dorked up (head is reporting everything OK).
> > 
> > elasticsearch.yml config:
> > 
> > cluster.name : elasticsearch  
> > marvel.agent.exporter.es.hosts:  
> > ["localhost:9200","localhost:9201","localhost:9202"]
> > 
> > node1 (/node1/data):  
> > transport.tcp.port: 9300  
> > http.port: 9200
> > 
> > node2 (/node2/data):  
> > transport.tcp.port: 9301  
> > http.port: 9201
> > 
> > node3 (/node3/data):  
> > transport.tcp.port: 9302  
> > http.port: 9202
> > 
> > Any ideas?  
> > Thanks -

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/30518e32-3b9f-4df2-8ee5-30abc0cc49d5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/30518e32-3b9f-4df2-8ee5-30abc0cc49d5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)
#### Post date: [August 30, 2014, 6:13pm UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471/4 "2014-08-30T18:13:42Z")

</div>

That's looks good to me, assuming localhost:9200 resolves to the ip ES is  
bound to (try curl localhost:9200 to verify). What problems are you seeing  
exactly?

On Friday, August 29, 2014 5:57:17 AM UTC+2, Tommy Bollhofer wrote:

> Thanks for the reply Boaz. Enabled debug logging for marvel....haven't  
> come across anything suspect just yet. All of the data for the indices in  
> marvel report just fine. It's just the cluster and node data; presumably  
> because all 3 nodes are on the same host....
> 
> [2014-08-28 23:49:14,860][INFO][node] [the Living  
> Darkness Null] version[1.3.1], pid[13752],  
> build[2de6dc5/2014-07-28T14:45:15Z]  
> [2014-08-28 23:49:14,860][INFO][node] [the Living  
> Darkness Null] initializing ...  
> [2014-08-28 23:49:14,931][INFO][plugins] [the Living  
> Darkness Null] loaded [transport-couchbase, marvel, jdbc-1.3.0.0-c49372f],  
> sites [marvel, head]  
> [2014-08-28 23:49:17,485][DEBUG][marvel.agent.exporter] [the Living  
> Darkness Null] initialized with targets: [localhost:9200], index prefix  
> [.marvel], index time format [YYYY.MM.dd]  
> [2014-08-28 23:49:17,757][DEBUG][marvel.agent.exporter] [the Living  
> Darkness Null] initialized with targets: [localhost:9200], index prefix  
> [.marvel], index time format [YYYY.MM.dd]  
> [2014-08-28 23:49:17,757][DEBUG][marvel.agent.exporter] [the Living  
> Darkness Null] initialized with targets: [localhost:9200], index prefix  
> [.marvel], index time format [YYYY.MM.dd]  
> [2014-08-28 23:49:17,768][INFO][node] [the Living  
> Darkness Null] initialized  
> [2014-08-28 23:49:17,768][INFO][node] [the Living  
> Darkness Null] starting ...  
> [2014-08-28 23:49:18,349][INFO][org.eclipse.jetty.server.Server]  
> jetty-8.1.0.v20120127  
> [2014-08-28 23:49:18,457][INFO  
> ][org.eclipse.jetty.server.AbstractConnector] Started  
> SelectChannelConnector@0.0.0.0:9091  
> [2014-08-28 23:49:18,457][INFO][transport.couchbase] [the Living  
> Darkness Null] bound\_address {inet[0.0.0.0/0.0.0.0:9091]  
> [http://www.google.com/url?q=http%3A%2F%2F0.0.0.0%2F0.0.0.0%3A9091%255D&sa=D&sntz=1&usg=AFQjCNGOqgz4jpZ4bOi4J9KHvlZjj3-Q3A](http://www.google.com/url?q=http%3A%2F%2F0.0.0.0%2F0.0.0.0%3A9091%255D&sa=D&sntz=1&usg=AFQjCNGOqgz4jpZ4bOi4J9KHvlZjj3-Q3A)},  
> publish\_address {inet[/192.168.0.40:9091]}  
> [2014-08-28 23:49:18,695][INFO][transport] [the Living  
> Darkness Null] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address  
> {inet[/192.168.0.40:9300]}  
> [2014-08-28 23:49:19,149][INFO][discovery] [the Living  
> Darkness Null] vp-es-dba/GKZAEAe-RZGSmvrQzzLYvw  
> [2014-08-28 23:49:22,162][INFO][cluster.service] [the Living  
> Darkness Null] new\_master [the Living Darkness  
> Null][GKZAEAe-RZGSmvrQzzLYvw][laptop][inet[/192.168.0.40:9300]], reason:  
> zen-disco-join (elected\_as\_master)  
> [2014-08-28 23:49:22,596][DEBUG][action.search.type] [the Living  
> Darkness Null] All shards failed for phase: [query\_fetch]  
> [2014-08-28 23:49:22,812][INFO][http] [the Living  
> Darkness Null] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address  
> {inet[/192.168.0.40:9200]}  
> [2014-08-28 23:49:22,813][INFO][node] [the Living  
> Darkness Null] started  
> [2014-08-28 23:49:23,431][INFO][gateway] [the Living  
> Darkness Null] recovered [28] indices into cluster\_state  
> [2014-08-28 23:49:27,750][INFO][cluster.service] [the Living  
> Darkness Null] added {[Gin  
> Genie][ju46OWj-QLiJDdTd5G\_Vrw][laptop][inet[/192.168.0.40:9301]],}, reason:  
> zen-disco-receive(join from node[[Gin  
> Genie][ju46OWj-QLiJDdTd5G\_Vrw][laptop][inet[/192.168.0.40:9301]]])  
> [2014-08-28 23:49:28,185][DEBUG][marvel.agent.exporter] [the Living  
> Darkness Null] accepting existing index template (version [5], needed [5])  
> [2014-08-28 23:49:47,481][INFO][cluster.service] [the Living  
> Darkness Null] added {[Dum-Dum  
> Dugan][1svv\_mTcTQmIuJAnR\_Ldtg][laptop][inet[/192.168.0.40:9302]],}, reason:  
> zen-disco-receive(join from node[[Dum-Dum  
> Dugan][1svv\_mTcTQmIuJAnR\_Ldtg][laptop][inet[/192.168.0.40:9302]]])
> 
> > 
> 
> On Thursday, August 28, 2014 4:42:41 PM UTC-4, Boaz Leskes wrote:
> 
> > That _should_ work as far as I can tell. Anything in the logs from the  
> > marvel.agent? you can enable debug logging for the marvel.agent log if need  
> > be...
> > 
> > Boaz
> > 
> > On Tuesday, August 26, 2014 9:44:58 PM UTC+2, Tommy Bollhofer wrote:
> > 
> > > I have 3 nodes running on my local machine for development purposes  
> > > (9200, 9201, 9202) with the marvel plugin installed on all 3. Cluster and  
> > > Node data doesn't seem to be reporting correctly so I'm suspecting I have  
> > > something dorked up (head is reporting everything OK).
> > > 
> > > elasticsearch.yml config:
> > > 
> > > cluster.name : elasticsearch  
> > > marvel.agent.exporter.es.hosts:  
> > > ["localhost:9200","localhost:9201","localhost:9202"]
> > > 
> > > node1 (/node1/data):  
> > > transport.tcp.port: 9300  
> > > http.port: 9200
> > > 
> > > node2 (/node2/data):  
> > > transport.tcp.port: 9301  
> > > http.port: 9201
> > > 
> > > node3 (/node3/data):  
> > > transport.tcp.port: 9302  
> > > http.port: 9202
> > > 
> > > Any ideas?  
> > > Thanks -

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fd4f9cac-f32d-4feb-bc14-91345fdb2dc8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fd4f9cac-f32d-4feb-bc14-91345fdb2dc8%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:05am UTC](https://discuss.elastic.co/t/marvel-config-for-3-nodes-on-the-same-machine-dev/19471/5 "2017-07-06T01:05:21Z")

</div>


