SAK

I saw in this video by Stephane https://docs.signal18.io/architecture/topologies/sharding the ability to see the proxy nodes via the web browser which we have not configured yet since the POC is based...

Would still like the shard proxy failover capabilities via the cli console. I am assuming since its a cli that same migh be command line driven for scripting a fail-over.

Noting both the browser and terminal consoles, neither support failover switchover control of the spider proxy nodes, which are MariaDB nodes. Would be ideal to support same from one replication-manager...

I would failover Spider proxy nodes because they are MariaDB databases; if the master proxy node fails, it needs to be managed. In particular, with the ever changing create or...

I just noted in the browser console , top left menu selection below the dashboard link there is a NEW MONITOR option, and one of the monitor types is shard...

spider proxy nodes have slaves they are mariadb databases

on the proxy tab I see the 3 nodes I defined listed, but no means to manage them for switch or failover

Understood, since it ia a MariaDB I as a DBA must accomodate its fail-over. Hoping this evoles to an enhancement. In the mean time what would you suggest?; a separate...

I could use the pre-fail-over script to adjust the traffic inflow to the new master proxy node.

The spider proxy nodes do have critical data ie the shard definitions themselves, and the ip's adjusted at shard cluster failover level, that data replicates to the salves so I...