# Elastic error from Kibana

**URL:** <https://discuss.elastic.co/t/elastic-error-from-kibana/118990>\
**Category:** Elasticsearch\
**Created:** [February 8, 2018, 7:59am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990 "2018-02-08T07:59:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![javiertec10](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@javiertec10](https://discuss.elastic.co/u/javiertec10)\
**Post date:** [February 8, 2018, 7:59am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990/1 "2018-02-08T07:59:11Z")

</div>

Hi dear team!

I have a problem in Kibana but, the error it seems that is about Elastic:

 ![imagen](https://us1.discourse-cdn.com/elastic/original/3X/e/e/ee5e02d22f8bbe7a8618c13d3634e37774c8a184.png)

If run curl -XGET '[http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)' I see this:

![imagen](https://us1.discourse-cdn.com/elastic/original/3X/5/6/56f194c7037b0447fc16c2b9bd9a021e9f1e2aa7.png)

Could you help me please?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 8, 2018, 8:11am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990/2 "2018-02-08T08:11:08Z")

</div>

That's a lot of shards for a single node.  
Why do you allocate so much? Using default settings?

May I suggest you look at the following resources about sizing:

[https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)

> **[How many shards should I have in my Elasticsearch cluster?
	  	 | Elastic](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**
>
> Elasticsearch is a very versatile platform, that supports a variety of use cases, and provides great flexibility around data organisation and replication strategies. This flexibility can however somet...

> **[NetSecureDay: Managing your Black Friday Logs](https://speakerdeck.com/elastic/netsecureday-managing-your-black-friday-logs)**
>
> Surveiller une application complexe n’est pas une tâche aisée, mais avec les bons outils, ce n’est pas si sorcier. Néanmoins, des périodes fortes telles que les opérations de type « Black Friday » (Vendredi noir) ou période de Noël peuvent pousser...

---

<div class="post-metadata">

**Author:** ![javiertec10](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@javiertec10](https://discuss.elastic.co/u/javiertec10)\
**Post date:** [February 8, 2018, 9:35am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990/3 "2018-02-08T09:35:10Z")

</div>

Hi David!

Thanks for your quick reply. The problem I have is that is not my installation... Probably it was installed by default settings and now, when we are going to use dashboards with more thant 30 days I see this type of errors...

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 8, 2018, 9:47am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990/4 "2018-02-08T09:47:37Z")

</div>

You probably better to reindex your data or add more nodes.

---

<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:** [March 8, 2018, 9:47am UTC](https://discuss.elastic.co/t/elastic-error-from-kibana/118990/5 "2018-03-08T09:47:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.