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
Summary | status variable for Slave_skipped_errors | [PATCH] status variable for Slave_skipped_errors |
Fix Version/s | 10.1 [ 16100 ] |
Assignee | Kristian Nielsen [ knielsen ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Priority | Minor [ 4 ] | Major [ 3 ] |
Status | Stalled [ 10000 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Status | Stalled [ 10000 ] | In Progress [ 3 ] |
Fix Version/s | 10.1.4 [ 18400 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v2 [ 58718 ] | MariaDB v3 [ 65294 ] |
Workflow | MariaDB v3 [ 65294 ] | MariaDB v4 [ 132467 ] |