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

enable nimbus & UI servers to be asisgned with available port, instead of pre-configured #622

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

anfeng
Copy link
Collaborator

@anfeng anfeng commented Jul 6, 2013

This is one of a series pull requests, which aim to launch Storm cluster in a cluster environment.

Currently, Nimbus server and UI server launched with a configured port number. In a cloud environment,
we don't really know which port is actually available. So, it will be convenient if Nimbus & UI server could simply
find an available port and launch it.

In this pull request, we enable Nimbus server and UI server to find ports dynamically:

  • If the nimbus port is configured to be <=0, Nimbus server will find an available port.
  • If the UI port is configured to be <=0, UI server will find an available port.
    Nimbus/UI server announces the port number via Zookeeper.

When Supervisor and UI server starts, they will pick up Nimbus host/port from Zookeeper (instead of simply reading configuration file).

@nathanmarz
Copy link
Owner

This overlaps with the work done in #422 to implement HA Nimbus (it uses ZK for Nimbus discovery as part of the implementation). It would be great to get some more work done on that one (it just needs to be tested more).

@anfeng
Copy link
Collaborator Author

anfeng commented Jul 9, 2013

Do you want to merge #422 first? This new pull request is much simpler though.

@nathanmarz
Copy link
Owner

The HA Nimbus is far more important... and this issue would just create more work for that one. For now, for the cloud-specific use case, can't whatever's launching Nimbus find a port and configure it appropriately? That's effectively how the worker ports are configured in storm-mesos.

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

Successfully merging this pull request may close these issues.

2 participants