"mario.cova--- via discuss" <[email protected]> writes:
> You can find below an occurrence of exiting and starting (in this case > via cron). No errors in show slave. > 2025-06-26 9:52:40 3603689 [Note] Slave SQL thread exiting, > replication stopped in log 'binlog.001785' at position 192319795, > 2025-06-26 9:53:01 3608261 [Note] Slave SQL thread initialized, > starting replication in log 'binlog.001785' at position 192319795, > relay log './relay-bin.000490' position: 192320091 > 2025-06-26 9:53:01 3608261 [Note] WSREP: ready state reached Hm, WSREP - so you are using Galera? Unfortunately, I'm not much familiar with the details of Galera. For normal (non-galera) MariaDB replication, I would expect to find a message in the error log explaining why the SQL thread stopped - for example due to reaching a START SLAVE UNTIL, user KILL statement, explicit STOP SLAVE statement, etc. It might be a Galera-specific bug that this is not seen here. - Kristian. _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
