[MDEV-8574] Running RESET MASTER TO n with too big n breaks binary logging Created: 2015-08-07  Updated: 2015-08-13

Status: Confirmed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1.6
Fix Version/s: 10.1

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-8469 Add RESET MASTER TO x to allow specif... Closed

 Description   

MariaDB [test]> show binary logs;
+------------------+-----------+
| Log_name         | File_size |
+------------------+-----------+
| mysql-bin.000001 |       312 |
+------------------+-----------+
1 row in set (0.00 sec)
 
MariaDB [test]> reset master to 2147483647;
Query OK, 0 rows affected (0.36 sec)
 
MariaDB [test]> show binary logs;
+----------------------+-----------+
| Log_name             | File_size |
+----------------------+-----------+
| mysql-bin.2147483647 |       316 |
+----------------------+-----------+
1 row in set (0.00 sec)
 
# So far, so good...

MariaDB [test]> reset master to 2147483648;
ERROR 1098 (HY000): Can't generate a unique log-filename mysql-bin.(1-999)
 
MariaDB [test]> show binary logs;
Empty set (0.00 sec)
 
MariaDB [test]> reset master to 1;
ERROR 1373 (HY000): Target log not found in binlog index
MariaDB [test]> reset master;
ERROR 1373 (HY000): Target log not found in binlog index
MariaDB [test]> create table t1 (i int);
ERROR 3 (HY000): Error writing file 'UNOPENED' (Errcode: 9 "Bad file descriptor")


Generated at Thu Feb 08 07:28:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.