[MDEV-27037] Mysqlbinlog should output a warning if EOF is found before its stop condition - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5(EOL), 10.6, 10.7(EOL)
Fix Version/s: 10.5.27, 10.6.20, 10.11.10, 11.2.6, 11.4.4
Component/s: Replication
Labels:
None

Description

In the event that mysqlbinlog finishes processing its input logs and did not reach the boundary provided by --stop-position, it should provide a warning. This to facilitate a script/wrapper which can accurately report on the progress of mysqlbinlog.

See PR-1855 for more details.

Attachments

Issue Links

causes

MDEV-35528 mariadb-binlog cannot process more than 1 logfiles when --stop-datetime is specified

Closed

MDEV-35900 mariadb-binlog reports nonsense warning with --stop-datetime in pitr

Closed

relates to

MDEV-30128 remove support for 5.1- replication events

Closed

MDEV-35694 Mysqlbinlog --stop-position should warn if EOF not reached with --read-from-remote-server

Closed

split from

MDEV-26188 Extend mysqlbinlog with argument --progress-log

Closed

split to

MDEV-34614 mysqlbinlog warn on EOF before GTID in --stop-position

Closed

(1 split to)

Activity

People

Assignee:: Brandon Nesterenko

Reporter:: Brandon Nesterenko

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2021-11-12 15:55

Updated:: 2025-09-02 21:57

Resolved:: 2024-09-12 12:44

Time Tracking

Estimated:

1.5d

Remaining:

Logged:

4.25h

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.