FTS Channel Resolution
This page describes how the FTS assigns channels to a job.
Notation
A : site A (source)
B : site B (destination)
[A] : group containing A
[B] : group containing B
* : catch all
FTS 2.0
For a transfer job from site A to site B, FTS will search the defined channels and assign the first found following this order:
Source |
Destination |
Description |
A |
B |
Dedicated channel from site A to site B |
[A] |
B |
Channel from a group including site A to site B |
A |
[B] |
Channel from site A to a group including site B |
[A] |
[B] |
Channel from a group including site A to a group including site B |
* |
B |
Catch-all to site B |
A |
* |
Site A to catch-all |
* |
[B] |
Catch-all to a group including site B |
[A] |
* |
Group including site A to catch-all |
* |
* |
Catch-all to catch-all |
FTS tries to find the best (less generic) possible match on the destination, since write operations scale worse than read operations.
FTS 1.5
Due to a bug, in FTS 1.5 the channel resolution order was the following:
Source |
Destination |
Description |
A |
B |
Dedicated channel from site A to site B |
A |
* |
Site A to catch-all |
* |
B |
Catch-all to site B |
* |
* |
Catch-all to catch-all |
(with many thanks to Pepe Flix for pointing this out)
--
PaoloTedesco - 20 Jul 2007