bin-53 opened a new issue, #10071:
URL: https://github.com/apache/apisix/issues/10071
### Description
When I discovered using apisix's eureka service, I couldn't get the node on
the registry
the error log:
```
2023/08/22 05:20:29 [error] 47#47: *477106 [lua] init.lua:540:
http_access_phase(): failed to set upstream: no valid upstream node: nil,
client: 192.168.88.66, server: _, request: "GET /eureka/home/ HTTP/1.1", host:
"10.210.21.105:9080"
```
1.the route config:
```
{
"id": "475035634029822659",
"create_time": 1692672902,
"update_time": 1692673262,
"uri": "/eureka/*",
"name": "Eureka",
"priority": 1,
"methods": [
"GET",
"POST",
"PUT",
"DELETE",
"PATCH",
"HEAD",
"OPTIONS"
],
"plugins": {
"proxy-rewrite": {
"regex_uri": [
"^/eureka(/|$)(.*)",
"/$2"
]
}
},
"upstream": {
"retries": 1,
"timeout": {
"connect": 6,
"send": 6,
"read": 6
},
"type": "roundrobin",
"scheme": "http",
"discovery_type": "eureka",
"discovery_args": {
"group_name": "",
"namespace_id": ""
},
"pass_host": "pass",
"service_name": "EUREKA-CLIENT",
"keepalive_pool": {
"idle_timeout": 60,
"requests": 1000,
"size": 320
}
},
"labels": {
"API_VERSION": "1.0"
},
"status": 1
}
```
2.the config.yaml :
```
discovery:
eureka:
host: # it's possible to define multiple eureka hosts addresses of the
same eureka cluster.
- "http://10.210.21.105:8761";
prefix: "/eureka/"
```
3.and My eureka server is normal:
4.the operate:
### Environment
- APISIX version (run `apisix version`):2.15
- 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]
