Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
Baoyuantop closed issue #11144: bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure URL: https://github.com/apache/apisix/issues/11144 -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
Baoyuantop commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-4021502293 APISIX is refusing to synchronize data from etcd due to a revision mismatch caused by data loss in etcd. This is not an APISIX problem. -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
Baoyuantop commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2914804571 Testing with the latest 3.12 version has the same problem. -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
Baoyuantop commented on issue #11144:
URL: https://github.com/apache/apisix/issues/11144#issuecomment-2914795261
I'm using apisix-docker with 3.7.0 for testing:
1. Start the project and configure routing
```
cd example & docker-compose up -d
```
```
{
"uri": "/anything",
"name": "apisix_test",
"priority": 1,
"methods": [
"GET"
],
"plugins": {},
"upstream": {
"nodes": [
{
"host": "httpbin.org",
"port": 80,
"weight": 1
}
]
}
}
```
Request the route can return normally.
2. Deletes the etcd container and removes the corresponding volumn then
restart etcd.
3. Modify the routing configuration to configure the wrong port.
```
{
"uri": "/anything",
"name": "apisix_test",
"priority": 1,
"methods": [
"GET"
],
"plugins": {},
"upstream": {
"nodes": [
{
"host": "httpbin.org",
"port": 81,
"weight": 1
}
]
}
}
```
Request the route reveals that it still returns normally.
The data in etcd is up to date at this point:
```
{"upstream":{"type":"roundrobin","scheme":"http","hash_on":"vars","pass_host":"pass","nodes":[{"priority":0,"weight":1,"host":"httpbin.org","port":81}]},"update_time":1748402288,"priority":1,"methods":["PUT","DELETE","PATCH","HEAD","OPTIONS","GET","POST"],"create_time":1748402288,"plugins":{},"uri":"/anything","status":1,"name":"apisix_test","id":"1"}
```
Requesting the control api reveals that the data in apisix is still old.
--
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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
github-actions[bot] commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2900645946 This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions. -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
JacobLi11 commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2151480626 mark -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
bstasz commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2142261265 Hello! I am having the same issue on both. Tried looking into the source of the issue but no luck. Am I missing a configuration or is there a bug? Both 3.3.0 and 3.9.1. Deployed with the Helm chart on EKS. -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
linyongluis commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2051777219 > please share the steps to reproduce this issue. 1、Running a apisix cluster 2、Configure a route by the admin api and access it successfully 3、Simulating etcd failures： First stop the etcd service, then delete all the data in etcd, then start etcd. 4、At this point, because apisix has not been rebooted, the previous route is still accessible to the 5、Modify the previous routing configuration (create) via the admin api: modify the node ip that corresponds to the upstream 6、Accessing this route reveals that although the configuration was successful and the data in etcd is correct, the apisix datasurface is still requesting the same node ip as before. -- 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]
Re: [I] bug: The apisix data plane does not update the upstream properly when etcd recovers from the failure [apisix]
shreemaan-abhishek commented on issue #11144: URL: https://github.com/apache/apisix/issues/11144#issuecomment-2051436046 please share the steps to reproduce this issue. -- 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]
