• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

MyISAM / InnoDB

dutchbb

Well-known member
#3
Hm.. it's mostly MyISAM and a few Memory. This is what I run

MySQL
Server version: 5.5.38-0ubuntu0.14.04.1
nginx/1.4.6
MySQL client version: 5.5.38

phpMyAdmin
Version: 3.4.3.1

I thought InnoDB is supported since v5.5? Should I upgrade the server before installing/importing XF for the production site?
 
Last edited:

dutchbb

Well-known member
#5
Thanks. My webhosts said that with the version of MySQL I'm using (libmysql - 5.5.38), innodb is not well supported and should not be the default.

He recommended Mariadb 10 for better support.

Another thing, I removed 'skip_innodb' from my.cnf and installed XF again. It still created MyISAM tables. I guess for now I just use that database.
 

dutchbb

Well-known member
#12
Most likely because they have
Code:
default-storage-engine = MyISAM
in the my.cnf. As @RoldanLT indicated - change it to InnoDB and restart the mysql service. If you use CentMin Mod, I noticed that it ships with the my.cnf using MyISAM as the default engine via the my.cnf.
Yeah correct, my old host probably set that.
 
Last edited:

eva2000

Well-known member
#14
Yeah, but then you get those like me who run Wordpress, IPS 4, MyBB, XenForo, CopperMine Gallery, and a few other things that don't look for a specific setup for CentMin since we run several on one system. :p
yeah got that covered in Getting Started Guide Step 11 :) ;)
Note: default /etc/my.cnf sets default storage engine to MyISAM (default-storage-engine = MyISAM). If you want to use InnoDB storage engine tables, set in /etc/my.cnf, default-storage-engine = InnoDB and restart MySQL server.
 

ForumCube

Active member
#17
He recommended Mariadb 10 for better support.
Directly moving to MariaDB 10 not sounds like a good idea. If you're currently using MySQL 5.5.38 then you should move to MariaDB 5.5.x. As that would be just drop-in replacement. You can upgrade to MariaDB 10 in afterwards.
 
#18
We run a cron to MySQL dump all DBs in our server. Recently during the time this cron is running, our host noticed that there were locked tables in our XF database that caused all Apache connections to fill-up.

So hosting is recommending to convert all tables using MyISAM to InnoDB, they are:
|xf_search_index | MyISAM |
| xf_session | MyISAM |
| xf_session_admin | MyISAM |

We are running MySQL 5.6, that allows InnoDB engines to support Full Indexes. So they are asking to convert all MyISAM tables to InnoDB and leave those memory tables as it is.

1. Is it ok to convert all tables using MyISAM to InnoDB?
2. Other than support for full indexes, is there any other need to have them use MyISAM?
3. Can the conversion from MyISAM to InnoDB happen when the community is up and running?

@Brogan , I sent a conversation about the same. Please revert. Thank you
 

Brogan

XenForo moderator
Staff member
#19
InnoDB full text search has different behaviour to MyISAM full text search.
We can't recommend changing the table types and can only officially support the (default) MyISAM-based search.

@Brogan , I sent a conversation about the same. Please revert. Thank you
For future reference, I don't provide support via conversation.
Support requests should be posted in the relevant forum or via ticket.