Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with gtid
Search options not deleted
user 7697
GTID - MySQL's Global Transaction Identifier
0
votes
1
answer
128
views
What could cause replication to break on MySQL when replicating from 5.7.40 to 8.0 replica
We do Row-based, GTID based replication (gtid_mode ON, enforce_gtid_consistency ON)
I was able to resume replication by setting slave_exec_mode to IDEMPOTENT temporarily. …
- 119
0
votes
Accepted
What could cause replication to break on MySQL when replicating from 5.7.40 to 8.0 replica
We enabled binary logs and were able to figure this out when it happened again. The replica had read_only=0 and an application level bug was doing writes in extremely rare scenarios.
- 119