Skip to main content
NetApp Knowledge Base

High FabricPool latency while promoting data back to performance tier

  1. Last updated
  2. Save as PDF
Views:
152
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  •  FabricPool
  • AWS

Issue

  • Reads to tiered data fail and high latency is observed:
EMS:
 
[Node-01: OscHighPriThreadPool: wafl.ca.latency.threshold:notice]: Measured latency from cloud (104748 msec) more than threshold (5000 msec) (aggregate: "aggr_data1_01", aggregate uuid: "AGGR-UUID", object store: "ObjectStore")
  • FabricPool read latency is a function of connectivity to the cloud tier

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.