Upgrade Replication of Ndb Cluster to GTID (1 reply)

How can the "gap event" generated by the Ndb cluster be skipped when restarting the cluster? This event is not being generated inside a GTID transaction. In the past we were able to skip 1 transaction and the replication would start.

With GTID enabled for the replication and Ndb generating a transaction that is not within a Global Transaction we are no longer able to skip the event generated when restarting the Ndb cluster.

Is there a way to skip an event which does not have a GTID?

Thanks