Kibana 8.12 Error

Elastic Stack Kibana
1

Hi Team,

While perfroming REST API search from Dev Tools in Kibana UI, We are experiencing below error. After trying 2 to 3 times results are showing in UI.

{
  "statusCode": 502,
  "error": "Bad Gateway",
  "message": "Client request timeout"
}

In the same time we can see below message in Elasticsearch logs from master node. We check the ping status from kibana node to elastic nodes and the latency is less than
1 ms. Could you please help me on this.

[2024-05-02T12:56:44,644][INFO ][o.e.h.AbstractHttpServerTransport] [elasticnode1] channel [Netty4HttpChannel{localAddress=/192.168.130.171:9200, remoteAddress=/192.168.130.169:41718}] already closed

Thanks,
Debasis

2

Hi Team,

Any help on the above request .

Thanks,
Debasis

3

Hi @Debasis_Mallick ,

In Dev Tools you can add wait_for_completion=false requests parameter as it might be the timeout issue.

After trying 2 to 3 times results are showing in UI.
So it is not working smoothly in browser too?

Can you double check if Kibana/ES have enough resources?

Best regards, Dima

4

The elastic service consists of two nodes each(16 vcpus,64 GB RAM) so I do not think resource will be constraint here.

Thanks,
Debasis

5

Hi @Dzmitry ,

Any help on the above error and we checked with IT team there is no changes from INFRA side. The ping response from kibana nodes to elastic nodes are less than 1ms. We are not sure where to debug the issue.

Thanks,
Debasis

6

The elastic service consists of two nodes each(16 vcpus,64 GB RAM) so I do not think resource will be constraint here.

@Dzmitry , apart from the assigned resources, resource utilization is being observed and we dont see an issue there. Also, there is only a single query running at any given time. There is no ingest ongoing. There is nothing else running on the servers. Hence we dont believe resource is an issue.

7

Hey,

What stack version do you run and how it is installed?

Regards, Dima

8

@Dzmitry After adding below parameter value the above error is solved.

elasticsearch.requestTimeout: 60000

Thanks,
Debasis

9

Interesting. I think the default time elasticsearch client wait for response is 30000 (30 seconds)

Response in Dev Tools has "took": <value in milliseconds>, so you can try different queries and understand which ones are time consuming.

Best regards, Dima

10

Let me check and update.

Thanks,
Debasis