nsqadmin: per-host queue operations

[tj]

we're siloing for this case using an nsqd per-customer but you can only get to pause/empty at the higher level

[jehiah]

is this a situation where you'd be able to build your own tooling on the nsqd http api to pause/unpause a more select group of instances? (any instance pause/unpause should be reflected in the admin ui even if it's not a full topic.)

I know @mreiferson and I debated having more granular controls in nsqadmin for pause/unpause/empty but we decided against it to keep the management UI simpler, and to encourage thinking about streams a distributed stream of messages managed in whole.

[tj]

yup! we could definitely do that instead

[mreiferson]

We're in the process of planning an nsqadmin refactoring as outlined in #323, I'm going to create a milestone with all of these issues for consideration.

@visionmedia I'm confused about one thing - are you suggesting a "pause" feature for an entire nsqd (and all its topics and channels)?

[tj]

nope just individual nsqd granularity