yuluo-yx opened a new issue, #1776: URL: https://github.com/apache/rocketmq-dashboard/issues/1776
**BUG REPORT** 1. Please describe the issue you observed: - What did you do (the steps to reproduce)? Fill a collection executor worker and its bounded queue, then submit another collection task. - What did you expect to see? Saturation should be visible to the caller so the failed collection can be observed and handled, while already queued work remains intact. - What did you see instead? `DiscardOldestPolicy` silently removes the oldest queued collection task and accepts the new one. This loses scheduled collection work without an error signal. 2. Please tell us about your environment: - apache/rocketmq-dashboard master - baseline commit `770822bbc812bfd0c2a94aa0128ab6f59b50d076` - JDK 17 3. Other information: `AbortPolicy` preserves queued work and reports saturation through `RejectedExecutionException`. -- 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]
