You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In real life, ports are allocated by Mesos and ES needs a routable address. So the simplest solution is to run in host mode, so ES obtains the ip address of the host.
Thanks for the reply. We are using Elastic search container and its discovery is done via HA Proxy and consul. HA Proxy front end port is bind to 9200 and backend to host on which elastic search container is running. As mentioned container run in Host mode, there was a conflict. However we have excluded 9200 9300 ports from Mesos offers so the issue is not reproducible now.
Is there a way to run elastic search executors in Bridge mode?
Presently they run in Host mode.
The text was updated successfully, but these errors were encountered: