Table of Contents
One of the major benefits that the SRM v2.2 specification brought was the introduction of the concept of spaces. A space is a reserved portion of dCache's total capacity. It allows file upload operation to be conducted with some certainly that sufficient space is available.
dCache's implementation of SRM spaces is an example of late pool binding. This is an advanced feature that means that, although dCache will (under normal operating conditions) always honour space reservations, dCache does not choose on which pool a file will be stored until a user uploads the file.
One of the benefits of late pool binding is that dCache doesn't waste storage capacity. When a space reservation isn't being completely used, some of the capacity can be used for other activity. One possible use of this capacity is providing temporary cached copies of data. This allows dCache to spread read requests for “hot” files over multiple pools, so increasing the throughput.
In dCache, space management operations (reserving space or using space) operate on LinkGroups. A LinkGroup contains one or more Links and include SRM specific concepts and settings. Broadly speaking, this section is about LinkGroups.
A pool may be a member of more than one poolgroup. A pool may also appear in more than one link. The results may be slightly confusing if the configuration is complicated, but the Pool Selection Unit (the component, mentioned in ..., that chooses on which pool a file should be placed) will operate correctly.
However, a pool must not appear in more than one LinkGroup and must not appear both in a Link within a LinkGroup and another Link outside a LinkGroup. This is because the space accounting must be handled correctly.