metadata error with MariaDB 11.4

[dveeden]

What did you do?

Setup DM with MariaDB 11.4

What did you expect to see?

"Message": "parse mydumper metadata error: [code=11123:class=functional:scope=upstream:level=low], Message: didn't found binlog location in dumped metadata file metadata, Workaround: Please check log of dump unit, there maybe errors when read upstream binlog status, metadata: Started dump at: 2024-11-08 16:30:53\nSHOW BINARY LOG STATUS:\n\tLog: mysqld-bin.000002\n\tPos: 329\n\tGTID:\n\nFinished dump at: 2024-11-08 16:30:54\n",

What did you see instead?

No response

Versions of the cluster

master @ 64decf6

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

[dveeden]

/label MariaDB

[lance6716]

From error message we know the content is

Started dump at: 2024-11-08 16:30:53
SHOW BINARY LOG STATUS:
	Log: mysqld-bin.000002
	Pos: 329
	GTID:

Finished dump at: 2024-11-08 16:30:54

caused by

tiflow/dm/pkg/dumpling/utils.go

Lines 125 to 146 in 64decf6

	switch line {
	case "SHOW MASTER STATUS:":
	if err3 := parsePosAndGTID(&pos, &gtidStr); err3 != nil {
	return nil, nil, err3
	}
	case "SHOW SLAVE STATUS:":
	// ref: https://github.com/maxbube/mydumper/blob/master/mydumper.c#L434
	for {
	line, err3 := br.ReadString('\n')
	if err3 != nil {
	return nil, nil, err3
	}
	line = strings.TrimSpace(line)
	if len(line) == 0 {
	break
	}
	}
	case "SHOW MASTER STATUS: /* AFTER CONNECTION POOL ESTABLISHED */":
	useLocation2 = true
	if err3 := parsePosAndGTID(&pos2, &gtidStr2); err3 != nil {
	return nil, nil, err3
	}

we didn't handle SHOW BINARY LOG STATUS

[joccau]

/assign

[joccau]

What did you do?

Setup DM with MariaDB 11.4

What did you expect to see?

"Message": "parse mydumper metadata error: [code=11123:class=functional:scope=upstream:level=low], Message: didn't found binlog location in dumped metadata file metadata, Workaround: Please check log of dump unit, there maybe errors when read upstream binlog status, metadata: Started dump at: 2024-11-08 16:30:53\nSHOW BINARY LOG STATUS:\n\tLog: mysqld-bin.000002\n\tPos: 329\n\tGTID:\n\nFinished dump at: 2024-11-08 16:30:54\n",

What did you see instead?

No response

Versions of the cluster

master @ 64decf6

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

Is the answers to question reversed for What did you expect to see? and What did you see instead? ?

[dveeden]

@joccau yes indeed. When setting up DM with MariaDB 11.4 I would expect it to work, but what I see instead is this error that mentions SHOW BINARY LOG STATUS.

I'm not sure it should mention SHOW BINARY LOG STATUS as that's for recent versions of MySQL and with MariaDB I would expect SHOW MASTER STATUS.