Use this panel to view high-level information about SAN File System metadata servers, including client
workload details.
Fields
The Servers table
lists the following information:
Attribute Details information for inactive, active and total metadata servers. |
Total The total for all metadata servers. |
Attributes
Inactive Servers Metadata servers in one of the following states: - Not running
- Failed initialization
- Initializing
- Not added
- Joining
|
Active Servers Metadata servers in one of the following states: - Offline
- Partly quiescent
- Fully quiescent
- Online
|
Total Servers All the metadata servers that have been added to the cluster, including
those that are in an unclustered meta-state. |
Fields
The Server
Transactions — Client Workload table pertains to client-level transaction
work being done on all the metadata servers, including the master metadata
server. The table lists each metadata server's name and a total for all metadata
servers regarding the following details:
Update Update ("write") transactions. |
Total All metadata server transactions ("read" and "write"). |
Fields
The Server
Buffers — Client Workload table pertains to client-level work, regarding buffers,
being done on all the metadata servers, including the master metadata server.
The table lists each metadata server's name and a total for all metadata servers
regarding the following details:
Dirty The current number of dirty buffers for client/user metadata activity.
Dirty buffers contain data awaiting input/output (I/O) to disk. |
Clean The current number of clean buffers for client/user metadata activity.
Clean buffers contain data, but are available for reuse. |
Free The current number of free buffers for client/user metadata activity.
Free buffers are those that are currently not in use. |
Total All buffer types per metadata server. |
Fields
The Server
Locks — Client Workload table pertains to client-level work regarding
locks, being done on all the metadata servers, including the master metadata
server. The table lists each metadata server's name and a total workload for
all metadata servers regarding the following details:
Session The current number of session locks for each metadata server. A session
lock holds a reference on an engine. A client must acquire a session lock
to do any operation with a filename. |
Data The current number of data locks held for each metadata server. Clients
must hold data locks in order to cache data pages, attributes of files, and
to cache read-only attributes and contents of directories and links. |
Byte Range The current number of byte range locks held for each metadata server.
These locks are used to implement lock system calls and have no direct effect
on the contents or attributes of SAN File System objects or other file system
operations. |
Total All lock types per metadata server. |