diff options
| author | Sergei Golubchik <sergii@pisem.net> | 2013-12-15 11:31:57 +0100 |
|---|---|---|
| committer | Sergei Golubchik <sergii@pisem.net> | 2013-12-15 11:31:57 +0100 |
| commit | 47b615d84bd41876d7a0838d8193b5ac31a5ff3d (patch) | |
| tree | 189b93ae22d7124a3c83e46d34900a5237acb731 | |
| parent | e68bccc743ddd5ee9b0e47ff73b57d088f015f17 (diff) | |
| download | mariadb-git-47b615d84bd41876d7a0838d8193b5ac31a5ff3d.tar.gz | |
Fix tokudb.hotindex-insert-bigchar failure in buildbot.
This test needs at least 320M for tokudb-max-lock-memory.
Normally tokudb-max-lock-memory is auto-sized to be 1/16th
of the available RAM size, and many our test VMs have 4G of RAM.
| -rw-r--r-- | storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt b/storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt new file mode 100644 index 00000000000..d76fda471ca --- /dev/null +++ b/storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt @@ -0,0 +1 @@ +--loose-tokudb-max-lock-memory=320M |