Can replication_heartbeat table be InnoDB?

Hello Foks,

I have a case where I'm working with an environment that has the detect_replication_lag on mysqlmon (MySQL Monitor) and the replication_heartbeat is crashing and needs to be repaired many times with a price of stopping the accuracy of getting the right position of the replication lagging:

170523 13:35:45 [ERROR] mysqld: Table 'replication_heartbeat' is marked as crashed and should be repaired

170523 13:35:45 [ERROR] mysqld: Table './maxscale_schema/replication_heartbeat' is marked as crashed and should be repaired

170523 13:35:45 [ERROR] mysqld: Table 'replication_heartbeat' is marked as crashed and should be repaired

170523 13:35:45 [Warning] Checking table: './maxscale_schema/replication_heartbeat'

At this point of MyISAM maybe going away and times on which we need more consistency and less issues with the table's structure per se, could we have that table being create with Engine=InnoDB? It seems the table is being created with Engine=MyISAM, as per the tests I did, I have default_storage_engine as InnoDB.

Thanks a lot in advance, cheers!!