0

i'm running Magento CMS, and underneath there are 2 physical servers both with Percona

Server version: 5.6.23-72.1-log Percona Server (GPL), Release 72.1, Revision 0503478

in Master/Slave with GTID config.

Here it is the config, specific for GTID (it's the same also on salve)

server-id =1
binlog_format =MIXED
log_bin =/var/log/mysql/mysql-bin.log
expire_logs_days =3
max_binlog_size =50M
log_slave_updates =1
gtid-mode =on
enforce_gtid_consistency master-info-repository =TABLE
relay-log-info-repository =TABLE sync-master-info =1
binlog-checksum =CRC32
master-verify-checksum =1
report-host =BCVMaster

My client randomly during the day, receives this error:

SQLSTATE[HY000]: General error: 1785 When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

I'm willing to resolv this problem, me from a server stand point of view and i have 2 magento developers ready to help me, but i need help on how to trace, identify and visualize offending query so either me or developer can resolve the problem.

What i have done so far

1)converted as many possible tables from MyISAM to InnoDB

2)changed binlog format from row --> mixed

3)rebuild twice the slave with innobackupex

4) tried to read from binary logs: mysqlbinlog --base64-output=decode-rows -vv mysql-bin.000179 > /root/mysqlbin179.txt but seems i'm not looking in the right direction.

Can i please have some help on this?

thank you

  • Really no one? Come on please i need your help – x86fantini May 24 '15 at 20:37
  • i would realy apreciate any kind of help....really i'm stuck – x86fantini May 28 '15 at 20:00
  • I can not comment because I have 0 rep but just to validate your issue: I am running in to a similar issue. I am running Magento 2.1.3 on top of a Percona cluster with Redis Cache and Elasticsearch. I am not able to save a single product. When I try to save in the admin the message that I receive is "Asymmetric transaction rollback". The exception itself is thrown in vendor/magento/module-catalog-search/Model/Indexer/Fulltext/Plugin/Product.php After debugging I am able to obtain the actual exception in the addCommitCallback() method which is: SQLSTATE[HY000]: General error: 1787 When @@GLOBAL – DOfficial Jan 5 '17 at 0:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.