yangjian102621 commented on issue #946:
URL:
https://github.com/apache/rocketmq-client-go/issues/946#issuecomment-1278808542
I had find the reason. i should have specify a QueueSelector for the
producer.
```go
type MyQueueSelector struct{}
func (q MyQueueSelector) Select(msg *primitive.Message, mqs
[]*primitive.MessageQueue) *primitive.MessageQueue {
orderId, err := strconv.Atoi(msg.GetShardingKey())
if err == nil {
return mqs[orderId%len(mqs)]
} else {
return mqs[0]
}
}
// then create producer with specified queue selector
p, err := rocketmq.NewProducer(
producer.WithNameServer(config.NameSrvAddr),
producer.WithGroupName(config.ProducerGroup),
producer.WithRetry(2),
producer.WithQueueSelector(MyQueueSelector{}),
)
```
Then it works.
```go
INFO[0063] Receive message: Ordered Message Step -> 0, orderId: 0
INFO[0063] Receive message: Ordered Message Step -> 1, orderId: 0
INFO[0063] Receive message: Ordered Message Step -> 2, orderId: 0
INFO[0063] Receive message: Ordered Message Step -> 3, orderId: 0
INFO[0063] Receive message: Ordered Message Step -> 4, orderId: 0
INFO[0063] Receive message: Ordered Message Step -> 0, orderId: 1
INFO[0063] Receive message: Ordered Message Step -> 1, orderId: 1
INFO[0063] Receive message: Ordered Message Step -> 2, orderId: 1
INFO[0063] Receive message: Ordered Message Step -> 3, orderId: 1
INFO[0063] Receive message: Ordered Message Step -> 4, orderId: 1
INFO[0063] Receive message: Ordered Message Step -> 0, orderId: 2
INFO[0063] Receive message: Ordered Message Step -> 1, orderId: 2
INFO[0063] Receive message: Ordered Message Step -> 2, orderId: 2
INFO[0063] Receive message: Ordered Message Step -> 3, orderId: 2
INFO[0063] Receive message: Ordered Message Step -> 4, orderId: 2
```
And i found it does not had a example for orderly message Producer,
considering add one?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
