[SVN-573] very long fs node IDs on bottleneck directories

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: Beta
• Component/s: src
• Assignee: Unassigned
• Reporter: Karl Fogel
• Created: 29/Nov/01 21:36
• Updated: 27/Oct/18 16:43
• Resolved: 15/Sep/04 08:43

Description

For example, in the Subversion repository, /trunk is
1.35.1.192.2.157.1.178, and /trunk/subversion/ is
121.15.1.151.2.110.1.9.1.123.

Possible solution: when exploring for a next-available
successor ID, be willing to backtrack a little; but before
we make this change, we need to make sure that the new
shorter ID will still be considered a successor of the old
one.  Hmmm.  Which is not currently the case.  We can
change the rules, though, just need to be careful about it.

Issue Links

• blocks: SVN-502 Subversion repository needs cleaning.
• depends upon: SVN-648 need FS dump/load format and tool
• depends upon: SVN-654 switch our NodeRevID representation
• is blocked by: SVN-648 need FS dump/load format and tool
• is blocked by: SVN-654 switch our NodeRevID representation
• is depended upon by: SVN-502 Subversion repository needs cleaning.