Drizzle 7.1.32-rc

Milestone information

Vijay Samuel
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon drizzle-7.1.32-rc.tar.gz (md5, sig) Source code tarball Drizzle 7.1.32-rc 221
last downloaded 8 weeks ago
Total downloads: 221

Release notes 

Note: See http://blog.drizzle.org/2012/03/24/1239/ for the same release notes with clickable links

This is the third and hopefully final Release candidate for Drizzle 7.1

Tar ball, Debian package and RPMs available.
Changes since previous release include:

* libdrizzle is no longer installed by these packages. To install libdrizzle, see lp:libdrizzle launchpad project. Libdrizzle so-version was bumped to 4.0.0.
* Removed Transaction Log (includes drizzletrx command line utility) and Replication Dictionary (Brian Aker)

Bugs and other minor fixes:

* Bug fixed: The Regex Policy plugin could consume unbounded amounts of memory, which could be used for denial of service attacks. (Clint Byrum.)
* Bug fixed: Drizzled could crash when filesystem permissions cause writing a pid file to fail. (Brian Aker)
* Bug fixed: An undocumented ipv6_function was enabled and could crash drizzled if called - the function was disabled. (Fixed by Henrik Ingo.)
* Bug fixed: In master master setup, slave plugin would try to apply transactions originating from itself. (Joe Daly)
* Bug fixed: Fix performance regression introduced with catalog being added to key. (Brian Aker)
* Bug fixed: actually return the next exception in Exception::getNextException() & Fix for execute parser to recognize escaped semicolons. (David Shrewsbury)
* Bug fixed: A typo in assertion causing false positive failure with log > 4GB.
* Updated docs. Check out comprehensive replication documentation! (Daniel Nichter, Henrik Ingo, Muhammad Umair, Brian Aker, et.al.)
* Cleanups to drizzle and drizzled --help output and error messages. Standardize plugin names. (Daniel Nichter, Mohit Srivastava)
* Updates and cleanups to the Kewpie testing suite. Enable more automated CI process. (Patrick Crews, Olaf van der Spek)

Changes in Drizzle 7.1 series since Drizzle 7 include:

- Multi-master replication
- Servers are identified with UUID in replication
- HTTP JSON interface available (experimental)
- Percona Innodb patches merged
- Xtrabackup in-tree
- IPV6 data type available
- Query log plugin
- Log output to syslog is enabled by default
- Ability to publish transactions to zeromq and rabbitmq
- Improvements to logging stats plugin
- Native multi-tenancy (database virtualization) support (catalogs)
- Removal of drizzleadmin utility (you can now do all administration from drizzle client itself)
- Removal of HailDB engine
- Revamped testing system Kewpie all-inclusive with suites of randgen, sysbench, sql-bench, and crashme tests
- Continued code refactoring & various bug fixes

Installing Drizzle 7.1.32-rc

The source tar package is available from our Launchpad download area. Please see the manual on how to install Drizzle 7.1.32-rc from source tar package.

The Ubuntu packages are available from the Drizzle PPA. Instructions on how to install from the PPA are in the Drizzle manual.

CentOS 6 packages are available from download.drizzle.org. Instructions on how to install them with yum are in the Drizzle manual.

Note: For Drizzle 7.1.32-rc, only 64-bit packages were built for RedHat/Centos. Please let us know if there is demand for 32-bit packages (such as by commenting to this blog post.)

Known issues

All of the optional plugins are packaged in their own package. These are named drizzle-plugin-*. If a plugin is installed, it is also configured to load by default. (see /etc/drizzle/conf.d/pluginname.cnf) However, not all plugins actually work without further configuration. These plugins will cause the server startup to fail. The workaround is to either configure the plugin to work, or uninstall it if you don't want to use it. (Related blueprint) In short, you should only install the plugins you want to use. Don't install all available plugins.

Please post bugs on the Drizzle bug tracker and questions and general feedback to drizzle-discuss mailing list.


This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.