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

Support to start a cluster in a single node #8

Closed
openinx opened this issue Jan 15, 2018 · 0 comments
Closed

Support to start a cluster in a single node #8

openinx opened this issue Jan 15, 2018 · 0 comments
Assignees
Milestone

Comments

@openinx
Copy link
Owner

openinx commented Jan 15, 2018

Now we cann't start a zookeeper cluster in a single node, because current config design can not specific different port for different process with the same job name.

we need to change the host part from:

hosts:
  - 127.0.0.1

to

hosts:
  127.0.0.1/port=9001/id=1:  # host.1
    config:
      zoo.cfg:
        - clientPort=2181
        - server.1=zoo1:2188:3188
  127.0.0.1/port=9001/id=2:  # host.2
    config:
      zoo.cfg:
        - clientPort=2281
        - server.2=zoo1:2288:3288
  127.0.0.1/port=9001/id=3:  # host.3
    config:
      zoo.cfg:
        - clientPort=2381
        - server.3=zoo1:2388:3288

BTW, the base_port part can be removed now.

@openinx openinx self-assigned this Jan 15, 2018
@openinx openinx added this to the release-1.0 milestone Jan 15, 2018
@openinx openinx closed this as completed Jan 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant