[MXS-1273] Can replication_heartbeat table be InnoDB? Created: 2017-05-23 Updated: 2017-12-01 Resolved: 2017-06-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Documentation |
| Affects Version/s: | 2.0.5 |
| Fix Version/s: | 2.2.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Wagner Bianchi (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Description |
|
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:
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!! |
| Comments |
| Comment by markus makela [ 2017-06-06 ] |
|
You should be able to do an ALTER TABLE to change the table from MyISAM to InnoDB. There's no real reason why it's chosen as MyISAM and I think the table should use the default storage engine. |
| Comment by Wagner Bianchi (Inactive) [ 2017-06-14 ] |
|
Markus, Yes, I completely agree with "the table should use the default storage engine", but, when I had this issue, the default storage engine was set to InnoDB and the table was created as MyISAM. I wonder if it's not hardcoded as ENGINE=MyISAM, isn't it? Thanks for the attention man, cheers! |
| Comment by markus makela [ 2017-06-15 ] |
|
The engine was hard-coded as MyISAM in the create table statement. |