#1254·nsq

*: make NSQ "cloud native"

Author: thestephenstantonCreated May 12, 2020Updated Feb 21, 2024
Labelsfeaturerequest

When running nsqd on AWS's ECS using Fargate, we are running into a problem where when nsqd gets SIGTERM, it automatically closes all ports and writes to disk everything that it has. Is there a reason that nsqd doesn't allow the consumers to finish reading off of the channel then do that flushing? Even more so for us, most of our messages are already inflight, so why not just let them finish up?

I would add this ability myself, I am just wondering though if there is a specific reason for this happening this way. It could be a flag that the user can give an amount of time that the consumer has left to finish before it flushes everything to disk.