@Rocky and Other I see that 4.1.1 is finally released in Docker hub. Maybe it'll take few days to come up on GitHub due to long release notes and pramotion. Has anyone tried 4.1.1? Do we have any Known issues?

Yes, StarRocks 4.1.1 has indeed been released to address a critical issue identified in version 4.1.0. Why 4.1.1 is Important The primary reason for the 4.1.1 release is a critical fix for container environments. In version 4.1.0, an unstable load order issue caused BE (Backend) processes to fail to start reliably in Docker/Kubernetes environments. * Known Issue in 4.1.0: BE start failure in containers (#71825). * Status in 4.1.1: This is fixed. If you are running on Docker, you should use 4.1.1 and skip 4.1.0 entirely. Critical Warning: Downgrade Limitation Before you upgrade, please be aware of a major backward compatibility change introduced in the 4.1 series: * Internal Data Layout Changes: Version 4.1 introduces new tablet splitting and distribution mechanisms. * Downgrade Restriction: After upgrading to v4.1, you cannot downgrade to any v4.0 version earlier than v4.0.6. Downgrading to versions prior to 4.0.6 will cause metadata and storage incompatibility, potentially leading to cluster failure or data loss. Known Issues & Observations Since 4.1.1 is a very recent maintenance release (as of June 2026), a comprehensive "Known Issues" list specifically for it may still be in development. however, keep the following in mind: 1. Release Notes Delay: It is normal for the detailed release notes to appear on GitHub slightly after the Docker image is pushed. 2. Recent Bug Fixes in 4.1 Branch: Recent fixes in the 4.1 line (which should be included in 4.1.1) addressed: * Data loss scenarios during tablet splits in specific range distribution setups (#71135). * Memory leaks in

DefaultValueColumnIterator

for complex types (#71142). * Potential hash table data loss during aggregation spills (#70851). * Issues with

AggregateJoinPushDownRule

rewriting materialized views over Iceberg tables (#71856). Recommendation: If you are moving to the 4.1 branch for features like the new Native Iceberg Variant type or Adaptive Multi-Tenant Data Management, 4.1.1 is the stable starting point for production. As always, perform a backup and test the upgrade in a staging environment first, especially given the downgrade restrictions. References • release_notes/release-3.5.md • release_notes/release-3.3.md • release_notes/release-4.0.md

@Rocky 4.1.1 also have patches which are included in 4.0.10(which released after 4.1.0 but before 4.1.1) right

Yes, that is correct. StarRocks follows a maintenance policy where bug fixes and stability patches are cherry-picked across active branches. Because v4.0.10 (released May 9, 2026) preceded v4.1.1 (released mid-to-late May 2026), the patches included in the 4.0.10 maintenance cycle are rolled into v4.1.1. Key Patches Included in both 4.0.10 and 4.1.1: Based on the release logs for that cycle, several critical fixes that reached 4.0.10 were also integrated into the 4.1 branch for the 4.1.1 release: * Memory & Stability: * Fixed a

BE SIGSEGV

(crash) in

PartitionedSpillerWriter

during spillable aggregations with skew elimination (#74074). * Optimized

CatalogRecycleBin

to prevent overhead during tablet scheduling and cleanup (#72128). * Added an Avro schema cache for Iceberg to reduce redundant memory allocations during partition loads (#72215). * Security & Connectivity: * Credential Redaction: Cloud storage secrets are now redacted in error messages for

INSERT INTO FILES

, preventing sensitive data from leaking into logs (#71245). * LDAP Improvements: Added support for LDAP direct bind authentication via DN patterns (#71589). * Data Correctness: * Fixed an issue where queries against "insert-only" ACID Hive tables could return incorrect results; these now return an explicit error instead of silent data gaps (#71460). * Corrected binary encoding for

VARBINARY

columns nested inside complex types (ARRAY, MAP, STRUCT) to prevent parsing issues in MySQL clients (#71346). Summary for Docker Users If you are using the Docker image, 4.1.1 is the mandatory version to use if you want the 4.1 feature set (like range-based auto-splitting or Native Iceberg Variant support). Version 4.1.0 had a known container-specific load order issue (#71825) that caused BE processes to fail at startup; 4.1.1 resolves this while bringing in the stability fixes from the 4.0.10 cycle. References • release_notes/release-4.0.md • release_notes/release-4.1.md • administration/Maintenance.md