@Rocky Shared-data mode running on kubernetes. Everything is fine with 3.5.15, however, when I try to upgrade to 4.1.0, fe starts but cn segfaults during startup

It appears you have encountered a known critical issue with the StarRocks 4.1.0 release. Specifically, there is an open bug (GitHub Issue #71731) reported recently (mid-April 2026) where the Compute Node (CN) segfaults immediately during startup, even before reaching the

main()

function. Why this is happening * Static Initialization Bug: The segfault occurs during C++ static initialization. This is why you see no logs in

<http://cn.INFO|cn.INFO>

or `cn.out`—the process crashes before the logging system (glog) can even start. * Version 4.1.0 Regression: This is a regression specifically in the 4.1.0 build. Since your environment works perfectly with 3.5.15, it is not a fundamental hardware incompatibility (like missing AVX2), but rather a bug in how global objects are initialized in the 4.1.0 binaries. * Kubernetes/Ubuntu Images: The issue has been confirmed to affect the official

starrocks/cn-ubuntu:4.1.0

images used in Kubernetes deployments. Recommended Actions 1. Rollback: Until a fix is released (likely in a 4.1.1 patch), it is highly recommended to stay on 3.5.15 or use the 4.0.x branch (e.g., 4.0.9), which is stable. 2. Architecture Check: Verify if you are running on ARM64 (Graviton/Aarch64) or x86_64. Some recent segfaults in the 4.x series have been specific to ARM64 optimizations. If you are on ARM, ensure you are using the corresponding architecture-specific image. 3. Check dmesg/Core Dumps: If you need more detail for a bug report, check the Kubernetes node's

dmesg

or look for a core dump. You will likely see the crash originating in a shared library or a static constructor. 4. Monitor Issue #71731: Keep an eye on the StarRocks GitHub repository for the resolution of this specific startup crash. Note on Upgrading to 4.x When you eventually move to 4.x (once the startup bug is fixed): * JDK 17 Requirement: Ensure your environment uses JDK 17, as StarRocks 3.5+ and 4.x require it. * JAVA_OPTS: Make sure your

cn.conf

(or Helm chart) includes the required reflective access flags:

bash
    --add-opens=java.base/java.util=ALL-UNNAMED
    --add-opens=java.base/java.nio=ALL-UNNAMED
    --add-opens=java.base/sun.nio.ch=ALL-UNNAMED

* Downgrade Caution: Note that once you successfully upgrade to 4.1, you cannot downgrade to any version below 4.0.6 due to internal changes in metadata layout (tablet splitting/distribution). References • release_notes/release-4.0.md