Posts Tagged ‘XtraDB’

MariaDB 10.1.3 Overview and Highlights

Thursday, March 5th, 2015

MariaDB 10.1.3 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.1.3/

This is the 1st beta, and 4th overall, release of MariaDB 10.1, so there are a lot of new changes, functionalities added, defaults changed, and many bugs fixed (I counted 420 – 117 in 10.1.2 & 637 in 10.1.1, fwiw).

Since it’s beta, I’ll only cover the major changes and additions, and omit covering general bug fixes (feel free to browse them all here).

To me, these are the highlights of the new features:

Of course it goes without saying that do not use this for production systems as it is only the 1st beta release. However, I definitely recommend installing it on a test server and giving it a go, test-drive the new features, throw some load at it, try to break it, and so forth.

You can read more about the 10.1.3 release here:

https://mariadb.com/kb/en/mariadb-1013-release-notes/

And if interested, you can review the full list of changes in 10.1.3 (changelogs) here:

https://mariadb.com/kb/en/mariadb-1013-changelog/

Hope this helps.

 

MariaDB 5.5.42 Overview and Highlights

Thursday, March 5th, 2015

MariaDB 5.5.42 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.42/

This is a maintenance release, and so there were not too many changes at all and only 3 changes (enhancements) I felt noteworthy:

  • The new version of the Audit Plugin is 1.2 is included with the following new features:
    • In the audit log passwords are now masked, i.e. the password characters are replaced with asterisks.
    • It’s now possible to filter logging to include only DDL (CREATE, ALTER, etc.) or DML (INSERT, UPDATE, etc.) statements.
    • For more information please refer to the About the MariaDB Audit Plugin page. The plugin is disabled by default.
  • With this release we introduce a low-level Client API. Applications, linked with libmysqlclient client library can use these functions to read and parse raw protocol packets:
    • unsigned long mysql_net_read_packet(MYSQL *mysql);
    • unsigned long mysql_net_field_length(unsigned char **packet);
  • Includes all bugfixes and updates from MySQL 5.5.42 (MySQL 5.5.42 Overview and Highlights)
  • TokuDB upgraded to 7.5.5

So there are no real crucial fixes requiring an upgrade, however, if you’re running the audit plugin, or TokuDB, or you want the benefits of the new fixes in general, then you should consider an upgrade.

If interested, the official MariaDB 5.5.42 release notes are here:

https://mariadb.com/kb/en/mariadb/development/release-notes/mariadb-5542-release-notes/

And the full list of fixed bugs and changes in MariaDB 5.5.42 can be found here:

https://mariadb.com/kb/en/mariadb/development/changelogs/mariadb-5542-changelog/

Hope this helps.

 

MariaDB 10.0.17 Overview and Highlights

Wednesday, March 4th, 2015

MariaDB 10.0.17 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.17/

This is the eighth GA release of MariaDB 10.0, and 18th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of new changes to report for this release, but there is a new version of the Audit Plugin and many other engines have been updated as well.

Here are the main items of note:

  1. The new version of the Audit Plugin is 1.2 is included with the following new features:
    • In the audit log passwords are now masked, i.e. the password characters are replaced with asterisks.
    • It’s now possible to filter logging to include only DDL (CREATE, ALTER, etc.) or DML (INSERT, UPDATE, etc.) statements.
    • For more information please refer to the About the MariaDB Audit Plugin page. The plugin is disabled by default.
  2. InnoDB upgraded to 5.6.23
  3. XtraDB upgraded to 5.6.22-72.0
  4. TokuDB upgraded to 7.5.5
  5. mroonga upgraded to 5.0
  6. Spider upgraded to 3.2.18
  7. Connect upgraded to 1.03.0005
  8. HeidiSQL upgraded to 9.1
  9. –galera-sst-mode option removed from mysqldump (MDEV-7615)
  10. mysqlbinlog –binlog-row-event-max-size support added (MDEV-6703)

Overall, there are no critical nor security related bugs fixes, so that is great. As for upgrading, if you’re using any of the above storage engines or the audit plugin, it would be a good idea to consider upgrading (at least review the fixes applicable to you to determine if they will be worth it or not).

You can read more about the 10.0.17 release here:

https://mariadb.com/kb/en/mariadb-10017-release-notes/

And if interested, you can review the full list of changes in 10.0.17 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10017-changelog/

Hope this helps.

 

MariaDB 10.0.16 Overview and Highlights

Wednesday, March 4th, 2015

MariaDB 10.0.16 was recently released (~1.5 months ago on 1/27/2015 – sorry for the delay on my end – I was just extra busy in my spare time recently), and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.16/

This is the seventh GA release of MariaDB 10.0, and 17th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of changes to report for this release, but there are 2 enhancements of note – one being the JSON table type (still *experimental*) and the other a new variable to aid with index statistics calculations on large tables, as well as some security fixes.

Here are the main items of note:

  1. Updates to the CONNECT handler (supporting the JSON table type) – which is *experimental* currently
  2. The innodb_stats_traditional system variable enables a larger sample of pages for larger tables for the purposes of index statistics calculation.
  3. InnoDB upgraded to 5.6.22
  4. XtraDB upgraded to 5.6.22-71.0
  5. TokuDB upgraded to 7.5.4
  6. Fixes for the following security vulnerabilities:

Given the security fixes, you should plan on upgrading if you’re running a prior version of 10.0.

You can read more about the 10.0.16 release here:

https://mariadb.com/kb/en/mariadb-10016-release-notes/

And if interested, you can review the full list of changes in 10.0.16 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10016-changelog/

Hope this helps.

 

MariaDB 10.1.2 Overview and Highlights

Saturday, January 17th, 2015

MariaDB 10.1.2 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.1.2/

This is the third alpha release of MariaDB 10.1, so there are still a lot of new changes, functionalities added, defaults changed, and many bugs fixed (I counted 117, which is *way* down from the 637 fixed in 10.1.1). Since it’s alpha, I’ll only cover the major changes and additions, and omit covering general bug fixes (feel free to browse them all here).

To me, these are the highlights of the new features:

You can read more about the 10.1.2 release here:

https://mariadb.com/kb/en/mariadb-1012-release-notes/

And if interested, you can review the full list of changes in 10.1.2 (changelogs) here:

https://mariadb.com/kb/en/mariadb-1012-changelog/

Hope this helps.

 

MariaDB 10.0.15 Overview and Highlights

Friday, January 16th, 2015

MariaDB 10.0.15 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.15/

This is the sixth GA release of MariaDB 10.0, and 16th overall release of MariaDB 10.0.

This release has an important InnoDB/XtraDB fix, a new addition, security enhancements (and improvement) – all related to yaSSL, so be sure to check out these fixes if you’re running MariaDB 10.0, and not up to 10.0.15 yet. (MariaDB 10.0 is the current stable series of MariaDB. It is an evolution of the MariaDB 5.5 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6.)

Here are the main items of note:

  1. This release fixes a serious bug in InnoDB and XtraDB that sometimes could cause a hard lock up of the server (MDEV-7026)
  2. This is the first release that includes Mroonga full-text search storage engine.
  3. When compiled with OpenSSL, MariaDB now supports TLSv1.2 protocol. Limit it to TLSv1.2 ciphers only with –ssl_cipher=TLSv1.2. Limit it to SSLv3 ciphers with –ssl-cipher=SSLv3. RPM and DEB packages from MariaDB.org are built with OpenSSL, others (for Windows and generic Linux) are built with yaSSL.
  4. Fixes for the following security vulnerabilities:
  5. Bundled PCRE is upgraded to 8.36
  6. InnoDB upgraded to 5.6.21
  7. XtraDB upgraded to 5.6.21-70.0
  8. TokuDB upgraded to 7.5.3
  9. SphinxSE upgraded to 2.2.6
  10. Updates to the CONNECT handler including:
  11. We now offer openSUSE repos, see the repository configuration tool for details on how to use it.

Given the severe InnoDB/XtraDB bug, if you’re running a prior MariaDB 10.0 version, I’d recommend upgrading (assuming you’re using InnoDB). Likewise, if you’re using SSL. And then there were a number of fixes to other fixes for TokuDB, CONNECT, and Sphinx, so if you’re using those technologies, you may want to consider upgrading as well.

You can read more about the 10.0.15 release here:

https://mariadb.com/kb/en/mariadb-10015-release-notes/

And if interested, you can review the full list of changes in 10.0.15 (changelogs) here:

https://mariadb.com/kb/en/mariadb-10015-changelog/

Hope this helps.

 

MariaDB 5.5.41 Overview and Highlights

Tuesday, January 13th, 2015

MariaDB 5.5.41 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.41/

This is a maintenance release, and so there were not too many changes, *but* please take notice as there are 2 very important bug fixes:

Thus if you’re running pre-5.5.41 and have encountered, or even if you may be prone to, either bug #7026 or #7100, you should plan to upgrade.

If interested, the official MariaDB 5.5.41 release notes are here:

https://mariadb.com/kb/en/mariadb/development/release-notes/mariadb-5541-release-notes/

And the full list of fixed bugs and changes in MariaDB 5.5.41 can be found here:

https://mariadb.com/kb/en/mariadb/development/changelogs/mariadb-5541-changelog/

Hope this helps.

 

Discussing the innodb_log_block_size variable

Tuesday, November 11th, 2014

Not a ground-breaking post here, but if you are interested in knowing more about the innodb_log_block_size variable, or if you use SSD cards and/or large InnoDB log files on ext4, then this is for you.

I’d read about it before briefly before, but didn’t give it too much thought until I ran across the following entry in an error log the other day:

InnoDB: Warning: innodb_log_block_size has been changed
from default value 512. (###EXPERIMENTAL### operation)

This got me wanting to know more.

Basically, this variable changes the size of transaction log records. Generally, the default of 512 is a good value. However, it has been found that setting it to 4096 has been beneficial when using SSD cards. (Note that while it is possible to set this to a value other than 512 or 4096, those are currently the only 2 values that make sense to use.)

Also, it has been found that 4096 is the best setting if you run ext4 along with innodb_flush_method=ALL_O_DIRECT (note both innodb_log_block_size and ALL_O_DIRECT are specific to XtraDB/XtraDB+; read: MariaDB and Percona server).

What is ALL_O_DIRECT and when it is useful?

“ALL_O_DIRECT: use O_DIRECT to open both data and log files, and use fsync() to flush the data files but not the log files. This option is recommended when InnoDB log files are big (more than 8GB), otherwise there might be even a performance degradation.”

http://www.percona.com/…/innodb_io.html#innodb_flush_method

Thus if you’re running large InnoDB log files (8G+) on ext4, you may want to consider ALL_O_DIRECT, and because you’re on ext4, you should set innodb_log_block_size=4096, the default log-block-size in ext4, in order to avoid the unaligned AIO/DIO warnings.

Likewise, if running with SSD cards, you’d likely see a performance improvement with innodb_log_block_size=4096 also.

If interested, there is a bit more about the innodb_log_block_size option here:

https://mariadb.com/…variables/#innodb_log_block_size
http://www.percona.com/…/innodb_io_55.html#innodb_log_block_size

Hope this helps.

 

MariaDB 10.1.1 Overview and Highlights

Saturday, October 25th, 2014

MariaDB 10.1.1 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.1.1/

This is the second alpha release of MariaDB 10.1, so there are a lot of new changes and functionalities added, and many, many bugs fixed (I counted 637). Since it’s alpha, I’ll only cover the major changes and additions, as there are a lot of great new features, and omit covering any of the bug fixes (feel free to browse them all here).

To me, these are the highlights of the new features:

And here are other new features of note:

You can read more about the 10.1.1 release here:

https://mariadb.com/kb/en/mariadb-1011-release-notes/

And if interested, you can review the full list of changes in 10.1.1 (changelogs) here:

https://mariadb.com/kb/en/mariadb-1011-changelog/

Hope this helps.

 

MariaDB 5.5.40 Overview and Highlights

Friday, October 10th, 2014

MariaDB 5.5.40 was recently released (it is the latest MariaDB 5.5), and is available for download here:

https://downloads.mariadb.org/mariadb/5.5.40/

This is a maintenance release, and so there are not too many big changes of note, just a number of normal bug fixes. However, there are a few items worth mentioning:

If interested, the official MariaDB 5.5.40 release notes are here:

https://mariadb.com/kb/en/mariadb/development/release-notes/mariadb-5540-release-notes/

And the full list of fixed bugs and changes in MariaDB 5.5.40 can be found here:

https://mariadb.com/kb/en/mariadb/development/changelogs/mariadb-5540-changelog/

Hope this helps.

 


Period Panties by Period Panteez Menstrual Underwear Menstruation PMS Panty