dimon-v

I curled twice curl -I 'https://api-phx-tp-tc.xxx.com.cn/tlive/backend/liveroom/page?mobile=&roomStatus=&roomName=&current=1&direction=desc&limit=10&orderby=&sourceType=0&orgType=117' curl -I 'https://api-phx-tp-tc.xxx.com.cn/tlive/backend/liveroom/page?mobile=&roomStatus=&roomName=&current=1&direction=desc&limit=10&orderby=&sourceType=0&orgType=118' The upstream node of my route is 10.100.2.169, but it is found through packet capture that a request is connected to...

 10.120.0.10 is the route of "di-svcmaker" upstream node, the upstream node of "tp-tc" route is 10.100.2.169,

@monkeyDluffy6017 tks, In the screenshot: 1、curl -I 'https://api-phx-tp-tc.xxx.com.cn/tlive/backend/liveroom/page?mobile=&roomStatus=&roomName=&current=1&direction=desc&limit=10&orderby=&sourceType=0&orgType=117' Upstream and tcpdump are correct, 2、curl -I 'https://api-phx-tp-tc.xxx.com.cn/tlive/backend/liveroom/page?mobile=&roomStatus=&roomName=&current=1&direction=desc&limit=10&orderby=&sourceType=0&orgType=118' The log shows that upstream 10.100.2.169, but tcpdump requests 10.120.0.10 @tzssangglass tks，由于昨天磁盘空间不足，清空了apisix的日志。现有的日志不能跟issue截图的请求相对应，但是10.120.0.10这个nginx上有 api-phx-tp-tc.xxx.com.cn这个域名的日志，并且是301. 日志是apisix请求的。正常情况api-phx-tp-tc.xxx.com.cn是不会请求10.120.0.10...

My other online apisix cluster, the same version of apisix, has the same problem again; Please show me how to check. Thank you very much

Thank you very much, this is not accidental; If testing, how to reproduce this problem

By adding logs in/openresty/liulib/resty/limit/req.lua, the calculated elapsed has a complex number when the request is fast, After calculating the ABS function, Excess is 0  1 grep error log 


When using OpenResty Limit Req, Set the rate to 200 Burst setting 1, after using WRK stress testing, I calculated that the number of 200 status entries in the access...