# Limit to number of Nodes?

**URL:** <https://discuss.elastic.co/t/limit-to-number-of-nodes/51344>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [May 30, 2016, 6:30pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344 "2016-05-30T18:30:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 30, 2016, 6:30pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/1 "2016-05-30T18:30:48Z")

</div>

Is there a limit to the number of nodes displayed in the free version of Marvel?

Right now I have 12 data nodes, all showing up, but I have 12 logstash nodes as well with ES client nodes running on them. When I view Marvel I only see a few of the logstash nodes. The configs are identical because I copied them from one node to all others. I know the nodes are there because:  
curl 10.1.55.2:/\_cat\_nodes | grep INDEXER  
10.1.55.6 10.1.55.6 4 9 0.78 - - INDEXER\_NODE\_4  
10.1.55.27 10.1.55.27 1 9 0.88 - - INDEXER\_NODE\_9  
10.1.55.30 10.1.55.30 0 9 0.59 - - INDEXER\_NODE\_12  
10.1.55.25 10.1.55.25 1 9 0.56 - - INDEXER\_NODE\_7  
10.1.55.26 10.1.55.26 2 9 0.35 - - INDEXER\_NODE\_8  
10.1.55.24 10.1.55.24 3 9 0.81 - - INDEXER\_NODE\_6  
10.1.55.28 10.1.55.28 2 9 0.48 - - INDEXER\_NODE\_10  
10.1.55.4 10.1.55.4 0 9 0.68 - - INDEXER\_NODE\_2  
10.1.55.23 10.1.55.23 3 9 0.29 - - INDEXER\_NODE\_5  
10.1.55.29 10.1.55.29 1 9 0.31 - - INDEXER\_NODE\_11  
10.1.55.5 10.1.55.5 3 9 0.66 - - INDEXER\_NODE\_3

This shows all the indexer nodes I have running right now. (I know node 1 is not listed it is currently offline.)

Marvel shows

 ![](https://us1.discourse-cdn.com/elastic/original/2X/f/fb2db30c07c70632db7e84171864c4047a2b333e.PNG)

Why would all of the nodes be listed when running the curl command but not show up in Marvel.

I have confirmed I am running the same version of elasticsearch, logstash, and marvel-agent on all nodes  
ES 2.3.1  
LS 2.3.1  
Marvel-Agent 2.3.1  
License 2.3.1

Thanks  
Tim

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [May 31, 2016, 5:14pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/2 "2016-05-31T17:14:51Z")

</div>

Hi Tim,

I have not seen this issue and there's no realistic limit that is set.

On the cluster being monitored, can you run:

```auto
$ curl -XGET host:9200/_cat/plugins?v

```

This will show what nodes believe to be installed as opposed to what's on the file system. It should list 12 data nodes, 12 client nodes (your "indexers"), and presumably 3 master nodes. Each one should show `marvel-agent` installed for the same version.

Let me know.

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [June 1, 2016, 11:23pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/3 "2016-06-01T23:23:50Z")

</div>

> [@pickypg](#):
>
> curl -XGET host:9200/\_cat/plugins?v

```auto
name component version type url
KIBANA_SEARCH_BALANCER_1 license 2.3.3 j
KIBANA_SEARCH_BALANCER_1 marvel-agent 2.3.3 j
MASTER_NODE_1 license 2.3.1 j
MASTER_NODE_1 marvel-agent 2.3.1 j
INDEXER_NODE_5 license 2.3.1 j
INDEXER_NODE_5 marvel-agent 2.3.1 j
INDEXER_NODE_8 license 2.3.1 j
INDEXER_NODE_8 marvel-agent 2.3.1 j
WORKER_NODE_12 license 2.3.1 j
WORKER_NODE_12 marvel-agent 2.3.1 j
WORKER_NODE_7 license 2.3.1 j
WORKER_NODE_7 marvel-agent 2.3.1 j
WORKER_NODE_10 license 2.3.1 j
WORKER_NODE_10 marvel-agent 2.3.1 j
KIBANA_SEARCH_BALANCER_2 license 2.3.3 j
KIBANA_SEARCH_BALANCER_2 marvel-agent 2.3.3 j
WORKER_NODE_5 license 2.3.1 j
WORKER_NODE_5 marvel-agent 2.3.1 j
WORKER_NODE_6 license 2.3.1 j
WORKER_NODE_6 marvel-agent 2.3.1 j
PB2ES_NODE_1 license 2.3.3 j
PB2ES_NODE_1 marvel-agent 2.3.3 j
INDEXER_NODE_6 license 2.3.1 j
INDEXER_NODE_6 marvel-agent 2.3.1 j
INDEXER_NODE_3 license 2.3.1 j
INDEXER_NODE_3 marvel-agent 2.3.1 j
WORKER_NODE_9 license 2.3.1 j
WORKER_NODE_9 marvel-agent 2.3.1 j
WORKER_NODE_11 license 2.3.1 j
WORKER_NODE_11 marvel-agent 2.3.1 j
WORKER_NODE_1 license 2.3.1 j
WORKER_NODE_1 marvel-agent 2.3.1 j
WORKER_NODE_8 license 2.3.1 j
WORKER_NODE_8 marvel-agent 2.3.1 j
MASTER_NODE_3 license 2.3.1 j
MASTER_NODE_3 marvel-agent 2.3.1 j
INDEXER_NODE_10 license 2.3.1 j
INDEXER_NODE_10 marvel-agent 2.3.1 j
INDEXER_NODE_12 license 2.3.1 j
INDEXER_NODE_12 marvel-agent 2.3.1 j
INDEXER_NODE_11 license 2.3.1 j
INDEXER_NODE_11 marvel-agent 2.3.1 j
WORKER_NODE_2 license 2.3.1 j
WORKER_NODE_2 marvel-agent 2.3.1 j
MASTER_NODE_2 license 2.3.1 j
MASTER_NODE_2 marvel-agent 2.3.1 j
WORKER_NODE_4 license 2.3.1 j
WORKER_NODE_4 marvel-agent 2.3.1 j
INDEXER_NODE_4 license 2.3.1 j
INDEXER_NODE_4 marvel-agent 2.3.1 j
INDEXER_NODE_9 license 2.3.1 j
INDEXER_NODE_9 marvel-agent 2.3.1 j
INDEXER_NODE_2 license 2.3.1 j
INDEXER_NODE_2 marvel-agent 2.3.1 j
WORKER_NODE_3 license 2.3.1 j
WORKER_NODE_3 marvel-agent 2.3.1 j
INDEXER_NODE_7 license 2.3.1 j
INDEXER_NODE_7 marvel-agent 2.3.1 j
PB2ES_NODE_2 license 2.3.3 j
PB2ES_NODE_2 marvel-agent 2.3.3 j

```

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [June 1, 2016, 11:32pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/4 "2016-06-01T23:32:09Z")

</div>

It certainly looks like it's installed everywhere, but it's noteworthy that some nodes are running slightly different versions.

Now that we have that plugin output, can we correlate that with the nodes info stored in your index?

```auto
$ curl -XGET "host:9200/.marvel-es-data-1?pretty&size=50" -o data-file.json

```

Then just attach the output either here or as a [gist](http://gist.github.com) (posting it as a gist makes it easier for you to delete later).

At the same time, can you also add any configuration settings that you are applying to one of the nodes that is missing _and_ one of the same types that is _not_ missing?

Thanks

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [June 2, 2016, 1:36pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/5 "2016-06-02T13:36:06Z")

</div>

So I'm not sure what happened but after 2 days of not seeing some of the nodes in marvel now I am seeing all of them. Its strange. I made no configuration changes at all.

I'm going to chalk it up to having to wait for some reason.

Thanks for the help. I am still happy to provide the requested info if it will help you troubleshoot this issue. But I am considering it resolved.

Thanks again

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [June 2, 2016, 7:29pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/6 "2016-06-02T19:29:19Z")

</div>

I appreciate the offer, but since it's all appearing I think it's too late to see what was failing.

I'm glad that it kicked in!

Thanks,  
Chris

---

<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:43pm UTC](https://discuss.elastic.co/t/limit-to-number-of-nodes/51344/7 "2017-07-06T13:43:16Z")

</div>


