Today we glad to announce release 1.0.3-4 of our XtraDB storage engine.
Here is a list of enhancements in this release:
- Move to MySQL 5.1.33
- Move to InnoDB plugin 1.0.3
- more reliable replication, innodb_overwrite_relay_log_info patch now included in the release
Percona XtraDB 1.0.3-4 (Sakura) available in source and several binary packages.
XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.
The links at percona still link to 5.1.31 and the ‘deb’ directory is empty at
https://www.percona.com/mysql/5.1.33-4/deb/
Will there be new .deb builds ??
Sander, yes we’ll build deb soon.
Folks, excellent news!!
BTW, source file mysql-5.1.33-xtradb4.tar.gz doesn’t contain XtraDB code, is it normal?..
Rgds,
-Dimitri
Dimitri,
Thank you! We loaded right files now.
Sander,
We uploaded deb package – https://www.percona.com/mysql/5.1.33-4/deb/
Seems to me the rw_lock issue is not fixed completely because I’m hitting a complete xtradb freeze time to time, and mysqld restart is the only solution..
From the mysqld.log:
–Thread 1080 has waited at btr/btr0cur.c line 508 for 241.00 seconds the semaphore:
X-lock on RW-latch at fffffffc72f811f8 created in file buf/buf0buf.c line 683
a writer (thread id 1080) has reserved it in mode wait exclusive
number of readers 0, s_waiters flag 0, x_waiters flag 1, lock_word: 100000
Last time read locked in file btr/btr0cur.c line 508
Last time write locked in file btr/btr0cur.c line 508
All my sessions during the test using a different set of data (different object references) and freeze arrives seems to me when they access different but neighbor rows. This is not happening with InnoDB plugin nor “default” MySQL 5.1.33..
Do you need more info?
Rgds,
-Dimitri
Hello. Thanks for the new release of XtraDB!
I found several issues.
* according to the srpm for RHEL5, it seems to use percona-xtradb-1.0.2-4.tar.gz not 1.0.3-4.
* several undefined references in case of HAVE_REPLICATION and MYSQL_SERVER:
* handler/ha_innodb.cc:2453: undefined reference to
active_mi'init_strvar_from_file(char*, int, st_io_cache*, char const*)’* handler/ha_innodb.cc:1988: undefined reference to
* handler/ha_innodb.cc:1988: undefined reference to
init_intvar_from_file(int*, st_io_cache*, int)'init_strvar_from_file(char*, int, st_io_cache*, char const*)’* handler/ha_innodb.cc:2003: undefined reference to
* handler/ha_innodb.cc:2003: undefined reference to `init_intvar_from_file(int*, st_io_cache*, int)’
Dimitri,
Could you please try the patch lp:~percona-dev/percona-xtradb/rw-lock-fix-trial?
Regards,
Evgeniy
Hi Evgeniy,
it’s too late for me – I have to free my test platform for other customer, will see next time 🙂
For the moment I may only confirm on my tests @16cores:
– XtraDB-4 is not performing better on the read-only workload rather XtraDB-3
– InnoDB plugin-1.0.3 is outperforming XtraDB-3/4 on the read-only now
– XtraDB-3 is outperforming InnoDB plugin-1.0.3 on the read+write workload
I’ll publish my report soon if anybody is interested in.
Rgds,
-Dimitri