We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Case
某业务比较小,只有2台服务器, 做物理主备比较合适,但在读写分离时遇到了问题,好像4.1版本的obproxy不支持物理主备库的读写分离,希望能支持。
Describe the solution you'd like
程序连接obproxy,根据设置或hint提示 可以访问主库,也可以访问备库
Describe alternatives you've considered
目前主库上并不能获取到备库的信息。 建议可以在obproxy中配置物理主备库的信息(路由缓存),可以根据健康检查脚本的返回结果去判断当前主备库的状态(处于主库、备库或者宕机状态), 类似于proxysql吧
Additional context
The text was updated successfully, but these errors were encountered:
看起来仅跟obproxy相关,转到obproxy的仓库
Sorry, something went wrong.
此功能已经收到,还未有明确的支持时间
No branches or pull requests
Use Case
某业务比较小,只有2台服务器, 做物理主备比较合适,但在读写分离时遇到了问题,好像4.1版本的obproxy不支持物理主备库的读写分离,希望能支持。
Describe the solution you'd like
程序连接obproxy,根据设置或hint提示 可以访问主库,也可以访问备库
Describe alternatives you've considered
目前主库上并不能获取到备库的信息。 建议可以在obproxy中配置物理主备库的信息(路由缓存),可以根据健康检查脚本的返回结果去判断当前主备库的状态(处于主库、备库或者宕机状态), 类似于proxysql吧
Additional context
The text was updated successfully, but these errors were encountered: