You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/05/14 16:02:11 UTC

[GitHub] [incubator-apisix] stone4774 edited a comment on issue #1452: feature: Load balancing of weighted-upstream

stone4774 edited a comment on issue #1452:
URL: https://github.com/apache/incubator-apisix/issues/1452#issuecomment-614516119


   @moonming 
   
   When a service publishes a new version, you can create a new upstream (similar to the cluster in envoy) for the instance of the new version, configure it to the service, and specify the weight as follows:
   
   ```
   curl http://127.0.0.1:9080/apisix/admin/services/200 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
   {
       "weighted_upstreams": {
           "total_weight": 100,
           "upstream_ids":[
               {
                    "upstream_id":1,
                    "weight": 99
               },{
                    "upstream_id":2,
                    "weight": 1
               }
           ]
       }
   }'
   ```
   
   I think it's very important, but at present, apsix doesn't support it. Now if I want to use a small amount of traffic to verify the new version, I have to find some routes with small traffic to try, but these traffic is selective and can't cover all situations
   
   We can refer to the implementation of envoy:
   https://www.envoyproxy.io/docs/envoy/v1.14.0/configuration/http/http_conn_man/traffic_splitting
   
   


----------------------------------------------------------------
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:
users@infra.apache.org