Would that not cause problems with xenForo since it does have some myISAM tables?Currently replication works only with InnoDB storage engine. Any writes to tables of other types, including system (mysql.*) tables, are not replicated. However, DDL statements are replicated in statement level, and changes to mysql.* tables will get replicated that way. So, you can safely issue: CREATE USER..., but issuing: INSERT INTO mysql.user..., will not be replicated.
Hi,@Deebs, I was researching this (and I know VERY little about clustering mySQL but am planning on learning) and one thing worried me. The Percona Galera Cluster denotes a "limitation"
Would that not cause problems with xenForo since it does have some myISAM tables?
Already using memcached on both servers (just to learn it - I can probably eliminate it on one and already have basically set up stuff so I can implement it). Since my site isn't that large, Enhanced Search isn't really needed but may end up buying it anyway.A large site that needs database clustering isn't going to be using the 3 MyISAM tables that XenForo uses.
xf_search_index isn't used if you are using the XF Enhanced Search.
xf_session and xf_session_admin aren't going to be used if you are using the session cache option (for example we use memcached for session).
ElasticSearch offers much more than just performance over MySQL full-text indexing.Already using memcached on both servers (just to learn it - I can probably eliminate it on one and already have basically set up stuff so I can implement it). Since my site isn't that large, Enhanced Search isn't really needed but may end up buying it anyway.
Post order is dependant on a computed position (driven by insert date), not the post id. Threads are displayed by date.Any issues with AUTO_INCREMENT while using Galera? Or collisions being successfully avoided as described here? [URL='https://blog.mariadb.org/auto-incre...//blog.mariadb.org/auto-increments-in-galera/[/url]
xf_session_activity can also be converted to being stored into your front-end cache. Otherwise convert to xf_session_activity, and get slightly lower inserts/updates but avoids full-table locks of MyISAMWhat's going to happen with MEMORY-tables, like xf_thread_view, xf_session_activity, xf_attachment_view?
We use essential cookies to make this site work, and optional cookies to enhance your experience.