As of v5.7.5, MySQL hosts can (optionally) provide GTID information for their last write on Ok response packets: https://dev.mysql.com/worklog/task/?id=6128.
It would be useful to have a configuration option making ProxySQL update tracked GTIDs per host from these packets, instead of just the binlog reader process - it is free, zero-overhead information already provided by hosts which is not currently being taken into account for causal reads.
Updating GTIDs from Ok packets would also alleviate issues related to binlog reader failing to connect to ProxySQL hosts, ensuring GTID updates are tracked, to some degree, on connections performing updates. See f.ex. #5670 .
As of v5.7.5, MySQL hosts can (optionally) provide GTID information for their last write on
Okresponse packets: https://dev.mysql.com/worklog/task/?id=6128.It would be useful to have a configuration option making ProxySQL update tracked GTIDs per host from these packets, instead of just the binlog reader process - it is free, zero-overhead information already provided by hosts which is not currently being taken into account for causal reads.
Updating GTIDs from
Okpackets would also alleviate issues related to binlog reader failing to connect to ProxySQL hosts, ensuring GTID updates are tracked, to some degree, on connections performing updates. See f.ex. #5670 .