Stephane VAROQUI

> Le 16 mars 2018 à 15:06, Jan a écrit : > > Valid point. In my test dummy, the master is also configured as a slave, but of course...

This is critical to keep the level because of this func (SM *StateMachine) IsFailable() bool { SM.Lock() for _, value := range *SM.OldState { if value.ErrType == "ERROR" { SM.Unlock()...

Hi Sak, yes they are internally monitored like MariaDb nodes, why would you failover the spider nodes, each table is pointing to each shard master via the server system table...

But spider nodes are not slaves , they are just proxies without data neither replication ? replication-manager tack the tables on the shards and build those link for you

I don't think this is will help that a way to build the config when dynamic config is enable They should any way show under the proxy tab If not...

This architecture is not supported what those slaves supposed to do ? May it's an architecture I never faced

oooooh I see what you wan't to do now ! you would like only one active proxy ,a VIP with a keepalived in between would match in this case and...

The plan was that the shard definitions is manage by replication manager and pushdown to the spider nodes . shard definitions are today : - federation for table_schema.table_name unique in...

What I would like to do introduce is a fist list of schema.tables that are universal so federation on multiple shards

Ok i have already pushed spider to aggregate 1 billions rows per second so to shard by hash of pk just create same schema.table in each shard master and point...