[GH-ISSUE #502] Worker infinite loop index updates #388

New issue

Closed

opened 2026-02-25 21:31:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 21:31:49 +03:00

Owner

Originally created by @ciur on GitHub (Jan 3, 2023).
Original GitHub issue: https://github.com/ciur/papermerge/issues/502

Originally assigned to: @ciur on GitHub.

Component: backend (papermerge-core)
Version: 2.1.3

While removing mptt dependency papermerge.search.tasks.update_index was changed: instead of updating index for each individual instance - the whole index is updated (similarly to invoking ./manage.py update_index).

However, that change results in infinite loop index updates - one single node update will make worker spend in infinite loop updating whole index over and over.

Yet another problem popped up - after node move - indexes of all moved nodes (i.e. moved node and all its descendants) instances should be updated as well, otherwise search results will reveal nodes with outdated breadcrumbs.

Originally created by @ciur on GitHub (Jan 3, 2023). Original GitHub issue: https://github.com/ciur/papermerge/issues/502 Originally assigned to: @ciur on GitHub. Component: backend (papermerge-core) Version: 2.1.3 While removing mptt dependency [papermerge.search.tasks.update_index ](https://github.com/papermerge/papermerge-core/commit/89fbfa999df8c96377698bb21e2987bac3fe360f#diff-5736fcd14f95b4ee4f7b82809c0f14db6d2fa26e3a72f36332122825e1aad36cL80) was changed: instead of updating index for each individual instance - the whole index is updated (similarly to invoking ./manage.py update_index). However, that change results in infinite loop index updates - one single node update will make worker spend in infinite loop updating whole index over and over. Yet another problem popped up - after node move - indexes of all moved nodes (i.e. moved node and all its descendants) instances should be updated as well, otherwise search results will reveal nodes with outdated breadcrumbs.