Archive for the ‘Uncategorized’ Category

Drizzle.org was unavailable today, domain now successfully transferred to SPI

Tuesday, November 8th, 2011

The entire drizzle.org domain was unavailable for about 10 hours today. This made our website, documentation, jenkins master and mail server inaccessible. On the other hand as we use public services such as Launchpad and Freenode for code repository, bug tracking, mailing list and IRC, this meant that development work continued as active as ever - in fact I think it was the most active day on IRC #drizzle channel in a while!

The DNS outage was related to our transferring of the drizzle.org domain from an individual Drizzle developer to Software in the Public Interest, Inc, our umbrella non-profit corporation. We don't know exactly why, but something went wrong between the registrars, so that the Whois record listed Tucows, the sponsoring registrar used by SPI, as the new registrar, but all other information was still pointing to the old registrar, including some Godaddy nameservers. As Godaddy eventually stopped answering DNS queries for drizzle.org - as they should - the drizzle.org domain became unavailable. 10 hours later the issue was fixed, and the correct SPI nameservers started to propagate through the DNS system. At the time of this writing, everything should have been working normally for some hours already.

And yes, in related news, drizzle.org is now transfered to the ownership of Software in the Public Interest. This is yet another step in our process of becoming a solid non-profit community project, with fiscal services provided by the SPI. So far the experience has been enjoyable and we've really felt a warm welcome into the family of SPI hosted free and open source software projects.

On that note I'd like to thank Ganneff, Solver, Hydroxide and weasel from the #spi  channel for actively helping in troubleshooting and fixing the problem today.

Drizzle at Percona Live

Tuesday, September 27th, 2011

Thinking of attending the upcoming Percona Live event in London, but not yet registered?  Use discount code DrizzlePLUK and save 40 pounds off normal registration.

Community members Henrik Ingo and Stewart Smith will be there and both will be presenting on Drizzle.  Hope to see you there!

 

Drizzle 2011.04.15 tarball has been released

Tuesday, April 12th, 2011

Drizzle source tarball, version 2011.04.15 has been released.
This is a release of the Fremont series and is a development release.  Our stable GA release can be found here.  Future releases to the Elliott series will be announced appropriately.

In this release:

  • xtrabackup is in the tree
  • transaction_reader utility (for scanning / debugging/ generating SQL from the trx log) included in tarballs
  • openstack can now run via Drizzle
  • various bug fixes

The Drizzle download file can be found here.

Drizzle 2011.03.14 tarball has been released

Tuesday, March 29th, 2011

Drizzle source tarball, version 2011.03.14 has been released.
This is the first release of the Fremont series and is a development release.  Our stable GA release can be found here.  Future releases to the Elliott series will be announced appropriately.
In this release:

  • multi-master replication available via slave plugin. Single master replication works as it has previously (some changes to config file required)
  • split libdrizzle v 1.0 and 2.0
  • Code refactoring (Thanks to Olaf van der Spek for his efforts here!)
  • Code cleanup (mysys, etc)
  • Various bug fixes

 

Look for xtrabackup soon!

The Drizzle download file can be found here.

FreeBSD support is not going away just yet - UPDATED

Monday, March 28th, 2011

Hi everyone! Just wanted to announce that Drizzle will stop supporting FreeBSD moving forward. We will continue to build on the platform, but will no longer run our test suite.

If someone in the community wants to take over maintenance of Drizzle on FreeBSD, we would be delighted! It is simply a matter of it taking too much of our limited time to keep things running on this system.

UPDATE:  As you can see below, we've had the FreeBSD port maintainer offer to help us keep things going.  Go open source! : )

Drizzle GA roundup

Monday, March 21st, 2011

Hi there.  In case you happened to miss it, Drizzle went GA ; )

The response has been tremendous...it is all kinds of rewarding to see new faces in IRC and to have feedback from new users.  We've seen lots of new visitors to the blog and our download numbers have been most satisfying.  Thank you for giving Drizzle a spin.

Here are some quick bits of news that you may have missed:

We have some very, very interesting things cooking up for the 2011 MySQL User's Conference and we hope to see you there.  Please remember to sign up for Drizzle Developer Day or Google Summer of Code if you are interested...time is running out.

We'd also really love to have more feedback on the software.  Any thoughts from anyone deploying Drizzle?  Any questions / issues from trying it out?  Anything else?  If so, IRC, emails and launchpad will help put us in touch : )

Drizzle sessions at the 2011 MySQL UC

Monday, March 7th, 2011

There are a large number of Drizzle sessions at this years' MySQL UC.  If you want to know more about what you'll be using instead of MySQL in the very near future, come and check them out ; )

The team will be blogging individually about their various presentations in greater detail in the future, so keep an eye out on Planet Drizzle!

Additionally, the Friday after the conference will be Drizzle Developer Day .  It will be a good opportunity to learn more, provide feedback, etc

Here is a 25% discount code to use in case you haven't registered yet:  mys11fsd: http://oreil.ly/goaqst.

Drizzle 2010.12.05 tarball has been released

Tuesday, December 7th, 2010

Drizzle source tarball, version 2010.12.05 beta has been released.
In this release:

  • innobase plugin update to innodbase 1.1.2 from MySQL 5.5.6-rc
  • continued work on sys_vars
  • continued work on user-level locks
  • added shutdown command to the command line client - can shut down an instance you are connected to
  • more work on concurrency testing and functions (kill, execute, wait, etc)
  • continued code cleanup
  • various bug fixes

The Drizzle download file can be found here

HailDB version 2.2.0 has been released

Wednesday, September 29th, 2010

HailDB source tarball, version 2.2.0 has been released.

In this release:

- Remove dict_table_check_for_dup_indexes(). It is now unneeded, there is a check in api/ for this, so embedded_innodb never had this problem.
- file_io_threads is deprecated but still exists - we now issue a warning about this if a user attempts to set it.
- fix of rmplint errors
- import fix for IMPORT TABLESPACE of compressed tables

The HailDB download file can be found here

Testing Drizzle's transaction log

Friday, July 9th, 2010
One of my first tasks on the Drizzle team was to check out the transaction log, part of Jay Pipes' work on replication.  We needed to make sure that the log itself was rock-solid and that any code written to use it would have a worthy foundation.  As it turns out, some people are really interested in getting replication working ; )



As can be seen from the blueprint, testing will involve two of our main testing tools, the randgen and our standard test suite (test-run, dtr, etc).  So far, our efforts have been concentrated on writing tests for the test suite.  These tests have largely consisted of executing queries that should make it into the transaction log, then using the UDF print_transaction_message($log_file,$log_offset) to examine the log's contents.  The tests can be found here and executed with ./test-run --suite=transaction_log.  (NOTE:  The tests themselves are largely complete, but our expected results are not yet finalized / correct due to the bugs noted below).  I'd like to extend a special thanks to Joe Daly for his help in writing these tests and finding some bugs in the log.



While we have tested all of the available data types and basic transactions and they are looking quite solid, our efforts have still turned up some interesting bugs:
(this list is maintained at the launchpad blueprint noted above)


  • Bug #594873: transaction log incorrectly records NULL INSERT into an ENUM as the first permissible value
  • Bug #594876: transaction log not differentiating NULL values and empty string for char columns
  • Bug #596972: transaction log logging 0 for NULL INTEGER VALUES
  • Bug #599582: Transaction log does not appear to be collecting all information for multi-row REPLACE statements
  • Bug #597910: Transaction log does not appear to be capturing FOREIGN KEY information
  • Bug #599851: Transaction log not capturing CASCADE'd UPDATE data on a table using a foreign key
  • Bug #599952: transaction log attributing statements to wrong tables on multi-table, multi-statement transactions
  • Bug #600032: rollback to savepoint not handled correctly in transaction log
  • Bug #600795: LOAD DATA INFILE INSERTs not registered by the transaction log



The first 3 bugs relate to how the log captures NULL values for various data types and have been traced to a single root cause.  The remaining 6 seem more interesting and serious for replication functionality.  To summarize, the transaction log appears to have trouble with trickier (more complex) transactions.  These include changes propagated via a foreign key, multi-row REPLACE, and multi-table transactions.



Once these bugs have been addressed, we will continue with test development for the randgen.  This will include stress testing the server / log with DDL-generating grammars and validation of the data stored within the log.  Initial experiments with high-volume (10+ threads at 250k queries each) have looked promising (no crashes, locks, major slow downs over time).  In the meantime, we'll be busy with other tasks (dump+restore)



As always, we welcome any feedback, questions, or bug fixes : )
More information on Drizzle testing can be found here.