Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
From MDEV-6457 was a suggestion for a status variable to report slave_skipped_errors.
Wasn't sure if I needed a mutex around this to account for potential parallel replication error faults occurring at the same time (probably yes).
attached patch against 10.0.15-trunk
Attachments
Issue Links
- relates to
-
MDEV-6457 preserve slave_skip_errors binlog events to own binlog
-
- Open
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
71d 2h 47m | 1 |
|
3h 9m | 2 |
|
39d 21h 50m | 2 |
|
19h 2m | 1 |