Hi Jochen, Always both ElasticSearch nodes are using 900 MB of 2GB RAM... but I will try it with 4GB if it is necessary.
Thanks ;) El viernes, 3 de febrero de 2017, 10:07:57 (UTC+1), Jochen Schalanda escribió: > > Hi Aitor, > > as I already mentioned, your ES cluster doesn't have enough hardware > resources to keep up with the data ingestion from Graylog. Assign at least > 4 GiB of memory for each Elasticsearch node. > > Cheers, > Jochen > > On Friday, 3 February 2017 08:05:27 UTC+1, Aitor Mendoza wrote: >> >> Hello Jochen, >> >> But the problem of disk space is from yesterday because a vmware >> datastore problem that is already solved. But I want to solve the alert "NO >> MASTER fixed" that appears till the first day... >> >> Thanks >> >> El jueves, 2 de febrero de 2017, 15:22:58 (UTC+1), Jochen Schalanda >> escribió: >>> >>> Hi Aitor, >>> >>> these logs clearly show that your Elasticsearch cluster is not healthy: >>> It ran out of disk space multiple times and it can't keep up with indexing >>> messages sent by Graylog (full task queues etc.). >>> >>> You'll have to provide more hardware (esp. more memory, at least 4 GiB) >>> to your Elasticsearch nodes. >>> >>> Cheers, >>> Jochen >>> >> -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/23e6f301-fcfa-4031-bd5f-c4b052bd9db1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
