Skip to content
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

Publishing a lot of nodes "skips" index updates #195

Open
kdambekalns opened this issue Mar 1, 2017 · 2 comments
Open

Publishing a lot of nodes "skips" index updates #195

kdambekalns opened this issue Mar 1, 2017 · 2 comments

Comments

@kdambekalns
Copy link
Member

kdambekalns commented Mar 1, 2017

Given that:

  • a workspace with a lot of changes exist (more than the default threshold of 100 to flush the indexing queues, indexingBatchSize)

When I:

  • publish all those changes in the workspace module (publishing from anywhere should have the same effect)

Then:

  • the indexer will log a lot of Could not index node with identifier …, not found in workspace live

This seems to be caused by the indexer looking for the node to index in the target workspace. But if the indexing threshold is reached before the publishing has actually been "persisted to disk", the nodes for that run cannot yet be found in the target workspace.

If this has happened, a nodeindex:build is needed to update the index to the expected state.

@kdambekalns
Copy link
Member Author

Setting the indexingBatchSize to more than the number of unpublished nodes works around the issue, this confirms the suspected cause IMHO.

@kitsunet
Copy link
Member

kitsunet commented Mar 1, 2017

we need queued indexing IMHO. Do the publishing, persist changes, queue re-index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants