-
-
Notifications
You must be signed in to change notification settings - Fork 512
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 when performing many INSERT queries mixed with normal traffic #1416
Comments
could you upload your |
I have downgraded to 6.0.4 and everything works perfectly fine. This also fixed another issue with increased CPU usage. searchd would suddenly, maybe 30 or so seconds after startup, use more and more CPU cores (while properly serving requests). I thought the index was borked, so I purged it, but it quickly came back after reindexing. I use a |
you could upload all your data as described at our manual Uploading your data into our write-only S3 storage It is also unclear you said
however initially you mention lot of Coud you provide reproducible example that we could chaeck here localy? |
I have a similar situation, but only via json queries |
it could be better to post crash log or searchd.log to make sure issues are related |
|
it is not the same crash as I see the highlighter related code but original crash was related to stored fields. Could you upload your index mentioned at the crash log to reproduce the crash locally? I see this index at the crash log posts_idx |
I posted a script that reproduces this crash on version 6.2.12. https://github.com/Eclipsium/manticore_crash
index config:
|
The crash was confirmed in 6.2.12 with help of the script, but we couldn't reproduce it in the dev version. @ericek111 can you check if the dev version helps in your case too? |
Since the dev version is always changing, it's worth to add that the version I tested on was |
Describe the bug
When a lot of
INSERT
requests are being sent, a coupleSELECT
s is enough to crash the daemon. This is easily and repeatedly reproducible. Possibly related to #1396Describe the environment:
Messages from log files:
The text was updated successfully, but these errors were encountered: