Kibana is not working, properly, it is very slow

Elastic Stack Elasticsearch
1

kibana is not working, properly, it is very slow
Is there any cache stored, which makes it slow?

2

If Kibana is slow it is generally due to Elasticsearch being slow. What is the specification of your cluster and hardware? How much data do you have? How many indices and shards?

3

How can i check my specification of cluster and hardware in aws elastic search?

Can i check data i have using kibana?

Can i check indices and shards using kibana?

So please suggest

4

I do not use AWS Elasticsearch so am not sure how to check the specification of the cluster you are using. For the other questions I would usually refer to monitoring, but that is as far as I know not available on AWS Elasticsearch. You can however go into the dev console in Kibana and run the _cat/indices and _cluster/stats APIs.

I would however recommend finding out which instance type you are using and the volume and type of storage you have.

5

Please give me the suggestions, below is the queries data

GET /_cluster/stats

{
"_nodes" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"cluster_name" : "xxxxxxxxxxx",
"cluster_uuid" : "xxxxxxxxxxx",
"timestamp" : 1593155810010,
"status" : "green",
"indices" : {
"count" : 7,
"shards" : {
"total" : 62,
"primaries" : 31,
"replication" : 1.0,
"index" : {
"shards" : {
"min" : 2,
"max" : 10,
"avg" : 8.857142857142858
},
"primaries" : {
"min" : 1,
"max" : 5,
"avg" : 4.428571428571429
},
"replication" : {
"min" : 1.0,
"max" : 1.0,
"avg" : 1.0
}
}
},
"docs" : {
"count" : 11313786,
"deleted" : 2
},
"store" : {
"size_in_bytes" : 18596243276
},
"fielddata" : {
"memory_size_in_bytes" : 0,
"evictions" : 0
},
"query_cache" : {
"memory_size_in_bytes" : 35853207,
"total_count" : 1295334,
"hit_count" : 16789,
"miss_count" : 1278545,
"cache_size" : 2196,
"cache_count" : 2196,
"evictions" : 0
},
"completion" : {
"size_in_bytes" : 0
},
"segments" : {
"count" : 368,
"memory_in_bytes" : 11276831,
"terms_memory_in_bytes" : 5450711,
"stored_fields_memory_in_bytes" : 5200480,
"term_vectors_memory_in_bytes" : 0,
"norms_memory_in_bytes" : 342144,
"points_memory_in_bytes" : 0,
"doc_values_memory_in_bytes" : 283496,
"index_writer_memory_in_bytes" : 0,
"version_map_memory_in_bytes" : 0,
"fixed_bit_set_memory_in_bytes" : 576,
"max_unsafe_auto_id_timestamp" : -1,
"file_sizes" : { }
}
},
"nodes" : {
"count" : {
"total" : 2,
"coordinating_only" : 0,
"data" : 2,
"ingest" : 2,
"master" : 2
},
"versions" : [ "7.4.2" ],
"os" : {
"available_processors" : 8,
"allocated_processors" : 8,
"names" : [ {
"count" : 2
} ],
"pretty_names" : [ {
"count" : 2
} ],
"mem" : {
"total_in_bytes" : 32677732352,
"free_in_bytes" : 324190208,
"used_in_bytes" : 32353542144,
"free_percent" : 1,
"used_percent" : 99
}
},
"process" : {
"cpu" : {
"percent" : 2
},
"open_file_descriptors" : {
"min" : 1694,
"max" : 1998,
"avg" : 1846
}
},
"jvm" : {
"max_uptime_in_millis" : 1641082084,
"mem" : {
"heap_used_in_bytes" : 5325132304,
"heap_max_in_bytes" : 17110138880
},
"threads" : 335
},
"fs" : {
"total_in_bytes" : 73445474304,
"free_in_bytes" : 54740013056,
"available_in_bytes" : 50948362240
},
"network_types" : {
"transport_types" : {
"netty4" : 2
},
"http_types" : {
"filter-jetty" : 2
}
},
"discovery_types" : {
"zen" : 2
},
"packaging_types" : [ {
"flavor" : "oss",
"type" : "tar",
"count" : 2
} ]
}
}

GET /_cat/indices

green open xxxxxxxxxxx 1JO3dJILTiSmToQgjNkqtw 5 1 0 0 2.7kb 1.3kb
green open xxxxxxxxxxx b_JpU62sRKiz6_Qq-DCIag 5 1 11249078 0 17.2gb 8.6gb
green open xxxxxxxxxxx lHCWVc-DRr2OX2RhYgw7PQ 5 1 62857 0 95.7mb 47.8mb
green open .opendistro-anomaly-detectors smz--7WiQuChawHreNKs7A 5 1 1 0 16.7kb 8.3kb
green open .kibana_1 fPBwACvLRJWbnE-CV4OtPg 1 1 12 2 88.1kb 41kb
green open xxxxxxxxxxx DZKF2-vhSNmL1bZI6cBegw 5 1 0 0 2.7kb 1.3kb
green open xxxxxxxxxxx 7mfDkdXURVancS5n_4Nf2g 5 1 1838 0 2.4mb 1.2mb

6

I see nothing odd there. I think we need to know what instance types and storage this cluster is running on.

7

how can i check instance types and storage this cluster is running on?

8

Check with whoever set up the cluster or AWS support.

It would also be useful to see if there are any errors or warnings in the logs, but I am not sure whether or how logs are accessible on AWS Elasticsearch.

9

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

image
image764×92 16.4 KB

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.

10

BTW did you look at https://www.elastic.co/cloud and https://aws.amazon.com/marketplace/pp/B01N6YCISK ?

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, APM, Logs UI, Infra UI, SIEM, Maps UI, AppSearch and what is coming next :slight_smile: ...

1 Like
11

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