Pierce Lopez
Pierce Lopez
> The best practice for scraping metrics is to do that against Pods and/or Endpoints, not Services ports directly. It is known to cause issues if more than one endpoint...
So it seems prometheus is working much differently than I assumed, from reading the chart. But then it seems like there's still much to cleanup in the chart? The existence...
Should the nsqd pods get the prometheus annotations, and this Service just be removed?
I think it may reasonable to merge this as-is :shrug:
nsqd is not supposed to be particularly ephemeral, so it is a StatefulSet in this chart. The nsqd instances should use their PodIP as broadcast-address, because consumers should connect to...
> My proposal with this discussion is to consider ... utilizing a name lookup mechanism for locating nsqd IPs That's what `nsqlookupd` does. Consumers poll nsqlookupd periodically (every 30s by...
> reduce the interval which consumers poll nsqlookupd You can generally set this, see for example the LookupPollInterval in https://pkg.go.dev/github.com/nsqio/go-nsq?utm_source=godoc#Config You may also want to reduce the nsqlookupd `-inactive-producer-timeout` https://nsq.io/components/nsqlookupd.html#command-line-options...
Nope, not interested in doing this, sorry.
If the topic and channels already exist on another nsqd, then when a new nsqd gets the first message of a new topic, it should fetch all channels that should...
not sure if this is really needed, the sub-classing of `ExitStack` seems pretty simple