Question
The Decision::StopRelocation enum variant is used in both WAL-based and cell-based relocation strategies, but its behavior differs:
Current Behavior
WAL-based relocation (line 315):
Decision::StopRelocation breaks the entire relocation loop
- Stops processing all remaining WAL entries
Cell-based relocation (line 466-468):
Decision::StopRelocation only breaks the current cell's processing loop
- Continues to the next cell in the sequence
The Question
Should Decision::StopRelocation in cell-based relocation:
- Stop the entire relocation run (consistent with WAL-based behavior)?
- Only skip the current cell (current behavior)?