-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
nsqd: ephemeral channel race condition with reconnecting client #883
Labels
Comments
I send a commit, makes The commit seems fix this issue. I'm thinking if it make sense to remove topic from |
see #886 |
slayercat
added a commit
to slayercat/nsq
that referenced
this issue
Apr 18, 2017
slayercat
pushed a commit
to slayercat/nsq
that referenced
this issue
May 2, 2017
…ent. It's possible for a client reconnecting quickly and subscribed to an ephemeral channel to race with nsqd's cleanup of said ephemeral channel, as documented in nsqio/go-nsq#206. Fixes nsqio#883
slayercat
pushed a commit
to slayercat/nsq
that referenced
this issue
May 2, 2017
…ent. It's possible for a client reconnecting quickly and subscribed to an ephemeral channel to race with nsqd's cleanup of said ephemeral channel, as documented in nsqio/go-nsq#206. Fixes nsqio#883
slayercat
pushed a commit
to slayercat/nsq
that referenced
this issue
May 2, 2017
…ent. It's possible for a client reconnecting quickly and subscribed to an ephemeral channel to race with nsqd's cleanup of said ephemeral channel, as documented in nsqio/go-nsq#206. Fixes nsqio#883
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible for a client reconnecting quickly and subscribed to an ephemeral channel to race with
nsqd
's cleanup of said ephemeral channel, as documented in nsqio/go-nsq#206.The text was updated successfully, but these errors were encountered: