>My main concern with the new map is to have to potentially accumulate lots of >items in the concurrent hash map,
I'm understand your concern, i think the tracker map is limited by maxUnackMessages, only put element into tracker map when trigger by redeliverUnackedMessages(). > irrespective of whether the DLQ is being used or not. I think we can optimize it next step, i think we can add a field in proto like `enableRedeliveryTracker`, broker just enable this mechanism when `enableRedeliveryTracker` is true. > Especially, this might be mostly not the case in exclusive/failover > subscriptions, where data is typically processed in order. Yes, i'm agree, i think we can only enable the counter tracking only on Shared subscriptions, mean that just in PersistentDispatcherMultipleConsumers. [ Full content available at: https://github.com/apache/incubator-pulsar/pull/2508 ] This message was relayed via gitbox.apache.org for [email protected]
