{"id":2914,"date":"2014-04-22T18:56:02","date_gmt":"2014-04-22T23:56:02","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=2914"},"modified":"2014-04-22T18:56:02","modified_gmt":"2014-04-22T23:56:02","slug":"ubuntu-14-04-some-mysql-ecosystem-notes","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2014\/04\/22\/ubuntu-14-04-some-mysql-ecosystem-notes","title":{"rendered":"Ubuntu 14.04 – some MySQL ecosystem notes"},"content":{"rendered":"

Following my previous post<\/a> on the launch, I just rolled Ubuntu 14.04 LTS on an Amazon EC2 t1.micro instance (not something you expect to run a database server on, for sure – 1 vCPU, 0.613GiB RAM). If you do an apt-cache search mysql<\/tt> you get 435 return result sets with the default configuration (trusty: main & universe).<\/p>\n

If you do apt-get install mysql-server<\/tt>, you get MySQL 5.5. You enter the password of choice, and before you know it, MySQL is installed (a SELECT VERSION()<\/tt> will return\u00a05.5.35-1ubuntu1<\/tt>).<\/p>\n

Next you decide to install MariaDB<\/a>. I run an apt-get install mariadb-server<\/tt>. It pulls in libjemalloc<\/tt> (for TokuDB) and I expect future releases to ship this engine by default. You enter the password, and you get a new message (as pictured).<\/p>\n

\"MariaDB<\/a><\/center>\u00a0<\/p>\n

I verify my test database that I created exists. It does. A SELECT VERSION()<\/tt> returns\u00a05.5.36-MariaDB-1<\/tt>. The innodb_version<\/tt> returns\u00a05.5.36-MariaDB-33.0<\/tt>.<\/p>\n

I\u2019m curious about MySQL 5.6 now. So I run apt-get install mysql-server-5.6<\/tt>. Not so straightforward.\u00a0<\/p>\n

start: Job failed to start\ninvoke-rc.d: initscript mysql, action \"start\" failed.\ndpkg: error processing package mysql-server-5.6 (--configure):\n subprocess installed post-installation script returned error exit status 1\nSetting up mysql-common-5.6 (5.6.16-1~exp1) ...\nProcessing triggers for libc-bin (2.19-0ubuntu6) ...\nErrors were encountered while processing:\n mysql-server-5.6\nE: Sub-process \/usr\/bin\/dpkg returned an error code (1)\n<\/pre>\n
Looks like MySQL 5.6 is more memory hungry\u2026 I edited \/etc\/mysql\/my.cnf<\/tt> to ensure that innodb_buffer_pool_size = 64M<\/tt> (I increased this to 128M and it worked too) was set (there was nothing in the default config) and re-ran apt-get install mysql-server-5.6<\/tt> and it started. My test database was still around ;-)<\/p>\n
I wanted to make sure that MySQL 5.6 isn\u2019t more memory hungry just on that instance so I created yet another clean t1.micro instance and did an apt-get install mysql-server-5.6<\/tt>. Same error. Reported lp#1311387<\/a>.<\/p>\n
Nothing to report in particular about Percona – 5.5.34 Percona XtraDB Cluster (GPL), Release 31.1 (Ubuntu), wsrep_25.9.rXXXX. One thing is for sure – if you’re playing around with the ecosystem, installs and upgrades aren’t exactly straightforward.<\/strong><\/p>\n
Share this:<\/h3>