Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running elastic Search executors in Bridge Mode #560

Closed
rsingh2411 opened this issue Apr 22, 2016 · 3 comments
Closed

Running elastic Search executors in Bridge Mode #560

rsingh2411 opened this issue Apr 22, 2016 · 3 comments
Labels

Comments

@rsingh2411
Copy link

Is there a way to run elastic search executors in Bridge mode?
Presently they run in Host mode.

@philwinder
Copy link
Contributor

No, the HOST mode is hardcoded here:
https://github.com/mesos/elasticsearch/blob/master/scheduler/src/main/java/org/apache/mesos/elasticsearch/scheduler/TaskInfoFactory.java#L160

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.

What are you trying to achieve?

@rsingh2411
Copy link
Author

rsingh2411 commented Apr 25, 2016

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.

@philwinder
Copy link
Contributor

Understood, thanks. Yes, you shouldn't give ports to Mesos that are in use on your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants