The Ultimate Guide to High Availability with MariaDB

Error 1837: When GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLLBACK

You are viewing an old version of this article. View the current version here.
Error CodeSQLSTATEErrorDescription
1837HY000ER_GTID_NEXT_TYPE_UNDEFINED_GROUPWhen GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLLBACK. If you see this error message in the slave SQL thread, it means that a table in the current transaction is transactional on the master and non-transactional on the slave. In a client connection, it means that you executed SET GTID_NEXT before a transaction and forgot to set GTID_NEXT to a different identifier or to 'AUTOMATIC' after COMMIT or ROLLBACK. Current GTID_NEXT is '%s'

Contents

  1. Possible Causes and Solutions

Possible Causes and Solutions

This article doesn't currently contain any content. You can help!

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.