MySQL 5.6.13 released

Maybe Im just partial to MyISAM but I would prefer to set MyISAM as default and let scripts make the call if they want innoDB and have it as a alternative...

see I have a site that is a direct clone of another but the 2nd one seems to be missing some of the options in a plugin and I havent yet figured out what the diff would be other than the 1st is all MyISAM and the 2nd is all innoDB.
(1st site was moved to new server where MyISAM was default, 2nd site was installed on new server with innoDB as default)
I did contact the author and he stated he has never studied innoDB or used it before, so what Im going to do is wait til the server is default MyISAM and do a reinstall and see if there are any changes.

I too was worried about the mixed engines and not knowing what would happen, we have had on occasion a loss of Mysql but only for a few seconds, thus wondering if there were any connections to the mixed engines in one DB

a quote from Mr.J
"Remember when hosting used to be fun?"
 
@ditto
Thank you for the explanation, and now would you be so kind as to show us the proper way to set MyISAM as default and innoDB as an option?
being a production server wouldnt want to make a mess of things lol
like a line by line of procedure...?
from what I read or see it doesnt look to much trouble but we have all seen the "simple" thing turn out to be a disaster..:(

Im not sure why innoDB is being set as the default and just what advantages or disadvantages there are but any programmer I have spoke with lately have stated that they build around MyISAM
Thank You all for your time and interests...
 
On my servers running CentOS 6.x 64bit and MySQL 5.6.x, it is as simple as adding the following line to /etc/my.cnf

Code: 
default-storage-engine=MyISAM

... and then restart MySQL

Code: 
service mysqld restart

You don't need to to anything to make InnoDB a option, so long as you do not disable InnoDB in my.cnf, it will be a option (at least on CentOS servers and MySQL 5.5.x and 5.6.x).

At the same time I would like to advice that you regarding InnoDB has the following in /etc/my.cnf (it's been discussed in the forums previously):

Code: 
innodb_file_format=Barracuda
innodb_file_per_table=1

And for those interested, here is everything I have in /etc/my.cnf on all my servers:

Code: 
[mysqld]
local-infile=0
open_files_limit=30000
max_allowed_packet=20M
default-storage-engine=MyISAM
innodb_file_format=Barracuda
innodb_file_per_table=1
performance_schema=off
 
Last edited:
Thank You SO much kind Sir
I really appreciate all your help, Really I do :):):):)
 
ditto said:
On my servers running CentOS 6.x 64bit and MySQL 5.6.x, it is as simple as adding the following line to /etc/my.cnf

Code: 
default-storage-engine=MyISAM

... and then restart MySQL

Code: 
service mysqld restart
Click to expand...
I've just done that on the server used by AndyII (it's a new server, still in testing mode). So we can expect a reply from him soon (I'm out most of the rest of the day).

But I notice you have a very small my.conf file compared to the one I use, which is the one distributed with MySQL for use with large memory systems (the new servers all have 24 GB memory).

Do you suggest that your small file is enough?

Thanks.

Jeff
 
NoBaloney2 said:
[..]
But I notice you have a very small my.conf file compared to the one I use, which is the one distributed with MySQL for use with large memory systems (the new servers all have 24 GB memory).

Do you suggest that your small file is enough?
Click to expand...

I can't say for sure, as I am still learning. My servers has 32GB RAM, and feels good with my current etc/my.cnf. The reason behind it, is because I am afraid that the settings in the default one distributed for large memory system maybe more limited then the default values I get by not using it at all. But I am not sure about this, until I am sure, I will not use any of the templates distributed for my.cnf

So, the reason is that I want the default values from MySQL by not setting the values in etc/my.cnf, so I only set the stuff there wich I want to overrule the default values ...
 
Last edited:
Everything seems to be working fine, re installed the site and all was MyISAM so all good there and I think at one time we needed to change from the standard cnf file and make it large as we were killing the MySQL server with a low memory limit
of course that was a lesser of a machine and this NEW machine may be working a lot less harder than the other was.
Jeff has been teasing me with these 12 core 48GB memory and dual 1TB HD's :cool::mad::eek:
 
The old machine was four-core and 6GB memory; the one we're currently moving from beta to release is eight-core and 24GB memory. I can deliver all the way to 48GB and 12-core as standard machines, but they of course cost quite a bit more :).

We'll stay with our default file for now; if anyone would like a copy, ask me in a week when we've given it more time.

Jeff
 
First I recommend that you add this line to /etc/my.cnf (because performance schema gives overhead and is bad for performance and you don't need it, it was not on as default in 5.5.x, but is on as default on 5.6.x):

Code: 
performance_schema=off

Then edit this file: /usr/local/directadmin/custombuild/options.conf and find the line that say "mysql=5.5" and change it to "mysql=5.6"

Then run this ("./build versions" is only for you to see what versions is available, note it is always needed to do "./build php n" after upgrade of MySQL):

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build versions
./build mysql
./build php n
 
ditto said:
First I recommend that you add this line to /etc/my.cnf (because performance schema gives overhead and is bad for performance and you don't need it, it was not on as default in 5.5.x, but is on as default on 5.6.x):

Code: 
performance_schema=off

Then edit this file: /usr/local/directadmin/custombuild/options.conf and find the line that say "mysql=5.5" and change it to "mysql=5.6"

Then run this ("./build versions" is only for you to see what versions is available, note it is always needed to do "./build php n" after upgrade of MySQL):

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build versions
./build mysql
./build php n
Click to expand...

Thanks, won't it mess my php.ini?
 
No, it will not mess your php.ini. However infrequently custombuild will patch your php.ini with changes (not overwrite it) if there are any needed adjustment. So you should always make backup of your own php.ini, so that you can make a diff and have full control. You must recompile php every time you upgrade mysql, so you do not have a choice. Changes you have added to php.ini will 99.99% of the times not be changed when you do ./build php n - if custombuild make changes to your php.ini, it will only be one or two lines that is changing.
 
Last edited:
I have added mysql=5.6 to options conf but when i type:

Code: 
./build mysql

You cannot install MySQL, because you do not have it set in options.conf file.

Though i have set it!
 
You should not add mysql=5.6 to options.conf, you should CHANGE mysql=5.5 to be mysql=5.6 in options.conf

Then you must run ./build update, please remove mysql=5.6 in options.conf and then CHANGE mysql=5.5 to be mysql=5.6 in options.conf, and then run these commands:

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build versions
./build mysql
./build php n

Just do exactly what I said and you will not have problems.
 
Do you have this in options.conf?:

mysql_inst=no

If so, that is the reason. You must then change it to:

mysql_inst=yes

(I will advice that you hire a server management company or person that specialize in DirectAdmin to help you with server management.)
 
ditto said:
You should not add mysql=5.6 to options.conf, you should CHANGE mysql=5.5 to be mysql=5.6 in options.conf

Then you must run ./build update, please remove mysql=5.6 in options.conf and then CHANGE mysql=5.5 to be mysql=5.6 in options.conf, and then run these commands:

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build versions
./build mysql
./build php n

Just do exactly what I said and you will not have problems.
Click to expand...

I mean i have changed (not added), sorry.

Code: 
#Possible values - 5.1, 5.5, 5.6
mysql=5.6
mysql_inst=no
mysql_backup=yes
mysql_backup_dir=/usr/local/directadmin/custombuild/mysql_backups

And it still says that i didn't changed lol
 
Please see my previous reply. You must change mysql_inst=no to be mysql_inst=yes
 
You must log in or register to reply here.
Back
Top