Skip to content

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

Open

Description

@kdambekalns

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.

Activity

  1. kdambekalns commented on Mar 1, 2017

    @kdambekalns
    MemberAuthor

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

  2. kitsunet commented on Mar 1, 2017

    @kitsunet
    Member

    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions