Hello there,
I use a Kibana 6.0.0 to request a very loaded Elasticsearch 6.0.0 to do insane dashboards. So the response time can go beyond 2 minutes. I agree to wait but Kibana seems to be less patient than me.
After few minutes (always less than 3), the Kibana returns this (in a top red banner):
Error: Gateway Timeout
ErrorAbstract@https://wassup.kibana.am.bigdata.intraorange/bundles/kibana.bundle.js?v=16070:12:24939
StatusCodeError@https://wassup.kibana.am.bigdata.intraorange/bundles/kibana.bundle.js?v=16070:12:28395
respond@https://wassup.kibana.am.bigdata.intraorange/bundles/kibana.bundle.js?v=16070:13:2730
checkRespForFailure@https://wassup.kibana.am.bigdata.intraorange/bundles/kibana.bundle.js?v=16070:13:1959
AngularConnector.prototype.request/<@https://wassup.kibana.am.bigdata.intraorange/bundles/kibana.bundle.js?v=16070:2:5100
processQueue@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:39:9912
scheduleProcessQueue/<@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:39:10805
$digest@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:39:21741
$apply@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:39:24509
done@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:38:9484
completeRequest@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:38:13952
createHttpBackend/</xhr.onload@https://wassup.kibana.am.bigdata.intraorange/bundles/commons.bundle.js?v=16070:38:14690
All the timeout settings I can think of (Kibana, ES, reverse proxies, etc) are beyond ten minutes.
We have two reverse proxies (26 minutes):
proxy_connect_timeout 1600;
proxy_send_timeout 1600;
proxy_read_timeout 1600;
send_timeout 1600;
and (166 minutes)
proxy_connect_timeout 9999;
proxy_send_timeout 9999;
proxy_read_timeout 9999;
send_timeout 9999;
Kibana (request for ES: 20 minutes):
elasticsearch.requestTimeout: 1200000
Elasticsearch (10 minutes):
{
"persistent" : {
"search" : {
"default_search_timeout" : "10m"
}
},
"transient" : { }
}
The problem was similar to this one, solved by this pull request. However all of this happened in Kibana 4. I still think it's a node.js configuration issue, and this issue, still open in 5.6.0, seems to agree.
Can someone help?
Regards.
Didier
PROBLEM SOLVED: there was a reverse-proxy between kibana (browser) and kibana (node.js).