You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/05/07 03:39:15 UTC

[GitHub] [rocketmq] dongeforever commented on issue #4226: scheduleMessageOffset exception

dongeforever commented on issue #4226:
URL: https://github.com/apache/rocketmq/issues/4226#issuecomment-1120124946

   @ni-ze 
   
   你复现的问题，可能跟这个Issue关系不大，但确实是一个比较好的问题，可以考虑单独开一个Issue解决。
   
   在定时、事务、重试等场景中，不止是会改Topic名字，还会新增一些属性等，这个地方一直是个设计脆弱点。
   
   看看如下方式能否规避这个问题：
   1.  用户配置的maxMessageSize，只对body生效，不包含属性长度和Topic长度
   2. 对于一次发送的链路，Topic长度和属性长度，要按照最大值 - maxBlank来确定；二次发送链路（从定时或者事务里出来的），增加一个特殊的参数，以确保要发送成功；


-- 
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: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org