So it's like Q4 2011? ;-\Quote:
Originally Posted by InterServed
Printable View
So it's like Q4 2011? ;-\Quote:
Originally Posted by InterServed
+1 from me too. I'm in need of MySQL 5.5 support.
Is it possible to integrate MySQL 5.5 in earlier cPanel versions than 32?
MySQL 5.5.12 Released
MySQL :: MySQL 5.5 Reference Manual :: D.1 Changes in Release 5.5.x (Production)
hmmmmmm!
+1 from me too. I'm in need of MySQL 5.5 support.
MySQL 5.5.13 Released
MySQL :: MySQL 5.5 Reference Manual :: D.1.4 Changes in MySQL 5.5.13 (31 May 2011)
:) I see the updates from mySQL but nothing from cpanel - I am now going to do it manually. Considering cpanel serves the laMp community, why wouldnt they have more resources working on MySQL (the M part of lamp)? Monopoly of sorts?Quote:
Originally Posted by DjiXas
The work for this is complete and ready to go, as soon as cPanel 11.32 is ready for delivery. The only notable changes are we now move /etc/my.cnf temporarily out of the way when upgrading from older versions of MySQL (e.g 5.1 -> 5.5). Once the upgrade is complete we return /etc/my.cnf to its original place.
The treatment of /etc/my.cnf in this way reduces the number of catastrophic problems that can occur when upgrading from older versions of MySQL. In version 5.5. a number of configuration directives were not only removed, but their presence in /etc/my.cnf now cause a fatal error. If this fatal error occurs when mysql_upgrade is running, your MySQL service can be left in a badly broken state.
Please note that this protection is only afforded if you perform the upgrade via the MySQL Upgrade interface in WHM. We no longer support manual upgrades of MySQL (and haven't since we introduced the MySQL Upgrade interface).
If you have specific questions about changes in relation to MySQL 5.5 support, feel free to ask.
How are you dealing with MySQL 5.5.x change to default InnoDB storage engine instead of MyISAM ? In a majority of cases existing MySQL 5.1.x WHM/Cpanel users' apps are MyISAM based but some apps such as vBulletin will auto convert/use InnoDB tables for some tables if InnoDB Storage engine is enabled and without proper InnoDB tuned parameters, will also cause problems.
So do you intend to switch MySQL 5.5. on WHM with my.cnf settings in place to keep MyISAM as default ? And leave it up to the end user who knows what they are doing to convert to and enable InnoDB tables and storage engine ?
for MySQL 5.5.x default my.cnf on WHM ?
When you mean no longer support manual MySQL upgrades, do me mean as in technical support provided for such ? Or you mean WHM 11.32 will technically no longer allow or have the capability for end users to manually upgrade MySQL i.e. switch to MariaDB/Percona if they know how to manually which is what I'm currently doing for MariaDB 5.2.x.Code:skip-innodb
default-storage-engine = MyISAM
sql-mode = NO_ENGINE_SUBSTITUTION
Does the upgrade also handle upgrading MySQL HELP tables which aren't automatically updated http://dev.mysql.com/doc/refman/5.5/...p-support.html ?
ETA on 11.32 ?Quote:
If you upgrade MySQL using a binary distribution, the help tables are not upgraded automatically, but you can upgrade them manually. Locate the fill_help_tables.sql file in the share or share/mysql directory. Change location into that directory and process the file with the mysql client as follows:
shell> mysql -u root mysql < fill_help_tables.sql
You can also obtain the latest fill_help_tables.sql at any time to upgrade your help tables. Download the proper file for your version of MySQL from http://dev.mysql.com/doc/index-other.html. After downloading and uncompressing the file, process it with mysql as described previously.
What version was integrated? 5.5.13?Quote:
Originally Posted by cpanelkenneth
Also, when is 11.32 RELEASE shipping?
MySQL 5.5.14 Released
MySQL :: MySQL 5.5 Reference Manual :: D.1.3 Changes in MySQL 5.5.14 (05 July 2011)
We left the upstream Engine default in place. This means new databases will default to the InnoDB storage engine unless otherwise specified during schema creation.Quote:
Originally Posted by eva2000
Tuning of the database service is left to the system administrator. If there are reasonable suggestions that work for the majority of users we are receptive to reviewing them.Quote:
Originally Posted by eva2000
I'm not sure I fully understand these questions.Quote:
Originally Posted by eva2000
We don't provide technical support for manually upgrading the MySQL version outside of the MySQL Upgrade UI in WHM. This is different than simply upgrading to the latest build of the currently installed version of MySQL. We also don't provide technical support for downgrading the MySQL version.Quote:
Originally Posted by eva2000
As the server owner you are free to disable the MySQL service we provide and install MariaDB, Drizzle or whatever. However our support, both technical and in the cPanel & WHM software, is necessarily limited in that regard.
I have no idea, but will look into it.Quote:
Originally Posted by eva2000
The earliest we would see an 11.32 build for the public is a week or two after 11.30.1 reaches the STABLE tier.Quote:
Originally Posted by eva2000
Version 5.5 was integrated. At this time build 5.5.14 is in our internal test builds.Quote:
Originally Posted by DjiXas
This is unknown. An uneducated guess is that version 11.32 would be promoted to the RELEASE tier sometime mid-August.Quote:
Originally Posted by DjiXas
Hi. Is there any ETA for 11.30 STABLE?Quote:
Originally Posted by cpanelkenneth
Assuming the rest of our quality expectations are met, we're targeting for the very near term (days rather than weeks).Quote:
Originally Posted by Kent Brockman
Well you answered that in your first sentence in my reply in that you intend to leave 5.5.x to default to innodb storage engine. My question rephrased, was if you intend to set 5.5.x to default to myisam storage engine overriding mysql 5.5.x defaults by using these 3 my.cnf optionsQuote:
Originally Posted by cpanelkenneth
This will keep mysql 5.5.x operating like previous mysql 5.0/5.1 defaulting to myisam. This way you can let the end user decide if they want to default to innodb by changing my.cnf toCode:skip-innodb
default-storage-engine = MyISAM
sql-mode = NO_ENGINE_SUBSTITUTION
Can get messy if you leave 5.5 to default to innodb as some scripts don't define the storage engine in their mysql create statements. You'll be getting alot of support tickets asking how to convert innodb tables back to myisam ! Unless, you're prepared to also provide optimisation and tuning advice for innodb related options and performance tuning. As well guides on how to properly backup innodb databases and repair/recovery of corrupted innodb tables and proper handling of innodb shared table space (ibdata1).Code:#skip-innodb
default-storage-engine = InnoDB
sql-mode = NO_ENGINE_SUBSTITUTION
Average joe ain't up to speed on innodb vs myisam differences, so enabling 5.5 to default to innodb storage engine may get messy. Safer method would be to set mysql 5.5 to default to myisam via my.cnf options above. And let those that understand innodb enable it themselves.