ModEtchFill
ModEtchFill
It may be easier for migration to have username and passwords for client authentication. Using a separate hera user table would keep the application-to-hera and hera-to-database accounts flexible and maybe...
We'll want to make a config and a set of functions so it's easy to add other mechanisms.
Current direction is toward LDAPS
@Keenal Go for it
For the read-replica query failover, the failover database would be TWO_TASK_STANDBY0. For MySQL failover, two pipes to separate entries, tcp(127.0.0.1:3306)/myschema?timeout=9s||tcp(127.0.0.2:3306)/myschema I'm not sure if those cover how you'd like to...
We think the Oracle RAC read-write split won't work with MySQL. Oracle RAC has synchronous replication which most MySQL clusters don't. In any case, we'll need to adjust the heartbeat...
This may prevent use of Transparent Failover. We should test
In some discussions, it seems this may be too powerful and could be abused. Maybe thinking through a global-secondary-index case--possibly with caching--would constrain scatter-gather usage and keep hera sharding scalable.
We think scatter-gather will cause too many scaling issues and abuse
Please look at the otel branch for some early development