starryCoder commented on PR #3848: URL: https://github.com/apache/hertzbeat/pull/3848#issuecomment-3535186246
That makes perfect sense!This strategy is much cleaner and more robust. > > Is my understanding of your proposed solutions correct? > > 👍 Yes, your summary is correct. My idea is that adding an exponential backoff strategy at the public consumption end, without concerning the implementation of the queue, won't affect the overall logic. It only needs to be triggered when the return value is null, for example: 50ms, 100ms, 500ms...1s. This prevents the queue implementation from causing system overload due to exceptionally rapid failures. That makes perfect sense! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
