Skip to main content
NetApp Knowledge Base

Resolving excessive FabricPool object store network latency

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

Applies to

  • ONTAP 9
  • StorageGRID FabricPool

Issue

  • EMS message is triggered: ARS is triggered when latency is between 5 and 10 seconds detected when using FabricPool..
Fri Sep 06 09:47:54 MDT [node1: OscHighPriThreadPool: wafl.ca.latency.threshold:notice]: Measured latency from cloud (5915 msec) more than threshold (1000 msec) (aggregate: "node1_ssd", aggregate uuid: "563a8dfc-97d1-45c9-921a-5ced93b34f5c", object store: "node_grid")
  • If latency is severe, timeout errors may also be seen causing users to see increased NFS/CIFS latency and potentially preventing access to data on the object-store

[Cluster01-01: OscLowPriThreadPool_4: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "S3_objectstore" from node <uuid>. Reason: Operation Timedout.

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.