Current State: Proposed
Authors: Jianfeng Wu
Shepherds: Zhendong Liu
Mailing List discussion:
Pull Request: #PR_NUMBER
Released: <relased_version>

No

No

Yes, In our testing environment, we need test different feture in the same time, so we need deploy different consumer logic instance in the different test environment for test different feture, but message will be consumed not our expect consumer instance.

Improve consumer in same Consumer Group Name to support different RACK, producer can specify message RACK when send message.

The producer can't specify who consumer instance can consumed when send message.

This solution I proposed consists of two operations: send message and consumer message strategy.

  Specify message for which RACK when producer send.

  consumer instance can specify RACK or default RACK, if specify RACK, this consumer will only consume specify the same RACK message, if the message not have consumer specify same RACK, will consumed by default RACK consumer.