Do we have to convert MySQL from MYISAM to InnoDB

We have our current version of confluence 6.2.1 upgraded to 6.3.3 and now we get an error

"MyISAM is configured as the default storage engine in your database, wh..."

 Problem there is, this system runs on a managed hosting server with no chance to change to innodb db environments. All tables are already innodb.

Question: is there a way to disable this innodb needed check?

otherwise we can not run confluence anymore.

kindly regards

1 answer

0 votes

No.  You must be using Innodb tables.

However, this is just a warning that your defaults are not suitable.  If your tables really are all Innodb for the confluence database, you can simply ignore it.

No it's not only a warning. after the startup was finished with running, the browser shows the following page:


Bildschirmfoto 2017-09-01 um 07.27.39.png

logfile contains:

..,803 ERROR [localhost-startStop-1] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup MyISAM is configured as the default storage engine in your database, which may result in data integrity issues. Please see for more information.

Ah, right.  It is theoretically possible to run a set of databases differently, so it can be possible to set up one database with Innodb as the default and leave the *global* default as MyIsam, which gives you this as a warning. It's rare to do this, I'm only familiar with the global flag.

However in your case, it's set incorrectly for your database, not just globally. 

Your hosting provider needs to change the default to InnoDB for this database, or you will need to find a new host.

No, our hosting partner could not change our db environments for other reasons too. That is our problem we need to fix. It was running with 6.2.1 and 6.3.3 makes this problems. how to let confluence ignore this check?

You can't avoid the check.  The setting is *mandatory* for newer versions of confluence.  Confluence will fail without the correct setting.

Your hosting provider *must* change it.

ok so we need te use another tool, that's bad

Yes, you need to use a database that is configured to meet the requirements.

See to see how to move on to a correctly configured database.

no we will leave the confluence tool and got to another documentation system cause we will not leave the serverprovider only because on parameter from confluence has changed from confluence 6.2.1 to 6.3.3.

Wow, you really want to cause yourself massive pains of migration because a service provider is too short-sighted or ill-equipped to provide a single, standard configuration setting?

Please forgive me for being harsh, but that sounds more than a little bit daft.

Seriously.  Finding a better service provider, even though you have to migrate, will be a lot easier, as it's "export, copy file, import".  Moving off Confluence could be a massive task.  Getting a decent provider and migrating is a lot smaller (And given the existing provider's miserable failure to support this makes me wonder where else they're failing).

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

1,122 views 59 8
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you