Scheduled back from saatchi (as i needed the producer credentials to access the queue properties):

$ cat /srv/storage/space/mirrors/code.google.com/sources/INDEX-svn-dumps.reverse-sorted-by-size.txt | tail -n +2 | ./schedule_with_queue_length_check.py --queue-name svndump --threshold 1000 --waiting-time 60 | tee scheduling-svn

So this will schedule up to 1000 tasks in the loader-svn queue every 60 seconds.
The state of what has been scheduled is in the scheduling-svn file.

After discussion with the team, it has been decided to remove from the re-scheduling the svn dumps whose compressed size exceeds 2Gib.
This reflects the same decision took for git repositories.

That list of compressed dumps whose size exceeds the 2Gib threshold is stored in uffizi:
/srv/storage/space/mirrors/code.google.com/sources/INDEX-svn-dumps-with-size-superior-to-2gib.txt

Recreated the scheduling input lists (which filters out those huge dumps) and rescheduled with that list using:

tail -n +187239 /srv/storage/space/mirrors/code.google.com/sources/INDEX-svn-dumps-with-size-inferior-to-2gib.txt | awk '{print $3" "$2}' | ./schedule_with_queue_length_check.py --queue-name svndump --threshold 1000 --waiting-time 120 | gzip -c - >> scheduling-svn.txt.gz

Note:
Both the old and the new input files are sorted in the same ascending order on the first column, the compressed dump's size:

• old: /srv/storage/space/mirrors/code.google.com/sources/INDEX-svn-dumps.reverse-sorted-by-size.txt
• new: /srv/storage/space/mirrors/code.google.com/sources/INDEX-svn-dumps-with-size-inferior-to-2gib.txt

This is in stand-by during the snapshot migration.