-
-
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
REPLACE INTO leading to index corruption #569
Comments
Thank you for the reproducible case @pakud . I've reproduced it on our side. |
➤ Aleksey N. Vinogradov commented: Investigation steps performed:
So, minimal reproducable case found, that is:
Now it is time to fix it. |
➤ Aleksey N. Vinogradov commented: (issue was introduced in d38409e) |
Closing as fixed. |
Fixed in 47b9aeb |
Describe the bug
after running attached file indextool --check informs about corrupted index
To Reproduce
Steps to reproduce the behavior:
get from https://mnt.cr/ftp content of github-issue-569 and unpack it.
config:
load the 'suspect' file [ uploadded via https://mnt.cr/ftp ] - it's full of REPLACE INTO with the last one having some binary garbage:
Expected behavior
on-disk index file should be consistent, indextool should succed.
Describe the environment:
Messages from log files:
there's nothing interesting in searchd.log; output of the indextool:
Additional context
i came up with this artificial example while working on sanitizing data from #566
it's the last line of the 'suspect' file that leads to the problem but it alone - without the previous ones - is not enough to
reproduce it
The text was updated successfully, but these errors were encountered: