[GitHub] [rocketmq] Aaron-He commented on pull request #2290: [ISSUE #2289] Serverless schedule support builtin core

[GitBox <gi...@apache.org>]

Aaron-He commented on pull request #2290:
URL: https://github.com/apache/rocketmq/pull/2290#issuecomment-986220620


   > > > I found another problem needed to discuss:
   > > > if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
   > > > Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.
   > > 
   > > 
   > > We can separate the commitlog of delayMsg from the normal messages commitlog in the next version. we can work together.
   > 
   > Is the separate storage of delayed messages and normal messages realized now?
   
   
    A new architectural implementation (still based on time wheels) will be released in the future, making timing delay message configuration more flexible, more efficient to send and receive, and less impact on “normal messages”.


-- 
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