Flowpack.ElasticSearch.ContentRepositoryAdaptor icon indicating copy to clipboard operation
Flowpack.ElasticSearch.ContentRepositoryAdaptor copied to clipboard

Publishing a lot of nodes "skips" index updates

Open kdambekalns opened this issue 7 years ago • 2 comments

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 avatar Mar 01 '17 07:03 kdambekalns

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

kdambekalns avatar Mar 01 '17 08:03 kdambekalns

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

kitsunet avatar Mar 01 '17 08:03 kitsunet