MySQL Bugs: #90976: Slave SQL Thread Error

Bug #90976	Slave SQL Thread Error
Submitted:	22 May 2018 22:11	Modified:	16 Oct 2018 15:05
Reporter:	Sandeep Kumar Maharana	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Row Based Replication ( RBR )	Severity:	S3 (Non-critical)
Version:	5.7	OS:	Windows
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	SQL Thread Error on Trigger execution on master

Description:
when Trigger executed on master,the slave sql thread break.
This trigger is design to execute for particular user.
  

How to repeat:
I try to create same trigger on slave also,but till SQL thread dwon every time when trigger execute.

Two triggers are:-
CREATE DEFINER=`support`@`localhost` TRIGGER `tapas`.`master_AFTER_UPDATE` AFTER UPDATE ON `onelogin_master` FOR EACH ROW
BEGIN

declare user varchar(50);
select user() into user;

if user='support@localhost' then
update onelogin.master m 
set m.cellid =new.cellid,
m.uarfcndl=new.uarfcndl
where 
m.siteid=old.siteid
and m.pci=old.pci
 ;
 end if;

END

and :-

CREATE DEFINER=`support`@`localhost` TRIGGER `tapas`.`master_BEFORE_UPDATE` BEFORE UPDATE ON `onelogin_master` FOR EACH ROW
BEGIN
declare user varchar(50);
select user() into user;

if user='support@localhost' then
insert into onelogin_master_history (azimuth, beamwidth, vendor, operator, batch, siteid, cellid, sectorid, sector, uarfcndl, pci, band, timestamp, technology, unique_id,update_date)
values(old.azimuth, old.beamwidth, old.vendor, old.operator, old.batch,old.siteid,old.cellid, old.sectorid, old.sector, old.uarfcndl, old.pci, old.band, old.timestamp, old.technology, old.unique_id,now() )
;
end if;
END

I don't see this is a bug, if you run RAW based replication (and you should) the trigger should exec on master only, if you run STATEMENT based replication then you need to worry about replication safety of your queries. If you share more details (config, logs..) we can check this further but an generale, this is not a bug

all best
Bogdan