@Kevin Cai and Starrocks Team, while upgrading the Starrocks version from 4.0.1 to 4.1.0, the CN pods are not coming healthy due to below error:

[Thu Apr 23 13:20:13 UTC 2026] Process conf file cn.conf ...
[Thu Apr 23 13:20:13 UTC 2026] Add myself (kube-starrocks-cn-0.kube-starrocks-cn-search.olymsre01.svc.cluster.local:9050) into FE ...
ERROR 1064 (HY000) at line 1: Compute node already exists with same host kube-starrocks-cn-0.kube-starrocks-cn-search.olymsre01.svc.cluster.local and port 9050
[Thu Apr 23 13:20:13 UTC 2026] run start_cn.sh
start time: Thu Apr 23 13:20:13 UTC 2026, server uptime:  13:20:13 up 1 day,  6:14,  0 user,  load average: 0.01, 0.06, 0.06
Run with JEMALLOC_CONF: 'percpu_arena:percpu,oversize_threshold:0,muzzy_decay_ms:5000,dirty_decay_ms:5000,metadata_thp:auto,background_thread:true,prof:true,prof_active:false'
/opt/starrocks/cn_entrypoint.sh: line 165:    27 Segmentation fault      (core dumped) $STARROCKS_HOME/bin/start_cn.sh $addition_args

I am running Starrocks on Graviton instances. Will that be an issue? I see same issue 71731 in closed state.

it's closed, and the fix will be included in next patch release (v4.1.1)

@Kevin Cai Thanks for the update. Is there any ETA when the v4.1.1 going to be released?

not yet. usually it will a few weeks in between two patch releases.

Okay. Just for information, is this issue related to AVX2 instructions not being supported on Graviton instances?

no. it is because of global static variables initialization chaos, a typical headache in c++ application.

So this issue can come on amd64 machines as well?

yes

@Kevin Cai is there any chance of a re-release of 4.1.0 with just the patch for the containerized boot issue?

I don't think so. may need to wait 4.1.1 or build your own binary with the patch fix.

Any update on when 4.1.1 will be releasing with the fix?

current ETA is end of the month.

Hi @Kevin Cai Is there any ETA of the new release 4.1.1 with this issue fixed?

@Kevin Cai Is this still on-track for the end of the month? We have some work we are trying to schedule on our end so just want to get a sense for if the working 4.1.x CN image will be available this week.

yeah, still target to end of the month.

Hi @Kevin Cai Is there any ETA of the new release with this issue fixed?

4.1.1 is already available on github two weeks ago. you should check it out.