This message was deleted.
# general
s
This message was deleted.
m
We also have this issue, looking on Bookkeeper performance, but do not know where it come from
j
New key with no existing consumers? So waiting on some re-discovery time?
j
Unfortunately, its happens even if there are messages with already consumed key in the backlog.
@James what do you mean by "re-discovery", consumer is not automatically selected from mumur hash ?
j
I just assume there's a discovery process when there's a new key like there is with new partitions.
j
You should read documentation it's not working by partition allocation but much more a customer chooses upon a range in a ring.
j
You should read my statement I didn't say it was working by partition allocation.
j
Sorry for the misunderstood, what do you mean by discovery?
By the way, increasing
receiverQueueSize
has improved performance and has reduces idle time.