In order to keep track on the flush activities the flush control web pages need to be activated. Add a new set alias directive somewhere between the define context httpdSetup endDefine and the endDefine command in the /opt/d-cache/config/httpd.batch file.

define context httpdSetup endDefine
...
set alias flushManager class diskCacheV111.hsmControl.flush.HttpHsmFlushMgrEngineV1 mgr=<FlushManagerName>
...
endDefine

Additional flush managers may just be added to this command, separated by commas. After restarting the ’httpd’ service, the flush control pages are available at http://<headnode>:2288/flushManager/mgr/*.

The flush control web page is split into 5 parts. The top part is a switchboard, pointing to the different flush control managers installed. (listed in the mgr= option of the set alias flushManager in the config/httpd.config). The top menu is followed by a reload link. Its important to use this link instead of the ’browsers’ reload button. The actual page consists of tree tables. The top one presents common configuration information. Initially this is the name of the flush cell, the name of the driver and whether the flush controller has actually taken over control or not. Two action buttons allow to switch between centrally and locally controlled flushing. The second table lists all pools managed by this controller. Information is provided on the pool mode (readonly vers. readwrite), the number of flushing storage classes, the total size of the pool and the amount of precious space per pool. Action buttons allow to toggle individual pools between ReadOnly and ReadWrite mode. Finally the third table presents all storage classes currently holding data to be flushed. Per storage class and pool, characteristic properties are listed, like total size, precious size, active and pending files. Here as well, an action button allows to flush individual storage classes on individual pools.