Aias00 opened a new issue, #6669: URL: https://github.com/apache/shenyu/issues/6669
- severity: High - files: `shenyu-disruptor/src/main/java/org/apache/shenyu/disruptor/DisruptorProviderManage.java:108-110` (`OrderlyExecutor(consumerSize, consumerSize, 0, MS, new LinkedBlockingQueue<>(), ..., AbortPolicy)`), `shenyu-disruptor/src/main/java/org/apache/shenyu/disruptor/thread/SingletonExecutor.java:32-34` (1,1,0,`new LinkedBlockingQueue<>()`), `QueueConsumer.java:58` (`executor.execute(queueConsumerExecutor)`) - description: The Disruptor ring buffer (`DEFAULT_SIZE=16384`) is bounded, but `QueueConsumer.onEvent` hands each consumed event to an executor backed by an *unbounded* queue. When consumers are slower than producers (e.g. admin persisting registrations to DB), the executor queue grows without bound → OOM. `AbortPolicy` is dead code (an unbounded queue never rejects). For orderly events the single `SingletonExecutor` thread is the per-key bottleneck. - impact: `RegisterClientServerDisruptorPublisher` (admin) and `ShenyuClientRegisterEventPublisher` (client) accumulate unbounded queued tasks under registration burst / DB slowdown. - suggested_fix: Bound the executor queue (`ArrayBlockingQueue` sized to ring-buffer slots) with `CallerRunsPolicy` (or block-the-producer) so Disruptor backpressure propagates to the consumer. - confidence: High --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/00-consolidated-critical-high.md`](docs/scan2-2026-08-02/00-consolidated-critical-high.md)._ -- 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]
