Chapter 6 HPSS Configuration
326 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
Table 6-16 Bitfile Server Configuration Variables
Display Field Name Description Acceptable Values Default
Value
Server Name Descriptive name of the
BFS. This name is copied
overfrom the BFS general
configuration entry.
This field cannot be modified. It is
displayed for reference only. Selected BFS
descriptive
name.
Server ID The UUID of the Bitfile
Server. This ID is copied
overfrom the BFS general
configuration entry.
This field cannot be modified. It is
displayed for reference only. Extracted
from the BFS
general
configuration
entry.
Maximum Open Bitfiles The maximum number of
bitfiles that can be open
concurrently in the BFS.
Any positive 32-bit integer value. 2000
Maximum Active I/O
Requests The maximum number of
I/O type requests that can
be open concurrently in
the BFS.
Any positive 32-bit integer value. 190
Advice:This value includes all requests that might result in data movement except
migrate requests. This includes read, write, copy file and all non-background type
stagerequests. If an open request results in any stage other than a background stage,
the open request is also counted. This value should be set high enough to cover the
maximumnumber of active and queued requests expected in the system. This value
cannotbe higher than (the maximum number of BFS threads - 4). Since migrate
requests are not counted, the maximum number of concurrent migrate requests
expected should be computed and this value should be set no higher than ((the
number of BFS threads - 4) - max migrate requests). Each storage class that is
inthe process of being migrated will generate 1 migrate request for each copy being
created.
Maximum Active Copy
Requests The maximum number of
copytype requests that can
be active concurrently in
the BFS.
Any positive 32-bit integer value. 95
Advice: This value counts only copy file requests and various forms of stage
requests. For copy file requests and non-background type stage requests, this limit
results in the requests being given a BUSY error when the request is generated.
Background stage requests are queued internally to BFS without using thread
resourcesand up to 2000 can be queued before a BUSY error will be returned. This
value will limit the actual number of threads that are busy in the background
processing the background stage requests. The copyfile command that is generated
bythe background COS change thread is included in this count. This count does not
include migrate requests.