Elasticsearch Native Binary Protocol through NGiNX Stream

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Elasticsearch Native Binary Protocol through NGiNX Stream

Olaf van der Spek
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 Liferay client using Elasticsearch Native Binary Protocol.
Without NGiNX everything works right so NGiNX somehow does not understand
this.

Using Elasticsearch 6.8.6
Nginx 1.15.9
Red Hat 7.7

nginx.conf
---clip----
stream {
include /etc/nginx/conf.d/elasticsearch_tcp.conf;
}

elasticsearch_tcp_conf
server {
proxy_buffer_size 16k;
listen 10.100.5.10:8090;
proxy_pass 10.20.1.10:9300;

Any ideas for what I could try please?

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,287254,287254#msg-287254

_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx
Reply | Threaded
Open this post in threaded view
|

Re: Elasticsearch Native Binary Protocol through NGiNX Stream

Olaf van der Spek
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://forum.nginx.org/read.php?2,287254,287325#msg-287325

_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx
Reply | Threaded
Open this post in threaded view
|

Re: Elasticsearch Native Binary Protocol through NGiNX Stream

Olaf van der Spek
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 Liferay Client configuration.

Cheers

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,287254,287331#msg-287331

_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx