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 2019/08/08 03:30:51 UTC

[GitHub] [rocketmq] HymanShi commented on issue #1362: Throws ClientErrorCode.CONNECT_BROKER_EXCEPTION in MQClientException when send max times still failed which in DefaultMQProducerImpl.java

HymanShi commented on issue #1362: Throws ClientErrorCode.CONNECT_BROKER_EXCEPTION in MQClientException when send max times still failed which in DefaultMQProducerImpl.java
URL: https://github.com/apache/rocketmq/issues/1362#issuecomment-519348819
 
 
   > @HymanShi As you described, rocketmq indeed need to polish the mechanism to make it more clear and useful for positioning problem, so would you like to polish this together?
   > 
   > The second question, if the producer still retries when the SYSTEM_BUSY exception was responded by the server, it will increase the load of the server, so in order to protect the server,
   > the producer will stop the retry process.
   
   @duhenglucky Thanks for your invitation, I'd like to polish this mechanism and how can i join it?
   Reply to the second question:In fact, when users happen the SYSTEM_BUSY or other exceptions which are not in the retry list,users always resend the message themselves immediately in order to prevent sending failure.It will still increase the load of the server.Maybe rocketmq should provide a self-later-resend mechanism when SYSTEM_BUSY or other exception happens.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services