Does NSQD ignores consumer disconnects? (server-wide message id)

[angry-elf]

Hello.

As I know, RabbitMQ handles consumer disconnects and resend lost-in-flight messages (without delivery reports) automatically to another connected consumer. It's looks ok as RabbitMQ has no unique (at least, per server) message id's (only per consumer).

As I realized, nsqd do not immediatelly resend messages from disconnected consumers which are in the "in-flight" state but wait confugred message timeout before. As I understand, customer can reconnect and send fin/req commands for messages, received in previous session.

Is it correct nsqd behaviour or side-effect? May be, it should be documented somewhere?

[mreiferson]

If a consumer disconnects while messages are in-flight they are treated like any condition where the message isn't responded to in time (ie, they timeout and re-queue).

Currently, a consumer cannot re-connect and respond to those messages... I suppose they could automatically re-queue without waiting the timeout (but that would simply be an optimization).

[mreiferson]

@angry-elf did you have any other questions relating to this?

[angry-elf]

Nop, thank you.