[GitHub] [rocketmq] cserwen commented on issue #3425: Can we use different SCHEDULE_TOPIC_XXXX for delay msg and retry msg?

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

cserwen commented on issue #3425:
URL: https://github.com/apache/rocketmq/issues/3425#issuecomment-951504066


   > This is due to the isolation problem of delay topic. It seems that splitting delay and retry could solve your case, but it will happen again when one of your delay topics is generating a lot of messages, and affect other delay topic. IMHO, we should pay more attention to the upgrade of the whole delay mechanism.
   
   @Jason918 
   - If we use different `ScheduleMessageService` and `SCHEDULE_TOPIC_XXXX`, the problem of mutual interference will be avoided.
   - Unless we can improve the performance of delayed messages to a very high level (for example, 5w TPS or higher), it will not be able to handle a large number of consumption failures and the `POP` consumption mode (heavily dependent on delayed messages) which will be provided later.


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