| Hjfocs added a comment. |
In T185637#3925101, @bd808 wrote:
- My knowledge of the stack stops here, but it sounds like Blazegraph talks to itself via HTTP?
Exactly.
HTTP Keep-Alive would be a client connection pooling optimization for Blazegraph talking to Blazegraph.
I agree it should. I tried with the Connection header, will investigate further.
There is no nginx proxy intervening in this conversation unless Blazegraph is actually talking to itself via the proxied hostname (pst.wmflabs.org) rather than direct communication using the 10.68.22.221:9999 ip and port.
True, it indeed uses direct communication.
The only way that I see an nginx instance would be involved is if you are using the public hostname of the proxy instead of directly talking to the internal service via an ip or internal hostname.
I totally agree. For some reason that is out of my knowledge, the upstream nginx directive solved the problem. That's why I opened this ticket.
Is there a part of this stack that I am misunderstanding
No, I think you grasped the picture.
is your initial inbound request actually to some other end point?
No.
Anyway, I really appreciate your analysis.
Will get back to you once I have terminated my investigation.
Cc: bd808, Aklapper, Hjfocs, 1978Gage2001, Lahi, aborrero, Gq86, GoranSMilovanovic, Kiailandi, Chicocvenancio, QZanden, Tbscho, dachary, LawExplorer, JJMC89, Luke081515, Wikidata-bugs, aude, Gryllida, Ricordisamoa, Sjoerddebruin, Tpt, scfc, Mbch331, Krenair, chasemp
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
