/ Register

Learn about Centmin Mod LEMP Stack today
Become a Member

Include option to enable InnoDB during setup

Discussion in 'Feature Requests & Suggestions' started by deltahf, Mar 2, 2015.

Tags:
Previous Thread Next Thread
Loading...
  1. Mar 2, 2015 #1
    deltahf

    deltahf Premium Member Premium Member

    585
    264
    63
    Jun 8, 2014
    Ratings:
    +486
    Local Time:
    10:43 AM
    I was looking into tuning MySQL, when I suddenly looked at my.cnf and realized that skip-innodb was uncommented (And I've been running my big XenForo board on MyISAM all this time...no wonder DB performance is shaky under load! :banghead:) I immediately realized that I had forgotten to change this setting when I moved to Linode last year, and I suppose that when I moved my InnoDB databases over, it just quietly restored the tables into MyISAM without objection.

    I'm sure InnoDB is disabled for a reason in Centminmod, but this could catch a lot of novice users off guard who may not touch their my.cnf. I think it would be a good idea to mention this somewhere in the setup, and to provide a quick option for whether or not they would like InnoDB enabled by default or not. :)
     
  2. Mar 2, 2015 #2
    eva2000

    eva2000 Administrator Staff Member

    54,068
    12,176
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,734
    Local Time:
    1:43 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Yeah .07 would have InnoDB disabled by default as it goes back to fact Centmin Mod LEMP stack was originally made for low memory systems 256-512MB VPS and low disk space <20GB VPS. So enabling InnoDB would consume excessive memory and disk space. The other reason is, InnoDB engine enabling or using InnoDB tables doesn't automatically give better performance unless you tune your MySQL InnoDB specific settings and that is different to MyISAM table tuning. If folks aren't aware of this, can get messy with InnoDB tables as InnoDB table repair, backup and maintenance is different to MyISAM. Folks can end up corrupting their data if they do not know what they are doing on InnoDB tables. e.g. backing up and restoring individual InnoDB data files like they would MyISAM data files would corrupt their data etc.

    It's much safer, for folks who need InnoDB to convert tables from MyISAM to InnoDB and have the InnoDB know-how. Then for folks who don't have a clue on differences between MyISAM and InnoDB table management etc to permanently corrupt their databases with no avenue for data recovery :)

    But yes, will figure out where in the initial install process, I can mention this :)

    However, with Centmin Mod .08 beta MariaDB 10 default requires InnoDB enabled. So guess that safeguard doesn't play out :eek:
     
  3. Jun 3, 2015 #3
    jeffwidman

    jeffwidman Active Member

    152
    27
    28
    Dec 3, 2014
    Ratings:
    +51
    Local Time:
    7:43 AM
    I would argue the opposite--the biggest problem with MyISAM is that it isn't fully ACID compliant. There's a lot of horror stories of MyISAM tables becoming corrupted and losing data in the course of normal operation... without the admin even touching the db settings at all.
     
  4. Jun 3, 2015 #4
    eva2000

    eva2000 Administrator Staff Member

    54,068
    12,176
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,734
    Local Time:
    1:43 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    yeah well hard to say, in 15yrs of using MyISAM i have never had tabe corruption that resulted in loss data. Really comes down to not what you use (myisam or innodb) but who and how you use it :)

     
  5. Jun 3, 2015 #5
    rdan

    rdan Well-Known Member

    5,443
    1,402
    113
    May 25, 2014
    Ratings:
    +2,194
    Local Time:
    11:43 PM
    Mainline
    10.2
    VB only works with MyIsam? :D
     
  6. Jun 3, 2015 #6
    eva2000

    eva2000 Administrator Staff Member

    54,068
    12,176
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,734
    Local Time:
    1:43 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    vB4+ had extended InnoDB support
     
Previous Thread Next Thread
Loading...

.