I encountered 11 instances of the following in a binlog group commit along with one other transaction on a different table.
the slave settings where:
(replication not in gtid mode)
master had binlog_commit_wait_count=20
as such the replication was stopped and the error was in the log:
a) Stopping replication after slave_transaction_retries has been achieved puts me in a much worse state than continuing to try, so is there any case where slave_transaction_retries is useful (apart from catching a coding error)?
b) is slave_transaction_retries = slave-parallel-threads sufficient to resolve this in the mean time? or do i need to set this to factorial(slave-parallel-threads) ?
I read though
MDEV-7882 and it looked different. Does anything else post 10.0.17 release change the handling of this situation?