You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to build out a graceful restart strategy for proxysql (for new releases, since they happen a lot and our current strategy of using keepalived to fail over the whole host for proxysql restart suscks). My current plan is to start a new instance (on a different admin socket) with the same config as the main instance, shut down the existing instance with the PROXYSQL SHUTDOWN command (which looks like it is a graceful shutdown), then reverse the process to flip back to the "normal" instance.
I'm currently stymied by the fact that the command line argument --admin-socket seems to be ignored if the admin-mysql_ifaces global variable is set, so there's no way for me to run two instances with different admin sockets without having totally different on-disk configuration files.
Would it be reasonable to make --admin-socket either override admin-mysql_ifaces or add to it?
The text was updated successfully, but these errors were encountered:
This is an important enhancement.
The reason why admin-mysql_ifaces overrides the command line argument --admin-socket is that it is possible to change admin-mysql_ifaces at runtime.
Therefore a solution could be that admin-mysql_ifaces does not overrides the command line argument --admin-socketat startup only
I'm trying to build out a graceful restart strategy for proxysql (for new releases, since they happen a lot and our current strategy of using keepalived to fail over the whole host for proxysql restart suscks). My current plan is to start a new instance (on a different admin socket) with the same config as the main instance, shut down the existing instance with the
PROXYSQL SHUTDOWN
command (which looks like it is a graceful shutdown), then reverse the process to flip back to the "normal" instance.I'm currently stymied by the fact that the command line argument
--admin-socket
seems to be ignored if theadmin-mysql_ifaces
global variable is set, so there's no way for me to run two instances with different admin sockets without having totally different on-disk configuration files.Would it be reasonable to make
--admin-socket
either overrideadmin-mysql_ifaces
or add to it?The text was updated successfully, but these errors were encountered: