[MDEV-20990] Binlog-pos is not empty on fresh install Created: 2019-11-06  Updated: 2023-12-15

Status: Open
Project: MariaDB Server
Component/s: Documentation, Replication
Affects Version/s: 10.2.27, 10.1.41
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Ragul Assignee: Joe Cotellese
Resolution: Unresolved Votes: 2
Labels: None
Environment:

Centos Rhel 7

Attachments: Zip Archive binary-log.10.2.18.zip     Zip Archive binary-log.10.2.27.zip     PNG File binlog_diff.PNG     PNG File image-2019-11-06-12-23-49-696.png     File mariaTest.sh    
Issue Links:
PartOf

 Description   

On mysql fresh installation of 10.2.27 & 10.2.18, I could see the weird behavior

As per the note found in https://mariadb.com/kb/en/library/gtid/#gtid_binlog_pos.

when the binlog is empty (such as on a fresh install or after RESET MASTER), there are no event groups written in any replication domain, so in this case the value of gtid_binlog_pos will be the *empty string*.

Binlog-pos should be empty string on fresh install but why the value is set as 0-1-1 in mariaDB-10.2.27



 Comments   
Comment by Senthil Kumar Sekar [ 2019-11-14 ]

Can one pls check and comment why the default value of gtid_binlog_pos is not an empty string now?
It also impacts us ?

Comment by Elena Stepanova [ 2019-11-18 ]

A good start would be to check the contents of the binary log using mysqlbinlog, to see if there is anything. Could you do that? Maybe the installation procedure executes something that is written into the log.

Comment by Ragul [ 2019-11-19 ]

Thanks @Elena

I could see some difference between the binary-log file generated by two versions of MariaDB (10.2.18 & 10.2.27) But I don't have an idea why such difference occurred now.

Attaching the binary-log of both version binary-log.10.2.18.zip binary-log.10.2.27.zip .

Can u please help with this?

Comment by Ragul [ 2019-11-22 ]

On reading the binlog, I could see a DDL transaction is considered at the start of the installation for 10.2.27 MariaDB (created a test database) ...while it is not considered in 10.2.18 MariaDB

Comment by Elena Stepanova [ 2019-11-25 ]

Thanks for the info.
Indeed, the statement was added in 10.2.24 (also 10.1.39, 10.3.15, 10.4.5) as a part of this commit:

commit 3db6de33b2b47a3c31bc8f8deb721abe0c5b0e1c
 
Author: Sergei Golubchik
 
Date:   Wed Apr 17 14:53:30 2019 +0200
 
 
 
    MDEV-17640 UMASK_DIR configuration for mysql_install_db is not applied to mysql database
 
    
    create mysql and test databases with SQL, not mkdir.

Apparently, the documentation note needs to be updated.

Comment by Julien Fritsch [ 2021-09-22 ]

jacob.moorman from our discussion, I decided to reassign Kenneth's ticket to you?

Generated at Thu Feb 08 09:03:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.