-
Notifications
You must be signed in to change notification settings - Fork 444
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
Is Message.ID unique id ? #250
Comments
If your cluster is configured to ensure that However, I wouldn't rely on this and would recommend you instead include your own identifiers in your message bodies that you ensure are globally unique. |
Some further notes: The nsq MessageID is currently only unique within a topic (and only if nsqd node IDs are different), other topics can easily have a message with the same MessageID. We only really want to promise that a MessageID will be unique for a particular connection between an nsq consumer and an nsqd. The only use of the MessageID should be for finishing or re-queuing a message. We want to be able to change the way these IDs are generated in the future, to be more efficient, and maybe robust against time going backwards, though I'm not sure if we will ... |
Ahh right, forgot about this! |
thanks. |
The text was updated successfully, but these errors were encountered: