Skip to main contentSkip to footer

Indexing fails? Check max_allowed_packet!

Sometimes Relevanssi can get stuck in the indexing. Relevanssi goes past the number of posts in the database and keeps indexing the posts. One possible cause is a too small max_allowed_packet value for your MySQL server.

This value controls how big queries your MySQL server can take. You can see the current value with one of these SQL commands:

SHOW VARIABLES LIKE 'max_allowed_packet';
SELECT @@global.max_allowed_packet;

A reasonable value is at least 4M (4194304). Many servers use 16M (16777216) as the default value. A value of 1M (1048576) is too small for Relevanssi and may cause indexing problems. To adjust the max_allowed_packet value, contact your service provider.

Your account

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

Search

Popular Resources

MemberPress Downloads add-on
The Downloads add-on for MemberPress adds downloadable files to MemberPress. These files are stored outside the Media Library, so by…
Voice Search
Relevanssi Premium’s Voice Search lets visitors enter a search query by speaking into their microphone. The browser converts speech to…

Related Posts:

Currently there are no related posts available.

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