Here are some starter words which might get us going...
Start options:
file_queue, path_queue, restart_queue: Give custom names to your queues. Probably don't need to touch these unless you want to use the same Redis database for multiple sync jobs simultaneously.
event_handler: Very important option to point at the "client-side" policy for a given job.
ignore_cache: If you want to re-scan everything, use this option to ignore the Redis cache which the workers use to track which paths have been sync'd already.
Optimization options:
exclude_file_type, exclude_file_name, exclude_directory_name: Ignore certain types of files, files by certain names, and directories of certain names, respectively. Can reduce the number of paths to sync.
files_per_task: How many paths a single task will contain. Saves trips to the Redis database.
initial_ingest: Each time a path is going to be registered, iRODS is checked to see if the path already exists. If it does, we avoid an error by not attempting to create it. If you know that this is the first time this is being ingested to this logical path, you can skip this check and blindly sync paths to iRODS without checking for existence. This saves trips to the iRODS server.
irods_idle_disconnect_seconds: A connection pool is used to reduce the number of times we need to spawn agents in the iRODS server. Holding these connections open forever is a drain on resources, so you can adjust the timeout on idle connections with this setting. You may wish to keep them open for longer if there's a known recurring sync job to run (I think)
Here are some starter words which might get us going...
Start options:
Optimization options: