Skip to main content
NetApp Knowledge Base

18 minutes delay between object-store going unavailable and available

  1. Last updated
  2. Save as PDF
Views:
367
Visibility:
Public
Votes:
8
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • Fabricpool
  • StorageGRID
  • Virtual gateway nodes
  • HA-groups

Issue

Ontap EMS logs will show close to 18 minutes delay between Object Store going unavailable and back to available

Sat Apr 10 09:27:07 +0200 [mc-netapp-a01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp-mc-netapp-a-primary" from node 727010ba-db24-11ea-b4cf-d039ea1ef264. Reason: Connection unavailable.
Sat Apr 10 09:44:55 +0200 [mc-netapp-a01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "fp-mc-netapp-a-primary" from node 727010ba-db24-11ea-b4cf-d039ea1ef264.
 
 
Tue Apr 13 20:12:24 +0200 [mc-netapp-a01: OscHighPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp-mc-netapp-a-primary" from node 727010ba-db24-11ea-b4cf-d039ea1ef264. Reason: Connection unavailable.
Tue Apr 13 20:30:10 +0200 [mc-netapp-a01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "fp-mc-netapp-a-primary" from node 727010ba-db24-11ea-b4cf-d039ea1ef264.
 
Object Store goes unavailable after 1000 failing S3 ops or after 2 minutes not responding, whichever comes first.
In the latter situation the total time of Object Store being unavailable is 20 minutes (2 minutes for the first Unavailable message + 18 minutes later for the Available message)
 
Usual behavior is that a HEAD call is made after going unavailable, which unless there is a more serious issue will be successful and the Object Store will be marked Available again with 1-2 seconds.

 

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.