[improve][broker] Add keyHashRangeIndex to distinguish the same hashRanges with the same consumerName

[Technoboy-]

Fixes #16654

Master Issue: #16654

Motivation

Add keyHashRangeIndex to distinguish the same hashRanges with the same consumerName.

Documentation

• doc-not-needed

[github-actions]

@Technoboy- Please provide a correct documentation label for your PR.
Instructions see Pulsar Documentation Label Guide.

[merlimat]

I think this will remove the possibility of having a stable assignment logic. Right now, if you specify the same consumer names, you will be guaranteed to receive the same keys after reconnections.

[codelipenghui]

I think this will remove the possibility of having a stable assignment logic. Right now, if you specify the same consumer names, you will be guaranteed to receive the same keys after reconnections.

Oh, good point. Maybe we should try to add more information to the topic stats instead of changing the behavior.

[leizhiyuan]

should we make consumerUniqueId a method of Consumer?

[Technoboy-]

I think this will remove the possibility of having a stable assignment logic. Right now, if you specify the same consumer names, you will be guaranteed to receive the same keys after reconnections.

Oh, good point. Maybe we should try to add more information to the topic stats instead of changing the behavior.

Add a new field to help user distinguish the same hashRanges.

[codelipenghui]

Can we get the consumer count without going through all the items of consumerKeyHashRanges? If we have many consumers under a topic, this might introduce CPU spike

[Technoboy-]

Decide to add more descriptions for this part.