Skip to main contentSkip to footer

A Relevanssi user reported a mystical database problem. After about two minutes of indexing, the server shuts down the indexing. This leaves MySQL queries hanging on the server, causing the site to crash. The only way to get the site back live was to reboot the whole MySQL server.

Eventually, they were able to figure out the problem. It was caused by a server misconfiguration. The innodb_buffer_pool_size was restricted to an absurdly low number and both query_cache and OPcode cache were missing. Once these problems were fixed, Relevanssi indexing started working without problems.

Your account

Not logged in. Log in to see your license details.

Search

Popular Resources

Disabling Relevanssi

If you need to disable Relevanssi, for example for a particular template, all you need to do is to unhook two filters: remove_filter( ‘posts_request’, ‘relevanssi_prevent_default_request’ ); remove_filter( ‘posts_pre_query’, ‘relevanssi_query’, 99 ); Before versions 4.10.2 (free) and 2.12.2 (Premium), you need to unhook these filters: remove_filter( ‘posts_request’, ‘relevanssi_prevent_default_request’ ); remove_filter( ‘the_posts’,…

EmbedPress autoembeds
EmbedPress has an auto-embed feature that tries to embed all URLs found in posts. This can cause problems with Relevanssi:…

Related Posts:

Comment Section:

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed