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 2022/01/10 02:00:14 UTC

[GitHub] [apisix] JiaYueHuang commented on issue #6034: bug: problems caused by stream_proxy (tcp proxy)

JiaYueHuang commented 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):
   ![apisix_config](https://user-images.githubusercontent.com/19731222/148710546-d957badd-f561-4b6a-8179-4c78df4dcd6e.png)
   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>`
   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org