hardme opened a new issue, #12497:
URL: https://github.com/apache/apisix/issues/12497
### Current Behavior
## Issue description
We are experiencing an intermittent issue where requests are routed to the
wrong upstream, even though the plugin chain should determine the correct
routing. The most concerning part is that when this happens, the plugin logs
are completely missing, but the access log shows the request was processed.
### Expected Behavior
Actual result
Occasionally, requests from a specific sid are routed to the wrong upstream
When this happens:
Access log shows the request was processed
Plugin logs (core.log.warn) are completely missing
The request reaches an incorrect upstream
Expected result
All requests should be routed according to the header matching rules
Plugin logs should always be present when plugins are executed
If plugins fail to execute, the request should not proceed to routing
### Error Logs
_No response_
### Steps to Reproduce
1. We have a plugin chain configured as follows:
- Plugin 1: Parse JWT token to extract `sid` and set it in header
- Plugin 2: Use the `sid` from header to call external service for
version info, then set version in header
- Plugin 3: `traffic-split` plugin routes to different upstreams based on
header matching rules
### Environment
- APISIX version (run `apisix version`):2.13.3
- Operating system (run `uname -a`):
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `luarocks --version`):
--
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]
