Sushimaster
Member
Hi,
the search index table contains ~35gb data, and we're experiencing table locks sometimes (we're not sure why, maybe backups but, who knows...) which leads to the following problem:
User is creating a thread or answering to a posting, clicks on SEND, saving needs 20sec and timed out.
However, after reloading the page the thread/post IS available - it seems that the last action (adding to search index) is, due to a table lock, not successful.
So my questions:
Why is the search index table in MyISAM format, not InnoDB (which is less affected by table locks)?
Is it possible to convert the table to InnoDB without problems?
Would the Enhanced Search addon (Elasticsearch) solve that problem?
the search index table contains ~35gb data, and we're experiencing table locks sometimes (we're not sure why, maybe backups but, who knows...) which leads to the following problem:
User is creating a thread or answering to a posting, clicks on SEND, saving needs 20sec and timed out.
However, after reloading the page the thread/post IS available - it seems that the last action (adding to search index) is, due to a table lock, not successful.
So my questions:
Why is the search index table in MyISAM format, not InnoDB (which is less affected by table locks)?
Is it possible to convert the table to InnoDB without problems?
Would the Enhanced Search addon (Elasticsearch) solve that problem?
