Hi good people, I hope you are all doing well. I h...
# questions-and-troubleshooting
y
Hi good people, I hope you are all doing well. I had great experiences with StarRocks on CelerData's platform, but now I am trying to run the open source version helm chart on AWS K8s and I am in a little bit of a pickle. I am implementing the shared everything architecture, using the CN nodes, and I am setting the path to S3. I am using the latest version,
4.0.2
When creating a table, it takes a long time, and I mean LONG. So long, sometimes it times out after 15 minutes. It's anywhere between 3-15+ minutes. This is very strange behaviour and after 2 days of trying, I am pretty much at a loss. Did anyone of you encounter this strange behavior ? Could anyone point in a direction what to look for ?
I got this working using version 3.3 using the same configuration. So what changed between those versions, and why didn't this happen to anyone else ?
a
In my case, I’m using 4.0.1 version, but It’s work well for me. How about downgrading your version to 4.0.1?
And, Did you bump 3.3 to 4.0.2 directly?
y
Hi Henry, I am glad you wrote back. I got it to work for a short time using version 4.0.2, but now it's not working again. I am facing a lot of issues trying to create a FE-CN cluster on K8s using helm. The most basic things are somehow not working for me. The statistics database is empty and I just can't get the cluster to work. Can you somehow help me out ?
a
hello, are you using starrocks operator helm chart? 👀https://artifacthub.io/packages/helm/kube-starrocks/operator
y
Yes I am. I am using the standard helm chart with 4.0-latest images. I can send you a redacted values files if that might help.
a
Yes. I’m interested in your values. As I understand it, when the cluster is set up with version 4.0.2, DDL commands are running slowly. Is that correct?
y
Well, it's even worse. My table creation time out for some reason.
So the statistics tables don't even get created
Copy code
2025-12-30 09:08:52.156+02:00 WARN (statistics meta manager|36) [StatisticsMetaManager.refreshStatisticsTable():529] create statistics table table_statistic_v1 failed
and
Copy code
2025-12-30 09:09:12.201+02:00 ERROR (TableKeeper|121) [TableKeeper.run():76] error happens in Keeper: com.starrocks.common.DdlException: Table creation timed out. unfinished replicas(1/1): 10083(yoav-starrocks-cn-0.yoav-starrocks-cn-search.default.svc.cluster.local)  timeout=10s
The folder in the s3 bucket does even get created.
Copy code
2025-12-30 09:12:52.598+02:00 WARN (statistics meta manager|36) [StatisticsMetaManager.createSampleStatisticsTable():165] Failed to create sample statistics, 
com.starrocks.common.DdlException: Table creation timed out. unfinished replicas(1/1): 10358(yoav-starrocks-cn-0.yoav-starrocks-cn-search.default.svc.cluster.local)  timeout=10s
 You can increase the timeout by increasing the config "tablet_create_timeout_second" and try again.
To increase the config "tablet_create_timeout_second" (currently 10), run the following command:
admin set frontend config("tablet_create_timeout_second"="20")
Copy code
or add the following configuration to the fe.conf file and restart the process:
tablet_create_timeout_second=20
Copy code
at com.starrocks.task.TabletTaskExecutor.waitForFinished(TabletTaskExecutor.java:434) ~[starrocks-fe.jar:?]
	at com.starrocks.task.TabletTaskExecutor.sendCreateReplicaTasksAndWaitForFinished(TabletTaskExecutor.java:311) ~[starrocks-fe.jar:?]
	at com.starrocks.task.TabletTaskExecutor.buildPartitionsSequentially(TabletTaskExecutor.java:113) ~[starrocks-fe.jar:?]
	at com.starrocks.server.LocalMetastore.buildPartitions(LocalMetastore.java:1864) ~[starrocks-fe.jar:?]
	at com.starrocks.server.OlapTableFactory.createTable(OlapTableFactory.java:778) ~[starrocks-fe.jar:?]
	at com.starrocks.server.LocalMetastore.createTable(LocalMetastore.java:852) ~[starrocks-fe.jar:?]
	at com.starrocks.statistic.StatisticsMetaManager.createSampleStatisticsTable(StatisticsMetaManager.java:163) ~[starrocks-fe.jar:?]
	at com.starrocks.statistic.StatisticsMetaManager.createTable(StatisticsMetaManager.java:442) ~[starrocks-fe.jar:?]
	at com.starrocks.statistic.StatisticsMetaManager.refreshStatisticsTable(StatisticsMetaManager.java:526) ~[starrocks-fe.jar:?]
	at com.starrocks.statistic.StatisticsMetaManager.runAfterCatalogReady(StatisticsMetaManager.java:556) ~[starrocks-fe.jar:?]
	at com.starrocks.common.util.FrontendDaemon.runOneCycle(FrontendDaemon.java:78) ~[starrocks-fe.jar:?]
	at com.starrocks.common.util.Daemon.run(Daemon.java:98) ~[starrocks-fe.jar:?]
I did try to set
tablet_create_timeout_second
to 60 even, and that didn't help either