Hi, thanks for the answer
The problem was the syntax in the Elasticsearch Native Binary Protocol
Client, which tried to sniff the configuration behind the proxy.
Setting the clientTransportSniff="false" and transport addresses with the
right syntax was enough.
So this case solved, quilty was Life
I assume Liferay is throwing exceptions. Are these timeouts or indications
of broken connections?
A typical problem with the Elasticsearch Native Protocol is that it does not
like third-party tear-downs of connections it uses (e.g., by NGINX or some
load balancer).
Posted at Nginx Forum:
https:/
Hi,
I have tried to ask from Elasticsearch forums and googled everywhere, but
with no help so I registered here.
I am using NGiNX to cover my Elasticsearch clusters and all the clients
connect through them.
Everything else works fine to both the http and non-http traffic. The
problem is the Lifer
