Scanner Backlog Impacts Metadata Accuracy
infoMinIO's scanner provides metadata for capacity reporting and lifecycle management, but scanner backlogs (objects_to_scan growing) delay accurate usage reporting and ILM policy execution.
Monitor minio.scanner.objects_scanned vs minio.scanner.objects_to_scan divergence. Alert when scan backlog exceeds threshold (e.g., >1M objects pending for >6 hours) or when minio.scanner.buckets_finished stops increasing for extended periods.
Scanner runs during idle periods by default. Check if cluster is under sustained high load preventing scanner progress. Review scanner metrics in MinIO Console (Monitoring -> Metrics -> Scanner). Consider temporarily reducing client workload to allow scanner catchup if metadata accuracy is critical. No manual scanner trigger exists; scanner auto-adjusts to load.