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

JUST WONDER WHY PRODUCER dose not support lookupd ! is there any official explain for this? #322

Closed
infynity opened this issue May 17, 2021 · 1 comment
Labels

Comments

@infynity
Copy link

why only consumer uses lookupd ,tks

@jehiah jehiah transferred this issue from nsqio/nsq May 17, 2021
@jehiah
Copy link
Member

jehiah commented May 17, 2021

@infynity I've moved this to go-nsq since how publishing messages is implemented is a client library concern.

Publishing messages to nsqd via lookupd is not supported because lookupd state is based on information about where messages are which exists after publishing messages. When a topic doesn't exist on any nsqd instance yet, you can't use lookupd to determine where the first message should be published to.

cc: #311 which is working to make it easier to publish to a pool of nsqd instances.

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

3 participants