[Buildbot-commits] [Buildbot] #2492: MySQL replication ignoring selected storage engine

[Buildbot trac]

#2492: MySQL replication ignoring selected storage engine
----------------------+-----------------------
Reporter:  andrewjcg  |      Owner:
    Type:  defect     |     Status:  new
Priority:  minor      |  Milestone:  undecided
 Version:  master     |   Keywords:  database
----------------------+-----------------------
 I am not 100% sure this is a buildbot problem, but the I'm seeing the
 following issue:

 When using a MySQL backend, buildbot sets the engine storage type using a
 "SET storage_engine=<type>" command
 (https://github.com/buildbot/buildbot/blob/master/master/buildbot/db/enginestrategy.py#L113).
 As per (http://bugs.mysql.com/bug.php?id=41101), MySQL does not record
 this command to the binlog, so MySQL replication will use the default
 storage engine on the slave.  Since buildbot can't use InnoDB (as per
 http://buildbot.readthedocs.org/en/v0.8.6/manual/cfg-global.html#mysql),
 this will break when its set as the default storage engine on the slaves,
 even when we explicitly set "MyISAM" as the storage engine in the buildbot
 config.

 I *think* this means the engine type should be included on the actual
 create table query, rather then using 'init_command', as this will get
 written to the binlog and the slaves will pick this up for replication.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2492>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation