Database engine MyISAM - upgrade FOG?
-
Hi
We have received a question from our database admins.
The FOG database engine is MyISAM. We are running FOG version 1.5.5. They want to change the engine but I guess that’s not a good idea.
Is there a version of FOG available that adapts this database engine?
Thx in advance!
-
@dominique What do you propose to upgrade the db engine to?
-
@george1421 the db’s suggested innodb. But I read that’s in a future version?
-
@dominique You can switch it to innodb. There are several tables that use an “invalid date” that cause the table conversion to fail on older version of fog. That date format is “00/00/0000”
Have your db admins review this thread where we work through the transition: https://forums.fogproject.org/topic/14254/high-cpu-usage
-
@george1421 We’re using fog version 1.5.5 for the moment.
No high CPU usage noted for the moment.But changing the database engine isn’t without risks, I presume.
Will an update of fog change this engine? I’ve read about 1.6.0, but that’s no stable version?
Another question, we have 1 master and 80 storage nodes. If I update, first the master or the storage nodes first?
I find conflicting reports about that.Thx!
-
@dominique said in Database engine MyISAM - upgrade FOG?:
No high CPU usage noted for the moment.
The high cpu usage is an artifact of having many computers with the FOG Clients installed.
But changing the database engine isn’t without risks, I presume.
From testing we see no risk other than the default no-date value is incompatible with some of the new sql defaults in mysql/mariadb. Changing the mysql startup value allows you to get pass this issue.
Will an update of fog change this engine? I’ve read about 1.6.0, but that’s no stable version?
I can’t personally speak about existing installed databases, but new FOG installs with use the innodb engine.
Another question, we have 1 master and 80 storage nodes. If I update, first the master or the storage nodes first?
If you are talking specifically about the database, there is only one database and that is on the master. The storage nodes remotely use the master node’s database. So if you update the master node mysql database all of the storage nodes will use it immediately. You may need to reboot each of the storage nodes once the database has been updated just to be sure.
-
@dominique said in Database engine MyISAM - upgrade FOG?:
Another question, we have 1 master and 80 storage nodes. If I update, first the master or the storage nodes first?
Between FOG 1.5.5 and the latest release we switched the local FTP username as well as updated the
fogstoragedatabase user password used by the storage nodes to access the DB. So I would say you will need to update all your nodes “in one big step”. I know that’s impossible having 80 storage nodes but I suggest you update them all as quick as possible.Master or storages first? There was a major change in replication when updating from 1.5.4 to a later version and we suggested to disable replication in the master, update storage nodes first and then the master. But that does not apply to updates of later versions. As far as I can Tell from the top of my head you can go either way. But keep in mind what I said before - update all as quickly as possible.
Will an update of fog change this engine? I’ve read about 1.6.0, but that’s no stable version?
We plan to switch to InnoDB with updating to 1.6.0 but surely that is not a stable version yet. Still Alpha currently.
-
@sebastian-roth Thx for the explanation.
Any idea when 1.6.0 will be general available?
-
@dominique said in Database engine MyISAM - upgrade FOG?:
Any idea when 1.6.0 will be general available?
There is no timeline for this yet. Many people use FOG but very few help working on it. So things are going very slow at the moment. We’ll bring out a last 1.5.x release (1.5.10) to finish up that line and then the next will be a first 1.6 release (months down the road).
If you are keen to get InnoDB earlier you can follow the topic Goerge posted. From my point of view this should be possible in 1.5.x setups as well. But we won’t officially support this and don’t want to push out for a major change in the 1.5.x branch anymore.
