kibana 4.4.1 in docker times out communicating with elasticsearch 2.2.0 in docker

[dfwcnj]

the processes are communicating via a docker overlay network. to make it work at all, i am forced to change a hard coded timeout from 1500 to 10000 in health_check.js. i attached the Dockerfile and kibana.yml
with the rise of networked containers, it would be nice to have more liberal timeouts.

kc.zip

[rashidkpc]

If the latency between your containers is that high you have a problem somewhere in your deployment.

That said, will be fixed here: #6341

[dfwcnj]

fair assumption.

actually, the latency appears to be due to my use of docker overlay networks. the extra copy overhead introduced by a couple of veth pairs, a couple of bridges and a vxlan seems to be the problem. the curl output below shows that I am a bit outside the limit imposed by the code, but not excessively so in my opinion.

i guess that my real complaints are that there seem to be a lot of hard coded values in the code when many of them should be configurable and that the logs do not seem to be sufficiently informative for me to track down the source of my problem without guess work.
.
time curl -i http://elasticsearch01:9200/
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 305

{
"name" : "EL5",
"cluster_name" : "ULDemo",
"version" : {
"number" : "2.2.0",
"build_hash" : "8ff36d139e16f8720f2947ef62c8167a888992fe",
"build_timestamp" : "2016-01-27T13:32:39Z",
"build_snapshot" : false,
"lucene_version" : "5.4.1"
},
"tagline" : "You Know, for Search"
}

real 0m2.522s
user 0m0.004s
sys 0m0.004s