Comment 4 for bug 1456683

So, it seems haproxy waits answer from glance-registry a lot of time.
regarding the following line there was low-speed request from registry ~17 sec:
<134>May 18 20:38:45 node-1 haproxy[17376]: 192.168.0.5:57567 [18/May/2015:20:38:28.367] glance-registry glance-registry/node-3 0/0/0/16905/16905 200 983 - - ---- 560/4/3/1/0 0/0 "GET /images/f66cade6-cea8-4cea-86b9-2ec8a728f51b HTTP/1.1
I attached screenshot with atop at the time. But I don't thinks that the node was so busy.