SuperCluster: Best Practice - Establish Threshold Alerts on the ZFSSA
(Doc ID 2288649.1)
Last updated on MAY 02, 2018
Applies to:Oracle SuperCluster Specific Software - Version 1.x to 2.x [Release 1.0 to 2.0]
Oracle SuperCluster M7 Hardware - Version All Versions to All Versions [Release All Releases]
SPARC SuperCluster T4-4 Half Rack - Version All Versions to All Versions [Release All Releases]
SPARC SuperCluster T4-4 Full Rack - Version All Versions to All Versions [Release All Releases]
SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Establish Threshold Alerts on the ZFSSA to ensure that availability and performance are not degraded for iSCSI LUNs consumed by SuperCluster tenant rpools
A properly monitored and maintained internal ZFSSA will ensure the optimum operations of all LDoms and zones that consume iSCSI LUNs off the internal ZFSSA. While the internal ZFSSA is also available for general-purpose shared storage with NFS, the single JBOD ZFSSA is not designed for heavy IO for extended periods of time. Proper monitoring of the utilization will also let you know which one of your virtual tenants may be using the ZFSSA excessively, negatively impacting other tenants on the SuperCluster.
An improperly utilized ZFSSA without monitoring can lead to one or many tenants experiencing local IO operations that are so slow that rpools can become non responsive. This could have all sorts of database and or application repercussions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document