0

MariaDB Galera Cluster states that the storage engine needs to be InnoDB.

I am using Mroonga on some tables in wrapper mode {which uses InnoDB under the hood as storage engine}.

The problem I am facing is broken synch.

All the standard InnoDB tables get replicated/synched perfectly fine but the tables that are using Mroonga do not get synched for some reason. Any clue what might be the reason?

[EDIT]

Here is the CREATE TABLE SQL

CREATE TABLE `employees` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `interview_memo` text NOT NULL,
  `caution_notes` text NOT NULL,
  PRIMARY KEY (`id`),
  FULLTEXT KEY `idx_employees_interview_memo` (`interview_memo`) COMMENT 'tokenizer "TokenMecab"',
  FULLTEXT KEY `idx_employees_caution_notes` (`caution_notes`) COMMENT 'tokenizer "TokenMecab"'
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COMMENT='engine "InnoDB"'
  • Can you provide example create statement(s) for the relevant table(s)? Related question here: Will “bridge” storage engines work with MariaDB Galera Cluster? Also, what error messages (if any) are you seeing? – dbdemon Jun 21 '18 at 12:08
  • Please provide SHOW CREATE TABLE for one of the unsync'd tables. – Rick James Jun 21 '18 at 20:10
  • Shouldn't that say ENGINE=Mroonga ... COMMENT='engine "InnoDB"'? The documentation on wrapper mode seems to say so. – dbdemon Jun 22 '18 at 19:46
  • Also, running that CREATE statement with ENGINE=Mroonga gives me this warning: Warning | 1112 | specified tokenizer for fulltext index <TokenMecab> doesn't exist. The default tokenizer for fulltext index <TokenBigram> is used instead. – dbdemon Jun 22 '18 at 20:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.