-
-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash and corrupted index on 3.4.2 under query load #367
Comments
The query I use is a little odd, it's basically to do a search for "the best possible match with as many of these keywords as possible":
I use a |
could you set correct
Just create folder there with proper name. This way all incoming TRX got stored into binlog that I could replay and get index at same state as you got prior to crash then I could try to investigate crash further. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Feel free to re-open the issue in case it becomes actual. |
Manticore Search version (top line in output of
bin/searchd -v
orbin/indexer -v
):Manticore 3.4.2
OS version (
uname -a
if on a Unix-like system):Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
Linux xxx 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Build version:
manticore_3.4.2-200410-69033058-release.buster_amd64-bin.deb
Describe the problem:
This crash happens repeatably after I recreate the index over the mysql connection from a golang project and then start doing heavy searches against it.
I add things to the index in bulk with
INSERT
and then runOPTIMIZE
afterwards, then run queries against it. This works great on macOS (manticore 3.4.2), but seems to crash on the production linux environment.It seems like this actually corrupts the index as after searchd restarts the index doesn't exist and I need to manually delete the folder for it to be recreateable.
Steps to reproduce:
I'm afraid it's going to be tough to create a simple reproduceable case 🤔
See logs below, nothing custom. Index is created with the following options (excuse the code, couldn't figure out how to get these out of sphinxql):
go code with table options
My workflow looks like:
It doesn't always crash, but it seems to quite often on different queries.
Messages from log files:
searchd.log
Nothing noteable in dmesg
manticore.conf
In case you've faced a crash what
indextool --check
returns:The text was updated successfully, but these errors were encountered: