Aias00 opened a new issue, #6698: URL: https://github.com/apache/shenyu/issues/6698
- severity: Medium - files: `shenyu-admin/src/main/java/org/apache/shenyu/admin/service/impl/DiscoveryUpstreamServiceImpl.java:101-106, 205-223` - description: `createOrUpdate` (public, no `@Transactional`) dispatches to private `create`/`update`, each of which does `mapper.insert`/`update` and then `fetchAll(...)` (which calls `discoveryProcessor.changeUpstream` — an external/discovery sync side-effect). If `fetchAll`/`changeUpstream` throws, the row write is already committed. `DiscoveryUpstreamController.createDiscoveryUpstreamList` compounds this by looping `createOrUpdate` with no transaction wrapper. - impact: Upstream rows persist in the DB while the discovery processor was never updated; gateway and admin disagree about upstream state. - suggested_fix: Add `@Transactional(rollbackFor = Exception.class)` to `createOrUpdate` and wrap the batch endpoint. - confidence: Medium - related_existing: none. --- _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]
