Firstsawyou commented on issue #3843:
URL: https://github.com/apache/apisix/issues/3843#issuecomment-803803759


   @spacewander  If you have time, please help look at this problem. In the 
proxy stream, can't we configure multiple upstream nodes? When I test that 
upsteam has multiple nodes, the following error message will appear:
   
   1、 add stream route
   
   ```shell
   curl http://127.0.0.1:9080/apisix/admin/stream_routes/1 -H 
'X-API-KEY:edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
   {   
       "upstream": {
           "nodes": {
               "172.16.10.241:6500": 1,
                "172.16.10.242:6500": 1
           },
           "type": "roundrobin"
       }
   }'
   ```
   
   2、 test request
   
   ```shell
   $ telnet 127.0.0.1 6500
   Trying 127.0.0.1...
   Connected to 127.0.0.1.
   Escape character is '^]'.
   Connection closed by foreign host.
   ```
   
   3、error.log  info
   
   ```
   2021/03/22 14:34:14 [error] 20162#20162: *41200 failed to run 
balancer_by_lua*: /home/apisix-bug-report/apisix/balancer.lua:50: table index 
is nil
   stack traceback:
           /home/apisix-bug-report/apisix/balancer.lua:50: in function 
'transform_node'
           /home/apisix-bug-report/apisix/balancer.lua:64: in function 
'fetch_health_nodes'
           /home/apisix-bug-report/apisix/balancer.lua:101: in function 
'create_obj_fun'
           /home/apisix-bug-report/apisix/core/lrucache.lua:92: in function 
'lrucache_server_picker'
           /home/apisix-bug-report/apisix/balancer.lua:189: in function 
'pick_server'
           /home/apisix-bug-report/apisix/balancer.lua:221: in function 
'load_balancer'
           /home/apisix-bug-report/apisix/init.lua:796: in function 
'stream_balancer_phase'
           balancer_by_lua:2: in main chunk while connecting to upstream, 
client: 127.0.0.1, server: 0.0.0.0:6500, bytes from/to client:0/0, bytes 
from/to upstream:0/0
   ```
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to