StarRocks 4.1.0: Since we upgraded (clean install and backup from restore) we noticed that every night if there is an error in our ETL job, the front end shuts off... anyone knows why it just switches the FE off and we have to manually start it back? Is there a new setting for FE? After switching back on it works fine. Going to try and find something from FE log. MetadataMgr.getOptionalMetadata():204] Failed to get table_function_catalog catalog 2026-05-01 033854.484+02:00 ERROR (starrocks-mysql-nio-pool-1410|12803) [MetadataMgr.getOptionalMetadata():204] Failed to get table_function_catalog catalog 2026-05-01 033855.143+02:00 ERROR (starrocks-mysql-nio-pool-1410|12803) [MetadataMgr.getOptionalMetadata():204] Failed to get table_function_catalog catalog 2026-05-01 033855.144+02:00 ERROR (starrocks-mysql-nio-pool-1410|12803) [MetadataMgr.getOptionalMetadata():204] Failed to get table_function_catalog catalog 2026-05-01 061145.449+02:00 ERROR (memory-usage-tracker|206) [Daemon.run():100] daemon thread got exception. name: memory-usage-tracker 2026-05-01 061145.450+02:00 ERROR (publish-version-daemon|113) [Daemon.run():100] daemon thread got exception. name: publish-version-daemon 2026-05-01 061145.449+02:00 ERROR (es-repository|182) [Daemon.run():100] daemon thread got exception. name: es-repository 2026-05-01 061145.449+02:00 ERROR (TabletWriteLogHistorySyncer|190) [Daemon.run():100] daemon thread got exception. name: TabletWriteLogHistorySyncer 2026-05-01 061145.451+02:00 ERROR (JournalWriter|281) [JournalWriter$1.runOneCycle():92] got exception when trying to write one batch, will exit now. 2026-05-01 061146.006+02:00 ERROR (starrocks-mysql-nio I/O-1|355) [MySQLReadListener.handleEvent():97] Unexpected error in MySQLReadListener 2026-05-01 101248.912+02:00 WARN (state-change-executor|237) [AlterMVJobExecutor.inactiveRelatedMaterializedViewsRecursive():1274] Skip to inactive related materialized views because of base table/view T_ERRORS is changed or dropped in the leader backgroud, isLeader: false, isReplay, reason:true 2026-05-01 101249.057+02:00 WARN (state-change-executor|237) [AlterMVJobExecutor.inactiveRelatedMaterializedViewsRecursive():1274] Skip to inactive related materialized views because of base table/view T_ERRORS is changed or dropped in the leader backgroud, isLeader: false, isReplay, reason:true 2026-05-01 101249.657+02:00 WARN (state-change-executor|237) [AlterMVJobExecutor.inactiveRelatedMaterializedViewsRecursive():1274] Skip to inactive related materialized views because of base table/view T_ERRORS is changed or dropped in the leader backgroud, isLeader: false, isReplay, reason:true 2026-05-01 101249.879+02:00 WARN (cache-stats-0|277) [FragmentInstanceExecState.waitForDeploymentCompletion():325] exec plan fragment failed, errmsg=fail to init reader. tablet=10032.642944190.f449ae5063961b9c-d4ad3abb2d09c6b4res=Not found: get_applied_rowsets(version 5527) failed tablet:10032 #version:1 [6070.2 6070.2@0 6070.2] #pending:0 cost (0/0/0) backend [id=10001] [host=si-starrocks.medis-domena.loc], code=INTERNAL_ERROR, fragmentId=F00, backend=si-starrocks.medis-domena.loc:9060 2026-05-01 101249.879+02:00 WARN (cache-stats-1|278) [FragmentInstanceExecState.waitForDeploymentCompletion():325] exec plan fragment failed, errmsg=fail to init reader. tablet=10032.642944190.f449ae5063961b9c-d4ad3abb2d09c6b4res=Not found: get_applied_rowsets(version 5527) failed tablet:10032 #version:1 [6070.2 6070.2@0 6070.2] #pending:0 cost (0/0/0) backend [id=10001] [host=si-starrocks.medis-domena.loc], code=INTERNAL_ERROR, fragmentId=F00, backend=si-starrocks.medis-domena.loc:9060 2026-05-01 101249.905+02:00 ERROR (stats-cache-refresher-0|272) [TableStatsCacheLoader.lambda$asyncLoadAll$2():83] com.starrocks.sql.analyzer.SemanticException: Getting analyzing error. Detail message: Statistics query fail | Error Message [[reason=INTERNAL_ERROR] [msg=null]] | QueryId [019de298-f74f-7704-9372-b329d4577835] | SQL [select cast(3 as INT), partition_id, any_value(row_count) FROM column_statistics WHERE table_id = 60239 and partition_id in (287087) GROUP BY partition_id].

ç2026-05-01 06:11:45.451+02:00 ERROR (JournalWriter|281) [JournalWriter$1.runOneCycle():92] got exception when trying to write one batch, will exit now.

This is the key line that cause FE exits. try to find all the logs related to this JournalWriter, see what else happened before exit.