Release Notes : dCache 1.7.0

File Pool hopping implemented

Module	Branch	CVS version
RequestContainerV5.java	head	1.43
MultiProtocolPool2.java	head	1.118
P2PClient.java	head	1.11
Pool2PoolTransferMsg.java	head	1.7

Overview

Starting with 1.118, the MultiProtocolPool2 sends a PoolMgrReplicateFileMsg to a specified destination soon after a file has been successfully received by a pool from a data client (dcap,ftp ...). This doesn't happen on a restage or on a pool to pool transfer. This Pool2Pool message can be used by an Replication Agent to perform necessary replication of newly incoming data.
For convenience, this message may be directly forwarded to the PoolManager which will replicate the specified dataset according to its pool attraction rules and its cost metric. In this case, the original dataset will keep its mode (precious,cached) and the replicated file will be in cached mode. Because of the fact, that the PoolManager selection module needs an destination IP address to run its decision process, the Pool has to specify one when sending the PoolMgrReplicateFileMsg. This IP address may be specified with the replicationOnArrival option. If not specified, the pool will send its own hostname.

Configuration

Common parameters

:

Option	Default	Meaning
ReplicationManager	PoolManager	Destination for PoolMgrReplicateFileMsg message
HostName	Hostname of this pool	Hostname in ProtocolInfo
DestinationMode	Not yet used

Pool startup options

:

             create diskCacheV111.pools.MultiProtocolPool2  <poolName>  \
                      "<basicPoolPath>                                  \
                       -replicateOnArrival[=<ReplicationManager>,<HostName>,<destinationMode>]   \
                       [OTHER OPTIONS]"
              Defaults :
                missing option means :
                   -replicationOnArrival=off
                -replicationOnArrival[=on]  means :
                   -replicationOnArrival=PoolManager,${thisHost},keep 
          

Additional pool commands

set repliation [<ReplicationManager>[,<HostName>[,<destinationMode>]]]

Changes replication options while system is running.
Options, changed with this command are not stored with the save command.

File Pool hopping : replicate on arrival from HSM

Module	Branch	CVS version
RequestContainerV5.java	head	1.36

Overview

The PoolManager can deliver a file, after a restage from an HSM, in one of two ways.

• Direct Delivery After a file has been staged to a particular pool, the file can be directly delivered to the client, even if the pool wouldn't be allowed to do so, following the Pool Selection Unit rules. If the same file is requested the second time it is replicated to an allowed pool prior to delivery.
• Delivery after replication If a file is staged to a pool which is not allowed to deliver the file to the requesting client, the file is replicated to an allowed pool before first delivery.

This feature allows to clearly separate HSM connected pools from pools used to deliver files to clients.

Configuration

PoolManager startup options

NONE

PoolManager command

rc set p2p fortransfer

After a restage, files are transfered to second pool if the initial pool is not allowed to deliver files to the requesting client.

rc set p2p notfortransfer

After a restage, files may be delivered to clients directly even if this initial pool is not allowed to do so. On a second request the file would be transfered to an allowed pool first.

One dCache, multiple PNFS

BUG FIX: PoolManager refetched for internal Restore Handler retries.

Module	Branch	CVS version
RequestContainerV5.java	head	1.36

Overview

Whenever the PoolManager internally retries a restore request, it refetches the StorageInfo first. This is necessary to detect at which point in time the file made it to tape.

Configuration

Not needed

BUG FIX: No longer fetch files from HSM if not yet stored to HSM.

Module	Branch	CVS version
RequestContainerV5.java	head	1.36

Overview

The RestoreHandler no longer tries to fetch files from tape as long as their are not yet stored on tape.

Configuration

Not needed