Kibanna is very slow and UI stcuk

[shahid]

Hi Team,
My kibana UI is responding very slow and some time stuck while searching . its setup on Dockers containers.
1 - Container - ElasticSearch
2 - Container LogStach
3 - Container Kibana

I check the logs of Elasticserach docker container on my Host server and i fould the below warnings.

is that can be the issue of slowness and stuck my Kibana

docker logs dockerelk_elasticsearch_1

[2018-10-30T10:25:54,480][WARN ][o.e.b.BootstrapChecks ] [vHE4RKF] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

[2018-10-30T10:48:21,871][WARN ][o.e.d.s.f.s.DocValueFieldsFetchSubPhase] Doc-value field [@timestamp] is not using a format. The output will change in 7.0 when doc value fields get formatted based on mappings by default. It is recommended to pass [format=use_field_mapping] with the doc value field in order to opt in for the future behaviour and ease the migration to 7.0.

[Christian_Dahlqvist]

How much data do you have in your cluster? How many indices and shards? What is the specification of the host where the stack is running? What kind of storage are you using?

[shahid]

@Christian_Dahlqvist, PFA!

Please find below my Host details on which container is setup for ELK (single node server).

OS Ubuntu 18.xx LTE
EC2 Instance Tyep: t2.medium
VCPU: 2
RAM: 4 GB
HDD: 150 GB

1 - How can i check the size of data on my ELk server ?
2 - How can I check how many indices and shards ?

Thanks

[Christian_Dahlqvist]

@shahid

t2.medium

t2 instance types have very limited burstable CPU, so are not ideal. I would recommend switching to a small m4/m5 instance types instead, which has constant CPU and is likely to give much better performance.

[shahid]

so the error on the screen short is due to the resource bottleneck ?
because while setup the beats on client site i am getting this error of time as well.

2018-11-05T11:42:57.681Z ERROR instance/beat.go:743 Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing directory /usr/share/metricbeat/kibana: Failed to import dashboard: Failed to load directory /usr/share/metricbeat/kibana/6/dashboard:
error loading /usr/share/metricbeat/kibana/6/dashboard/Metricbeat-apache-overview.json: returned 400 to import file: . Response: {"statusCode":400,"error":"Bad Request","message":"Request Timeout after 30000ms"}

[Christian_Dahlqvist]

I have seen users having problems with t2 instances when just running Elasticsearch on them. You are trying to also run Kibana and Logstash, which can be CPU intensive, so I am not surprised you are seeing timeouts. Check any monitoring data you have and see how CPU usage/credits look like over time, and I suspect you will see what the bottleneck is.

[shahid]

@Christian_Dahlqvist.
Thanks for the immediate response.
here is exact stats i got from the server.

buntu@ip-xx.x.x.xx:~$ curl -XGET 'ElasticServerIP:9200/_cat/allocation?v&pretty'

shards disk.indices disk.used disk.avail disk.total disk.percent host ip node
42 4.6gb 11.5gb 85.2gb 96.8gb 11 172.x.x.xx vHE4dbKF
41 UNASSIGNED

[Christian_Dahlqvist]

Did you try another instance type? Did it work better?

[shahid]

@Christian_Dahlqvist no i did,nt try other type yet. its lilt better now . after doing some memory tweaking on Host and container on ES.