[MDEV-20249] rocksdb.optimize_table fails: sst file reduction was not enough Created: 2019-08-04  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - RocksDB, Tests
Affects Version/s: 10.2, 10.3, 10.4
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Petrunia
Resolution: Unresolved Votes: 1
Labels: None


 Description   

The failure looks like this:

https://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/19325/steps/mtr_ps/logs/stdio/text

rocksdb.optimize_table 'write_prepared'  w1 [ fail ]
        Test ended at 2019-07-26 04:08:03
 
CURRENT_TEST: rocksdb.optimize_table
--- /mnt/buildbot/build/mariadb-10.3.17/storage/rocksdb/mysql-test/rocksdb/r/optimize_table.result	2019-07-26 01:32:33.000000000 -0400
+++ /mnt/buildbot/build/mariadb-10.3.17/storage/rocksdb/mysql-test/rocksdb/r/optimize_table.reject	2019-07-26 04:08:03.241689846 -0400
@@ -40,7 +40,7 @@
 optimize table t4;
 Table	Op	Msg_type	Msg_text
 test.t4	optimize	status	OK
-sst file reduction ok
+sst file reduction was not enough 8596599 -> 8245954 (minimum 1000kb)
 optimize table t6;
 Table	Op	Msg_type	Msg_text
 test.t6	optimize	status	OK
 
mysqltest: Result length mismatch
 
 - saving '/mnt/buildbot/build/mariadb-10.3.17/mysql-test/var/1/log/rocksdb.optimize_table-write_prepared/' to '/mnt/buildbot/build/mariadb-10.3.17/mysql-test/var/log/rocksdb.optimize_table-write_prepared/'
 
Retrying test rocksdb.optimize_table, attempt(2/3)...

The testcase has:

source optimize_table.inc;
optimize table t1;
source optimize_table.inc;
optimize table t3;
source optimize_table.inc;
optimize table t4;
source optimize_table.inc;
optimize table t6;
source optimize_table.inc;

The failure always happens after table t4:

 Table	Op	Msg_type	Msg_text
 test.t4	optimize	status	OK
-sst file reduction ok
+sst file reduction was not enough 8596599 -> 8245954 (minimum 1000kb)
 optimize table t6;
 Table	Op	Msg_type	Msg_text
 test.t6	optimize	status	OK


Generated at Thu Feb 08 08:58:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.