Kristian, please review and apply attached patch. If you disagree with this patch or need any feedback from contributor, please post your comments here and set status to stalled.

It would be good to know which are the common error numbers that one would need to use with slave_transaction_retry_error when using Spider. This is needed when we document Spider and also as a recommendation when configuring MariaDB with
Spider usage.

Kentoku, do you have any suggestions for the error numbers that one should use?

I suggest the following errors.
1158: Got an error reading communication packets
1159: Got timeout reading communication packets
1160: Got an error writing communication packets
1161: Got timeout writing communication packets
2013: Lost connection to MySQL server during query
12701: Remote MySQL server has gone away

Pushed into bb-10.2-spider

Here is the commit comment:

This is about adding more options to force slave retries

Two new variables has been added:
slave_transaction_retry_errors

• Tells the slave thread to retry transaction for replication when a
  query event returns an error from the provided list. Deadlock and
  elapsed lock wait timeout errors are automatically added to this list
  slave-transaction-retry-interval
• Interval of the slave SQL thread will retry a transaction
  in case it failed with a deadlock or elapsed lock wait
  timeout or listed in slave_transaction_retry_errors

Other changes:

• Simplified code for slave_skip_errors (to be aligned with
  slave_transaction_retry_errors)
• Renamed print_slave_skip_errors() to make_slave_skip_errors_printable()
• Remove printing error from init_slave_skip_errors as my_bitmap_init()
  will do that if needed.
• Generalize has_temporary_error()

Cleaned up and pushed into bb-10.2-spider

The new system variables has been added to the KB