-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Possible issue with Buddy on Windows #2116
Comments
what to expect on this ticket?" could you provide error message from the ?
could you upload |
seems the dump is invalid as I got error right on the start
the daemon version is
|
seems I reproduced this issue - the Buddy error at the daemon log
and the error message at the cli
it inserted
|
if I disable sharding at the buddy then
I got the same error around 40k docs posted
however now daemon log has no any traces of the buddy error |
I restarted buddy with
and at the daemon console I see that buddy pauses during processing the Here is a
from the daemon timestamp I see if It is unclear what point of the error or what stack of the error in the buddy - someone should debug that in the buddy. |
@tomatolog pls check if you still can reproduce it in Window after manticoresoftware/manticoresearch-buddy#274 (comment) is fixed. |
can not reproduce the issue on windows as got error
on data from I use buddy from the master branch 2963d15e2f0004f90fda72f35389ec0be57f901e and daemon from the master too
now sure how to get further |
I use fixed dump from Not sure how it might be related to initial description. |
There's a chance we fixed it after the latest updates. To confirm it's resolved, let's run a simple loop test that executes some queries multiple times, like If it works without any errors we encountered before, we can close the issue. |
seems work fine at the master head of the daemon and head of the buddy source |
Bug Description:
We seem to have a peculiar issue while using Buddy on Windows. We should try to replicate it on another machine and validate if it's a localized issue or a more widespread problem.
Due to the changes we've made in how we work with mysqldump, we should use the following Manticore search version:
To reproduce the issue, we should run the restoration with mysqldump:
P.S. The file is available on dev2 at /tmp/bench.tar.gz
If we can insert everything without encountering timeout errors in the log, that's great (probably a local issue). However, if we're unable to insert and consistently encounter timeouts, resulting in a failed restoration, we should investigate what's causing the problem.
I tried to reproduce it on Linux, but I couldn't succeed; it worked fine.
Manticore Search Version:
6.2.13 8850df782@24042916 dev
Operating System Version:
Windows
Have you tried the latest development version?
Internal Checklist:
To be completed by the assignee. Check off tasks that have been completed or are not applicable.
The text was updated successfully, but these errors were encountered: