Feature #8457
Updated by Peter Amstutz about 8 years ago
Currently, keep client always orders the server list the same way on a per-block basis. If compute nodes are all requesting the same file at once (a common event when starting a large run), this can lead to load on the keepstore at the top of the list for each block while other servers with the same block are not utilized.
Since blocks are typically replicated, we could shuffle the top N services (where N is the replication count for the block). This will spread out the load in a properly replicated and balanced cluster as different clients will use slightly different priority orders for requesting blocks.