-
Notifications
You must be signed in to change notification settings - Fork 1
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
advanced-search-index Failed without any logs or details as to why #29
Comments
Hi James, |
I did not see any errors which is why it was a little frustrating. I'm going to try and replicate this issue locally to see if I can see errors there. |
Ok, the above issue I think is due to a custom field that I added to the index which expected an int32 but got a float. But there's now a new issue where the entire indexing job will fail at the very last moment because it throws an error, after 134 minutes indexing everything:
|
I have a concerning feeling that despite indexing everything for the last 134 minutes, the alias was not accepted and so my products are not accurately indexed, which means that product searches will return old results and 404's if items have been disabled or moved in the meantime. |
I've looked up my TypeSense collections and aliases, and it looks like it's found here:
and the alias list is here:
I'm not sure if I can see anything wrong here, but it's curious why there would be a timeout and 404 after 130 or so minutes. |
Ok further debugging as I run the index, these are firing in the logs over and over again:
It's odd because all of these products have prices so I'm not sure what's up there. |
I do see the
|
This is the extent of the failure error in my logs:
|
I think there are multiple issues here, one of them being a timeout on the entire process. Perhaps being able to split up the indexing into multiple jobs based on the number of items might be best, then it can pick up where it leaves off if there's an error and timeouts are not an issue. The other issues I think are related to differences between deployed environments, I believe I have figured them out. |
Hi James, thanks for providing all the additional information, and I'm sorry that this is such a frustrating issue! I will look into this this week. |
Every so often in a reindexing job, the job fails and the job error just says:
0 documents imported successfully, 1 documents failed during import. Use
error.importResults
from the raised exception to get a detailed error reason for each document.The text was updated successfully, but these errors were encountered: