Closed fidodone closed 2 years ago
--drive-random-pick-sa
is for random pick initial sa file set in rclone.conf like below
[local]
type = drive
scope = drive
service_account_file = [SA_FILE_PATH] <--- random pick initial one
service_account_file_path = [SA_FOLDER]
root_folder_id =
team_drive = [TEAM_DRIVE_ID]
Why not ramdon pick in rolling?
In short rolling is more than balance use of SAs also for balance of sa projects
You should know why using this option: DO NOT using single project too much, Gxxglx (maybe) monitor API calls, if one project consume too much, they will warn you for abuse usage of api and shut down your project, also you need to remain only one sa in project to recover it. (I indeed got that mail and only way to use SAs is to recreate the project)
Most user create sa file from script, it can't guarentee the order of sa files, that's means project which sa belongs to also intersected. It's the time rolling to work.
I did some tests using the
--drive-random-pick-sa
flag and even with the flag set glcone is rotating service accounts sequentiallyin my test I used 10 SAs
command:
gclone copy ~/test drive:test3 -Pv --drive-rolling-sa --drive-rolling-count=1 --drive-random-pick-sa