Aias00 opened a new issue, #6792: URL: https://github.com/apache/shenyu/issues/6792
- severity: Medium-High - files: `shenyu-plugin/shenyu-plugin-proxy/shenyu-plugin-rpc/shenyu-plugin-dubbo/shenyu-plugin-apache-dubbo/src/main/java/org/apache/shenyu/plugin/apache/dubbo/cache/ApacheDubboConfigCache.java:253,282` (`reference.get()`); lazy-init fallback `ApacheDubboProxyService.java:135-140` (`initRefN` → `build` → `reference.get()`) - description: On first request per path or after `invalidate`/cache expiry, `getReferenceConfig` calls `ReferenceConfig.get()` on the calling (event-loop) thread. `ReferenceConfig.get()` synchronously connects to the registry (Zookeeper/Nacos), resolves providers and builds the `GenericService` proxy — known blocking, potentially multi-hundred-ms. - impact: Cold-start / metadata-refresh latency spikes on the Dubbo route; event-loop stalls when Dubbo references are lazily (re)built during traffic or registry flap. - suggested_fix: Pre-warm references off the event loop (the metadata-sync path already has `initRef`); ensure lazy init in `genericInvoker` is removed or moved to `Mono.fromCallable(...).subscribeOn(boundedElastic())`. - confidence: High --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/06-medium-tiers.md`](docs/scan2-2026-08-02/06-medium-tiers.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]
