tzssangglass commented on issue #5767:
URL: https://github.com/apache/apisix/issues/5767#issuecomment-1001998778


   After  checked, I found that this is a bug. 
   
   As I mentioned above, add the service configuration as follows
   
   ```
   {
       "name": "arch.test.nacos",
       "upstream": {
           "timeout": {
               "connect": 6,
               "send": 6,
               "read": 6
           },
           "type": "roundrobin",
           "scheme": "http",
           "discovery_type": "nacos",
           "pass_host": "pass",
           "service_name": "service-provider",
           "keepalive_pool": {
               "idle_timeout": 60,
               "requests": 1000,
               "size": 320
           }
       }
   }
   ```
   
   
   add  the upstream configuration as follows
   
   ```
   {
       "timeout": {
           "connect": 6,
           "send": 6,
           "read": 6
       },
       "type": "roundrobin",
       "scheme": "http",
       "discovery_type": "nacos",
       "pass_host": "pass",
       "name": "arch.test.nacos",
       "service_name": "service-provider",
       "keepalive_pool": {
           "idle_timeout": 60,
           "requests": 1000,
           "size": 320
       }
   }
   ```
   
   We should note that the service itself does not have a `service_name` 
attribute.
   
   my error.log is 
   
   
   ```
   2021/12/28 18:10:29 [warn] 695#14133352: *20589 [lua] upstream.lua:251: 
set_upstream(): new_nodes : { {
       host = "192.168.2.43",
       port = 8070,
       weight = 1
     }, {
       host = "192.168.2.43",
       port = 8070,
       weight = 1
     }, {
       host = "192.168.2.43",
       port = 8070,
       weight = 1
     } }, client: 127.0.0.1, server: _, request: "GET /echo/hello HTTP/1.1", 
host: "127.0.0.1:9080"
   ```


-- 
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]


Reply via email to