-
Notifications
You must be signed in to change notification settings - Fork 313
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
BUG: WP-CLI index --offset not working #2557
Comments
Hi @cbratschi , This seems to be working, the confusion is probably with the number of "Processed" items. For example, if I have roughly 10,000 posts and do: This is the output:
I understand it might not be super intuitive, however your offset should still be respected. |
Hi @oscarssanchez, Yes, the offset is working internally but the precess always starts from zero and the total amount stays the same. On our staging environment the memory is limited and indexing causes memory leaks which lead to a crash after 80000 posts using 2 GB of memory. If we manually calculate the offsets it completes after several runs. However, it would be better if the processing does not start from zero if an offset is given. Knowing the exact last position makes it easier to resume afterwards. Thanks, |
Replace text with: |
Now that #2591 was merged into |
Describe the bug
The "wp elasticpress index --offset=80000" is no longer working. Whatever offset is being set, the re-indexing always starts from zero again.
Steps to Reproduce
Expected behavior
Should start from offset.
Screenshots
Environment information
Site Health Info:
Additional context
The text was updated successfully, but these errors were encountered: