-
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: cannot delete topic #343
Comments
hi @visionmedia - looks like you have consumers still connected on the |
ohh shit, we're using nsqlookupd to locate the nodes and reconnect when disconnected, I'll try pausing our ingestion queue and shut those down before removing the topic |
nevermind that won't work too well for now haha way too many services connected from before, we'd have to shut down everything to get rid of it |
right, the typical order to completely delete a topic would be:
|
just going to launch some new nodes that'll probably be faster, thanks! |
hrrm going to re-open, this is becoming a big issue for us, some how they keep sneaking in there, our own fault of course but we everything in our cluster uses "events" so we can't really shut them all down easily just to delete a topic from a node |
can you paste the |
it's by-design that a consumer also creates the topic isn't it? Problem is right now that we've got into a bit of a mess there with 3 or 4 programs, on 100s of machines connecting to these nsqds that accidentally had the "events" topic. Seems like the only way to really fix that problem is to shut them all down, remove the topic, and boot them all back up |
it is by design, but you should still be able to delete a topic for a single node (the topic should be tombstoned for a short interval where it isn't returned via lookupd, connections disconnected, and then purged fully from lookupd). I was curious to see logs to see if those things were happening... |
ah ok I don't remember trying individual nodes, I'll try that out |
That would explain things... if you weren't using the topic tombstone then you would experience these symptoms. Specifically, it's the little red-x next to the nodes on a topic page: For more info see: http://nsq.io/components/nsqlookupd.html#deletion_tombstones (closing) |
hmm, I'm just using the default tombstone value, but they're definitely re-registering immediately. Here's with the X on the node's page:
and here's the nsqd log with the X on the topic page:
and one of the nsqlookupd's:
|
@visionmedia these clients are using What is their behavior when clients are configured to use According to these logs, it looks like it reconnects immediately. That's not quite correct, it should wait for the next discovery cycle and only if it finds that node again should it reconnect. That would also cause these symptoms. |
Yeah they just attempt to reconnect with backoff right now, I guess that's where I found the behaviour of a consumer creating a topic a little weird. I'll get that updated thanks! |
Not really sure what's going on here, our primary topic is "events", and I have a bunch of unrelated nsqd nodes set up which did have "events" at one point, however it won't let me delete the topic. I get a 200 response, but it's created again immediately after even though we're not publishing to an "events" topic on any of those nodes.
nsqadmin correctly displays that in-flight and messages for those nodes are all 0, so I'm confused about it not letting me remove the topic.
Truncated screen:
The text was updated successfully, but these errors were encountered: