Release Notes : dCache 1.6.6

Multi I/O mover queue support.

Overview

With production-1-6-6 dCache supports up to 10 distinct mover queues per pool. They only cover client - dCache data movements (ftp,dcap,http). Pool to pool or HSM transfers are still handled by the already established queues. Each of the new queues is identified by its name, which is defined on creation of the pool. Different mover queues may have a different maximum number of movers allowed. (Which is actually the basic idea of diffent mover queues). Technically, different pools may have a different number of mover queues and/or different queue names, although this doesn't make too much sense. The first queue specified in the configuration (see below) is per definition the default mover queue, independed of its actual name. Requests, not requesting a particular mover queue or requests requesting a mover queue, not existing on the selected pool, are handled by the default mover queue.

Each door may be configured to use a particular mover queue. The pool, selected for this request, doesn't depend on the selected mover queue. So a request may go to a pool which doesn't have the particular mover queue configured and will consequently end up in the default mover queue of that pool.

For the dCap protocol, the corresponding door may be configured to allow the client to determine the mover queue name. In that case the client may use the extra option facility to specify a mover queue.

Configuration

Pool Configuration

Pool startup option :

           create diskCacheV111.pools.MultiProtocolPool2  <poolName>  \
                    "<basicPoolPath>                                  \
                     -io-queues=<queueName-1>[,<queueName-2[,...queueName-10]]    \
                     [OTHER OPTIONS]"
        

Up to 10 queue may be given. The first name specified will become the default mover queue. The default mover queue is choosen if an incoming request doesn't specify a queue or specifies a queue not available on that pool.

Additional pool commands

mover ls

Compatibility command. Lists all requests from all queues.

mover ls -queue

Lists all requests sorted according to the mover queue.

mover ls -queue=<mover queue name>

Lists all requests of queue <mover queue name>.

mover set max active <maxActiveCount> -queue=<mover queue name>

Sets the maximum number of allowed mover of queue <mover queue name>.

mover set max active <maxActiveCount>

Compatibiltiy command. Sets the maximum number of allowed mover of the default mover queue.

Ftp Door (Abstract) configuration

Gsi Ftp startup option :

            create dmg.cells.services.login.LoginManager GFTP \
                       "<portName>                 \
                        diskCacheV111.doors.GsiFtpDoorV1 \
                        -io-queue=<queueName>      \
                        [OTHER OPTIONS]"
        

All requests send from this door will ask to be scheduled to the given mover queue. The selection of the pool is not affected.

DCap Door (Abstract) configuration

DCap startup option :

           create dmg.cells.services.login.LoginManager DCap \
                       "${dCapPort} \
                        diskCacheV111.doors.DCapDoor \
                        -io-queue=<queueName>\
                        -io-queue-overwrite=allowed|denied \
                        [OTHER OPTIONS]"
        

All requests send from this door will ask to be scheduled to the given mover queue. The selection of the pool is not affected. If io-queue-overwrite=allowed is given the dcap client is allowed to request a certain mover queue. For the dCap library this is done, using the extra option.

           dccp -X-io-queue=<queueName>   <source> <destination> [OPTION]
        

Cost module

The cost is correctly calculated for the individual queues. The cm set magic on option is not yet honored.

Queue web page

The mover queue web page shows all queues defined by the individual pools. Queues, not defined in a pool, are marked with '-1' instead of the actual mover numbers.

Example

Optional usage of VO authorization module added.

dCache can optionally talk to VOMS server.

Example