Issue Summary

When a page is moved to a target location where custom sort is applied to a page tree all items are index within the subtree.

This can quickly overload the index queue if there are 50+ child pages as the page and its attachments must all be indexed.

Steps to Reproduce

1. Create Parent A with 10 children pages named Child A1 - Child A10.
2. Create Parent X with 100 children pages named Child X1 - Child X100.
3. Enable DEBUG logging for com.atlassian.confluence.internal.index.AbstractBatchIndexer, com.atlassian.confluence.search.lucene, and com.atlassian.bonnie.search.extractor
   • The logging is very verbose, but atlassian-confluence.log will show all items being indexed for each move
4. Move Child A2 under Parent X

Expected Results

You should see only 3 pages being re-indexed (moved page, old parent and new parent).

Actual Results

You see over 100 pages being re-indexed (all children of Parent X).

Workaround

Restore alphabetic sort under Space tools > Reorder pages: Move and Reorder Pages - Confluence