I'm new to Kibana and Marvel.
I have a problem where Kibana is always Red when i'm bulk indexing documents (i'm using the Bulk JAVA API)
After the indexing, it goes back alive and shows some stats, but no graph history. The cluster is green though when i curl _health the cluster via the REST API.
Any idea how to fix this ? i've already tried to delete the .kibana index and restart my elastic cluster.
Are you indexing into existing indices or are indices automatically created as a result of your indexing? How many indices do you have? What is the size of the cluster? Which version of Elasticsearch are you on?
I'm using Elastic 2.2 and Kibana 4.4 and i'm pulling the latest Marvel plugin (i'm using Docker)
The cluster is Green (when i check the health by /_cluster/health) but form time to time (it is not a constant thing) kibana is red.
I am indexing to existing indices (created manually before bulk indexing) i have 12 indices and the cluster is a basically a three nodes setup with 30 GB of RAM each and 4TB of HDD (NFS)
What i noticed is that when the cluster is idle or does not do too much of indexing, Marvel becomes live and shows some activity (no history though on indexing/activity graphs) but when i'm bulk indexing Kibana goes Red most of the time and Marvel neither Sense are available.
I've tried to delete the .marvel* indices
Thanks for your replies.
I added the line index.merge.scheduler.max_thread_count: 1 to my yml files
I'll try now to do bulk import and see how it goes.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.