JiaYueHuang edited a comment on issue #6034: URL: https://github.com/apache/apisix/issues/6034#issuecomment-1008485771
I use apisix to encapsulate the openstack’s API to achieve high availability and rate limiting. 1.Problem description My apisix configuration file (config.yaml) shows below (only shows the problem related part):  I use the stream_proxy (tcp proxy) to listen ``vip`` (provided by keepalived) and 11211, 3306 ports (related to memcached and mysql services), and then I will create ``upstream`` and ``route`` related to memcached and mysql services to achive High Availability (shown below). Notice: I observed that, for msyql and memcache services, stream_proxy (tcp proxy) must be used, otherwise (if still use the http proxy), mysql and memcache services wouldn’t work out (commands below couldn’t connect correctly). `telnet <vip> 11211` `mysql -ukeystone -pKeyStone_pwd -h<vip>` For simplicity, related upstreams has only one node: Mysql’s upstream shows blow:  Memcached’s upstream shows below:  Mysql’s stream_route (experiment shows that it’s also valid for ordinary route, but will have the same problem) shows below (matched by 3306 port and forward the service to specific node):  Memcache’s stream_route :  Then we test the mysql and memcache services, execute the command below (it shows correctly): `telnet <vip> 11211` `mysql -ukeystone -pKeyStone_pwd -h<vip>`   -- 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]
