This message was deleted.
# general
s
This message was deleted.
i
Copy code
"subscriptions" : {
    "subscriptionName" : {
      "msgRateOut" : 0.0,
      "msgThroughputOut" : 0.0,
      "bytesOutCounter" : 1099336,
      "msgOutCounter" : 11480,
      "msgRateRedeliver" : 0.0,
      "messageAckRate" : 0.0,
      "chunkedMessageRate" : 0,
      "msgBacklog" : 4,
      "backlogSize" : 119640,
      "earliestMsgPublishTimeInBacklog" : 0,
      "msgBacklogNoDelayed" : 4,
      "blockedSubscriptionOnUnackedMsgs" : false,
      "unackedMessages" : 820,
      "type" : "Key_Shared",
      "msgRateExpired" : 0.0,
      "totalMsgExpired" : 0,
      "lastExpireTimestamp" : 0,
      "lastConsumedFlowTimestamp" : 1691146017587,
      "lastConsumedTimestamp" : 1691146017565,
      "lastAckedTimestamp" : 0,
      "lastMarkDeleteAdvancedTimestamp" : 0,
      "consumers" : [ {
        ...
        "messageAckRate" : 0.0,
        ...
        "availablePermits" : 680,
        "unackedMessages" : 820,
        ...
        "blockedConsumerOnUnackedMsgs" : false,
        "readPositionWhenJoining" : "16:3",
        "lastAckedTimestamp" : 0,
        "lastConsumedTimestamp" : 1691146017565,
        "lastConsumedFlowTimestamp" : 1691146017582,
        ...
        "lastAckedTime" : "1970-01-01T00:00:00Z",
        "lastConsumedTime" : "2023-08-04T10:46:57.565Z"
      },
p
For the key_shared subscription. The newly joined consumer can only consume messages when the mark delete position goes through the read position when the consumer joins.
i
The old stalled consumer gets disconnected after some time. Apparently, after that keys are reshuffled and messages start being consumed. At least, I observe such behaviour, that the new consumer receives messages.
The new consumer receives the messages:
unackedMessages:820
.
p
Yes, that is expected. If a message is redelivered by a consumer, it will be available to other consumers. When the old stalled consumer gets disconnected, all the unacked message of this consumer will be redelivered.
🙏 1