You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "ymwneu (via GitHub)" <gi...@apache.org> on 2025/09/02 07:43:00 UTC

[I] [Bug] Bug title [rocketmq]

ymwneu opened a new issue, #9654:
URL: https://github.com/apache/rocketmq/issues/9654

   ### Before Creating the Bug Report
   
   - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions)  of this repository and believe that this is not a duplicate.
   
   - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
   
   
   ### Runtime platform environment
   
   centos
   
   ### RocketMQ version
   
   latest version
   
   ### JDK Version
   
   jdk8
   
   ### Describe the Bug
   
   There is a variable called bufferLocal in TimerMessageStore, which is used to store a single message from the commitlog. The initial size of bufferLocal is currently set to maxMessageSize plus 100 bytes. Since some properties may be added during the intermediate stages of scheduled messages, the maximum message size can exceed maxMessageSize. Although an extra 100 bytes is reserved during initialization, in some scenarios this is not sufficient, resulting in message read failures and subsequently blocking the entire scheduled message process.
   
   ### Steps to Reproduce
   
   Send a timer message with its size set to the maximum allowed message size.
   
   ### What Did You Expect to See?
   
   Messages can be retrieved normally in TimerDequeueGetMessageService.
   
   ### What Did You See Instead?
   
   An exception is thrown when retrieving messages in TimerDequeueGetMessageService.
   
   ### Additional Context
   
   _No response_


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

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


Re: [I] [Bug]The bufferLocal size of the TimerMessageStore not enough [rocketmq]

Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #9654: [Bug]The bufferLocal size of the TimerMessageStore not enough 
URL: https://github.com/apache/rocketmq/issues/9654


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

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


Re: [I] [Bug]The bufferLocal size of the TimerMessageStore not enough [rocketmq]

Posted by "AradhyaSharma31 (via GitHub)" <gi...@apache.org>.
AradhyaSharma31 commented on issue #9654:
URL: https://github.com/apache/rocketmq/issues/9654#issuecomment-3401396046

   HI, I was going through the code base and I wanted to ask for some guidance: would maintainers prefer addressing this issue by:
   
   1. Increasing the fixed buffer margin,
   2. Making the buffer size configurable via `storeConfig`,
   3. Allowing dynamic allocation/resizing, or
   4. Some other approach?
   
   I want to ensure that any contribution aligns with the project’s design philosophy. 
   
   Thank you for your guidance!


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

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