What are the NetApp Element Software Garbage Collection (GC) Events?
- Views:
- 507
- Visibility:
- Public
- Votes:
- 0
- Category:
- element-software
- Specialty:
- solidfire
- Last Updated:
- 8/28/2023, 8:01:02 PM
Applies to
NetApp Element Software
Answer
The following are the Element Software Garbage Collection Events (gcEvents) that can be seen in SolidFire Active IQ and the Element UI:
- GCStarted = Garbage Collection has been initiated. This will automatically occur every hour at the top of the hour.
- GC Cluster Coordination Complete = All participating Slice and Block Services are confirmed by Garbage Collection and GC is ready. This message should immediately follow GCStarted.
- GCCompleted = Garbage Collection complete and you should see one of these events for every participating block service (BS) that is noted in the GCStarted event.
- GCStartDeferred – GC already in progress* = GC start was deferred due to GC already running
- GCAborted = any reason GC failed to start. Information on the cause of the abort will be found in the Details section of the Active IQ Events and Element UI Event Log.
- GCFailed - Garbage collection started but failed to complete. Generally, this can be seen with intermittent network-related timeouts such as issues found in the following KB: Intermittent unresponsiveService is reported
*Note – GCStartDeferred is introduced in Element Software 12.7. Prior versions would report a GCAborted Event if the GC was already running when the next GC start initiated.
Additional Information
Should Garbage Collection fail to complete in 12 or more hours, a support case will be created for NetApp Support to investigate.