Try to recovery from relay log read problem automatically

See error below:

140930  8:57:59 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594

Errors such as these could be transient and automatically handled: the first time it happens at a particular position, the server can automatically stop the slave, reposition to the same master log file and master log pos (or GTID) and start slave again.

Of course this action should be reported in the errorlog also.
If the same error happens again at the same position, then it should not retry.

In a nutshell, having replication break on this situation and sit there "until human intervention arrives" is unnecessary, as the server can do exactly what the human would do.