Closed nikmagini closed 8 years ago
Currently, the first replica of a newly injected file is always created in status 'not staged' (t_xfer_replica.state=0) by the Inject datasvc API.
Any subsequent replica on Disk nodes is created with status 'staged' (t_xfer_replica.state=1) by FilePump instead
This means that the FileRouter will be biased in selecting subsequent replicas, even if the original replica would be faster.
Fix committed in https://github.com/dmwm/PHEDEX/commit/7ad51fc83aab84bb3d2a77620890f1c43aa75bfa and released in datasvc 2.3.22 currently in testing on cmsweb-testbed, will go to production on 2015-06-07
Note: the same issue also affects replicas of blocks reactivated by BlockActivate.
Deployed in production on cmsweb with datasvc 2.3.22 - closing
Currently, the first replica of a newly injected file is always created in status 'not staged' (t_xfer_replica.state=0) by the Inject datasvc API.
Any subsequent replica on Disk nodes is created with status 'staged' (t_xfer_replica.state=1) by FilePump instead
This means that the FileRouter will be biased in selecting subsequent replicas, even if the original replica would be faster.
Fix committed in https://github.com/dmwm/PHEDEX/commit/7ad51fc83aab84bb3d2a77620890f1c43aa75bfa and released in datasvc 2.3.22 currently in testing on cmsweb-testbed, will go to production on 2015-06-07
Note: the same issue also affects replicas of blocks reactivated by BlockActivate.