The AttachmentsIndex table

ted · July 16, 2019, 5:00pm

Thank you knation, that explains it! I’m getting this output:

[12877] [Tue Jul 16 16:48:40 2019] [error]: 50505 (/opt/rt4/sbin/rt-setup-fulltext-index:720)

These links explain that MariaDB has an issue with reporting the version number:

github.com/mailwatch/MailWatch

upgrade.php index warning

opened 04:34PM - 12 Mar 17 UTC

closed 10:32AM - 13 Mar 17 UTC

shawniverson

``` - Adding missing index `subject_idx` on table `maillog`.............. WARN…ING *** ERROR/WARNING SUMMARY *** MySQL version unsupported for index `subject_idx` on table `maillog`, upgrade to version >= 50604 (you have version 50505) ``` Using MariaDB 10.1 (upgraded from mysql 5.1 via MariaDB 5.5). Don't see any obvious issues, but not sure if this message is benign or not. This is a server with a long-running instance of MailWatch that has been around a while on CentOS 6.8.

"MariaDB is lying about its MySQL version compatibility: they backported 5.6 MySQL’s innodb fulltext index in MariaDB 10.0.5 but they didn’t change the server_version compatibility string (still 5.5.5).

If your MariaDB version is greater that 10.0.5 it’s safe to add the fulltext index…"

There’s some discussion here about how to resolve it:
https://jira.mariadb.org/browse/MDEV-13341

For now I can update the code to explicitly allow the InnoDB creation if the version is >= 50505 too.
But I wonder if it’s smarter to leave the index as MyISAM since it adds over 70GB to the size? - I tried running rt-externalize-attachments but we only saved 2.5GB

Thank you very much!

I’m still curious if we can drop the AttachmentsIndex table from backups to save space; somebody tried and subsequent runs of rt-setup-fulltext-index didn’t update the index for old tickets; is the magic sauce simply to remove Set( %FullTextSearch… from RT_SiteConfig.pm BEFORE subsequently re-running rt-setup-fulltext-index to recreate the index from scratch?