[JCR-1238] Change default value for maxMergeDocs

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.4
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: Marcel Reutegger
• Created: 27/Nov/07 14:02
• Updated: 15/Jan/08 23:27
• Resolved: 28/Nov/07 10:23

Description

This is actually a left over from the time before JCR-197 was implemented. Back then index merges were performed with the client thread and would hold up execution for a long time if a large number of nodes were merged. The default value for maxMergeDocs limited this to 100'000 nodes, resulting in a couple of seconds for the merge operation.

This default value does not make sense anymore because index merges are performed in a background thread and may take a long time without an effect on regular workspace operations. If a workspace grows large it may cause performance degradation because the number of index segments increases linearly when there are more than 100'000 nodes.

I propose to set the new default to Integer.MAX_VALUE