-
Notifications
You must be signed in to change notification settings - Fork 314
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
Problem with syncing data #2649
Comments
Hi @derringer, Thanks for opening the issue. One of the changes we made in version 4.0.0 was to introduce a dynamic index process, so, let's say, you use 1,000 posts per page, ElasticPress will get 1,000 from the database but won't send them all in one request but send them in small bulks until all of them are processed. The main goal of this feature is to avoid having several failures due to "Request too big" requests. People wanting to index without this feature can use the WP-CLI command with the static-bulk flag: I presume it will be some sort of data issue with the content? Is there any additional logging that can be done? You can also use the code in this gist to log all the requests made and their characteristics. Would it be possible for you to
Thanks! |
This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful. |
Hi @felipeelia , Sorry for the delay. Now we are running 4.0.1 on the development server to test this now. I have enabled all those things and the log in the webpage gets stuck on many repeated lines of: And Here is the wp-debug.log (https://pastebin.com/GDESh62D). I deleted post ID 2... Now it stops and repeats: |
Hi @derringer, First of all, thank you for getting back to us. Looking at your log, it doesn't seem it is stuck where I thought it would be. Here are a few things that could help us to identify the root of the problem:
Thanks! |
|
So disabling this plugin or actually, working around it with this filter (the ignore_custom_sort attribute turns off the AutoSort behaviour in the plugin):
fixed the posts. But there is still a problem now with the terms indexing. It only seems to index the number in "Content Items per Index Cycle". |
That is an excellent discovery, @derringer. Thank you very much! For the problems with terms, does it work if you run: |
No, so that is what I ran (without the
On the live with with the old plugin (3.6.6) there are about 1400 terms indexed. |
Hi @derringer, that looks like a bug in the plugin. While running the current codebase, can you please run I've opened #2665 to fix the problem, would it be possible for you to test it? If you can't let me know and I can create a zip file for you. Thanks! |
Hi @felipeelia, Using that command works fine and there are 9656 items in ES:
Will test the patch now. |
I have patched my version with #2665 and can confirm that it works as expected indexing 9656 terms. Thanks @felipeelia |
When pressing sync, or delete data it seems to get stuck in a loop
Log
Log on the sync page shows:
Environment information
Additional context
Rolling back to 3.6.6 works perfectly and all posts and terms are indexed.
Is there any additional logging that can be done - I presume it will be some sort of data issue with the content?
I tried removing all the additional metadata fields using the filter hook, but there is was no difference (other than the mapping was much smaller).
What other information can help?
The text was updated successfully, but these errors were encountered: