You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current topic is bound to message, and the topic route can only be obtained when a message is sent. Therefore, after the service is restarted, the transactionProducer must send a message before it can check the previous semi-transaction message.
When business traffic is relatively low, the business may not send transaction messages for a long time after the service is restarted. As a result, during this period, previously sent semi-transaction messages will not be check, reducing the timeliness of the messages.
Motivation
transactionProducer get the topic route before sending the message
Describe the Solution You'd Like
transactionProducer get the topic route before sending the message
Describe Alternatives You've Considered
no
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
当前topic是和message绑定的,只有发送消息了才能获取到topic route。因此服务重启后,事务消息Producer必须发送一条消息后才能回查之前的半事务消息。
在业务流量比较低的时候,服务重启后可能很长时间业务都不会发送事务消息,导致在此期间,之前发送的半事务消息一直不会回查,降低了消息的时效性。
The current topic is bound to message, and the topic route can only be obtained when a message is sent. Therefore, after the service is restarted, the transactionProducer must send a message before it can check the previous semi-transaction message.
When business traffic is relatively low, the business may not send transaction messages for a long time after the service is restarted. As a result, during this period, previously sent semi-transaction messages will not be check, reducing the timeliness of the messages.
Motivation
transactionProducer get the topic route before sending the message
Describe the Solution You'd Like
transactionProducer get the topic route before sending the message
Describe Alternatives You've Considered
no
Additional Context
No response
The text was updated successfully, but these errors were encountered: