-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Thread Panic from grenad
- must be greater than
#3043
Labels
Milestone
Comments
loiclec
added a commit
to meilisearch/milli
that referenced
this issue
Nov 14, 2022
Where the batch's information was not properly updated in cases where only the proximity changed between two consecutive word pair proximities. Closes meilisearch/meilisearch#3043
loiclec
added a commit
to meilisearch/milli
that referenced
this issue
Nov 16, 2022
Where the batch's information was not properly updated in cases where only the proximity changed between two consecutive word pair proximities. Closes meilisearch/meilisearch#3043
bors bot
added a commit
to meilisearch/milli
that referenced
this issue
Nov 17, 2022
697: Fix bug in prefix DB indexing r=loiclec a=loiclec Where the batch's information was not properly updated in cases where only the proximity changed between two consecutive word pair proximities. Closes partially meilisearch/meilisearch#3043 Co-authored-by: Loïc Lecrenier <loic.lecrenier@me.com>
Re opening, not fixed until we merged the new milli's version into |
Closed by #3084 |
amab8901
pushed a commit
to amab8901/milli
that referenced
this issue
Dec 2, 2022
Where the batch's information was not properly updated in cases where only the proximity changed between two consecutive word pair proximities. Closes meilisearch/meilisearch#3043
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
During ingest, and trying to re-create the panic from #3042, I also saw this:
To Reproduce
Have not found minimal, reproducible example.
Believe it is related to changing the ETL to run in multiple workers who may re-write the same indices/ID's.
I have moved ETL scripts into Airflow and parallelized them, so I am GUESSING there are instances where inserts from different workers are over-writing the same ID in close succession.
Expected behavior
Handle parallel ETL inserts dealing with the same ID without crash
Screenshots
Meilisearch version: v0.30.0rc1
Additional context
This may be related to #3042 -- It was seen during the same ETL trials.
TODO
release-v0.30.0
The text was updated successfully, but these errors were encountered: