MinIO AIStor RELEASE.2025-08-21T02-50-21Z focuses on improving operational visibility, automation capabilities, and stability through new APIs, enhanced metrics, and critical bug fixes including an important XFS filesystem compatibility fix for Linux kernel 6.14+.
Answer
This release delivers key operational improvements for enterprise deployments, including configuration drift detection, enhanced KMS monitoring, and new API usage analytics. Organizations running Linux kernel 6.14+ with XFS filesystems should upgrade to resolve a critical compatibility issue.
New Features
Configuration Drift Detection
What
A new configuration hash in the server info endpoint enables automated validation to identify configuration changes across the cluster.
This allows automation tools and monitoring systems to:
- Detect when configurations differ between nodes
- Identify unintended configuration changes
- Validate configuration consistency across deployments
Availability
Available in this release.
Why
Configuration drift is a common operational challenge in distributed systems. When nodes have different configurations, it can lead to:
- Inconsistent behavior across the cluster
- Difficult-to-diagnose issues
- Compliance and audit failures
- Unexpected performance differences
Providing a configuration hash enables automated detection and alerting for drift conditions.
What This Means for Customers
- Automated drift detection for configuration management tools
- Faster troubleshooting by identifying configuration inconsistencies
- Better compliance posture with configuration validation
- Simplified auditing of cluster configuration state
KMS Monitoring Metrics
What
Prometheus metrics now track successful and failed KMS requests, providing improved observability of server-side encryption operations.
New metrics include:
- KMS request success counts
- KMS request failure counts
- KMS operation latency
Availability
Available in this release.
Why
When using server-side encryption with external KMS, visibility into KMS operations is critical for:
- Identifying encryption-related issues before they impact applications
- Capacity planning for KMS infrastructure
- Troubleshooting failed encryption/decryption operations
- Meeting SLA requirements for encrypted workloads
What This Means for Customers
- Proactive alerting on KMS issues
- Better capacity planning for KMS infrastructure
- Faster root cause analysis for encryption-related problems
- SLA tracking for encryption operations
API Usage Analytics Endpoint
What
A new endpoint /minio/admin/v4/api/stats delivers aggregated, cluster-wide API metrics for the last minute and last 24 hours.
This provides:
- Per-API operation statistics
- Request counts and latencies
- Cluster-wide aggregation
- Rolling time windows
Availability
Available in this release.
Why
Understanding API usage patterns is essential for:
- Capacity planning and resource allocation
- Identifying hot spots and optimization opportunities
- Chargeback and showback reporting
- Performance analysis and tuning
What This Means for Customers
- Better visibility into cluster usage patterns
- Simplified capacity planning with aggregated metrics
- Chargeback support with detailed API statistics
- Performance optimization based on actual usage
Improvements
Enhanced Batch Catalog Reporting (v2 API)
What
Batch catalog reporting via the v2 API now supports additional metadata fields:
- Bucket key status - Encryption key information
- KMS key ARN - Key Management Service key identifier
Updated mc batch generate catalog produces v2 templates with clearer prefix guidance.
Availability
Available in this release.
Why
Rich metadata in catalog reports enables better data governance, compliance reporting, and encryption auditing across large namespaces.
What This Means for Customers
- Better encryption auditing with key status in reports
- Improved compliance reporting with richer metadata
- Easier catalog job creation with updated templates
Improved Batch Job Error Messages
What
More specific error messaging for misconfigured batch jobs, making it easier to identify and fix configuration issues.
Availability
Available in this release.
Why
Clear error messages reduce troubleshooting time and help operators quickly resolve configuration issues.
What This Means for Customers
- Faster troubleshooting of batch job issues
- Reduced operational overhead for job management
Disk Reordering Tool Enhancement
What
The disk reordering tool now supports format.bin metadata, expanding its utility for storage maintenance operations.
Availability
Available in this release.
Why
Storage maintenance operations sometimes require disk reordering. Supporting format metadata makes this tool more useful in complex maintenance scenarios.
What This Means for Customers
- More flexible storage maintenance options
- Better tooling for complex disk operations
Critical Bug Fixes
XFS Filesystem Compatibility (Linux Kernel 6.14+)
What
Resolved an XFS filesystem compatibility issue on Linux kernel 6.14+ that could cause operational problems.
Availability
Available in this release.
Why
Linux kernel 6.14 introduced changes that affected XFS behavior. Organizations running newer kernels with XFS could experience issues without this fix.
What This Means for Customers
- Required upgrade for environments running Linux kernel 6.14+ with XFS
- Stable operation on newer Linux distributions
- Future compatibility with upcoming kernel versions
Site Replication Data Race Fix
What
Fixed a data race condition in site-to-site replication peer configuration that could cause inconsistent replication behavior.
Availability
Available in this release.
Why
Data races in replication configuration could lead to unpredictable behavior and potential data consistency issues in multi-site deployments.
What This Means for Customers
- More reliable site replication in multi-site deployments
- Consistent replication behavior across configuration changes
Additional Bug Fixes
| Issue | Fix |
|---|---|
| Empty event file creation | Prevented during restarts |
| OpenTelemetry trace handling | Corrected trace processing |
| Restart loops with older operators | Eliminated compatibility issues |
| Failed upload cleanup | Automatic cleanup of temporary data |
| Drive offline duration calculations | Improved accuracy for healing |
| Replication metrics | Restored to v3 endpoint |
Breaking Changes
Stricter Batch Validation
What
Batch job configurations with overlapping prefixes are now rejected. Job definitions require distinct prefixes.
Impact
Existing batch jobs with overlapping prefixes will fail validation and need to be updated.
Migration
Review and update batch job definitions to ensure prefixes do not overlap.
API Field Rename
What
The field queuedInProgress has been renamed to inProgress in bucket statistics responses.
Impact
Applications parsing bucket statistics responses need to be updated to use the new field name.
Migration
Update any code or scripts that reference queuedInProgress to use inProgress instead.
Upgrade Recommendations
| Environment | Recommendation |
|---|---|
| Linux kernel 6.14+ with XFS | Upgrade immediately |
| Multi-site replication | Upgrade soon for race condition fix |
| Using batch jobs with overlapping prefixes | Review and update jobs before upgrade |
| Parsing bucket statistics API | Update code before upgrade |
| All other environments | Upgrade at next maintenance window |
References
Summary
MinIO AIStor RELEASE.2025-08-21 delivers:
- Configuration drift detection for automated cluster validation
- KMS monitoring metrics for encryption observability
- API usage analytics endpoint for cluster-wide statistics
- Enhanced batch catalog reporting with encryption metadata
- Critical XFS fix for Linux kernel 6.14+ compatibility
- Site replication race condition fix for multi-site deployments
Note: Review breaking changes for batch job validation and API field renames before upgrading.
For upgrade assistance, contact your MinIO support team.