Jehiah Czebotar
Jehiah Czebotar
@armon This project has been incredibly useful - would you consider tagging a release for this project? (at v1.0 or otherwise) I'd love to be able to more reliably reference...
This adds support for a `nsqd` mode where messages are drained to facilitate removing a `nsqd` instance from a cluster. New `nsqd` API Endpoints * `PUT /state/shutdown` * `PUT /state/drain`...
This updates nsqd to have a `--topology-region` and `--topology-zone` config argument and prefer sending messages to same-zone and same-region consumers as proposed in #1300
To facilitate running `nsqd` in environments where the host isn't long running and to facilitate operations around managing a cluster a new "draining" mode will be introduced to `nsqd`. A...
NSQ does not facilitate easy ways to manage a cluster that spans a geographic boundary where it's ideal to prefer same-datacenter consumption to avoid extra network bandwidth and latency. This...
I'd like to provide an experience report from introducing new nsqd nodes to a cluster while operational activities which involve pausing channels are underway. --- Currently nsqd discovers the topic/channel...
Note: I'm primarily capturing this idea, I have no short term plan to implement this but want to put it out there. I've long wanted an ability to set a...
`nsqadmin` does a great job at exposing the consumers on a given topic/channel but there is no way to introspect the producers connected via TCP to a nsqd node. nsqd...
When using nsqd to expose data to external clients, it would be great to have a red x next to connections listed in nsqadmin so that you could kill them....
This supports nsqio/nsq#1305