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

io.l5d.serversets discovery zookeeper is invalid #2197

Closed
chenhaibocode opened this issue Dec 20, 2018 · 5 comments
Closed

io.l5d.serversets discovery zookeeper is invalid #2197

chenhaibocode opened this issue Dec 20, 2018 · 5 comments

Comments

@chenhaibocode
Copy link

chenhaibocode commented Dec 20, 2018

I tried it as a document, but I still couldn't. I wanted to use zookeeper as my disco, and then Linkerd routed the service IP port through zookeeper.

console log:
image

postman:
image

linkerd.yaml:
image

zookeeper data:
image

@dadjeibaah
Copy link
Contributor

Thanks for filing this @chenhaibocode, this is strange since you have everything wired up correctly and that logical path results in a (neg). We will dig into this.

@chenhaibocode
Copy link
Author

@dadjeibaah ok, thank you.

@chenhaibocode
Copy link
Author

@dadjeibaah Is it related to the zookeeper version?

@adleong
Copy link
Member

adleong commented Jan 23, 2019

Hi @chenhaibocode. What library are you using to populate the serverset entries into Zookeeper? Or are you populating it manually? I believe the serversets protocol requires that entries in a serverset should be ephemeral znodes as children of the service name. So in your example, the service endpoint data should live in an emphemeral child of /discovery/prod/test.

@adleong
Copy link
Member

adleong commented Feb 4, 2019

Hope my previous comment was helpful. Please re-open this issue if that doesn't work for you.

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

No branches or pull requests

3 participants