docker starrocks 主节点启动 报错

这种报错如何解决?比较着急 ,请教大佬改怎么弄?

2022-11-10 03:17:50,434 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:17:52,435 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:17:55,536 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:17:57,536 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:17:59,537 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:01,537 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:03,538 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:05,538 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:07,553 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:09,553 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:11,554 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:13,554 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:15,555 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:17,555 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:19,556 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:21,556 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:23,557 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:25,557 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:27,558 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:29,559 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:31,559 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:33,563 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:35,564 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:37,564 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:39,565 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:41,566 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false
2022-11-10 03:18:43,566 INFO (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [GlobalStateMgr.waitForReady():898] wait globalStateMgr to be ready. FE type: INIT. is ready: false

看下最新的日志信息,这是fe初始化的日志信息

集群中有几台FE?集群是哪个版本?

2.4 版本3个fe

最新的日志信息 就是这样子的 一直打印这些

tail -f fe.warn.log
2022-11-10 03:31:55,098 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [StateChangeExecutor.notifyNewFETypeTransfer():45] notify new FE type transfer: UNKNOWN
2022-11-10 03:32:09,043 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [ColocateTableIndex.cleanupInvalidDbOrTable():879] remove 0 invalid tableid: []
2022-11-10 03:36:45,907 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [StateChangeExecutor.notifyNewFETypeTransfer():45] notify new FE type transfer: UNKNOWN
2022-11-10 03:36:58,250 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [ColocateTableIndex.cleanupInvalidDbOrTable():879] remove 0 invalid tableid: []
2022-11-10 03:39:38,946 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [StateChangeExecutor.notifyNewFETypeTransfer():45] notify new FE type transfer: UNKNOWN
2022-11-10 03:39:52,506 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [ColocateTableIndex.cleanupInvalidDbOrTable():879] remove 0 invalid tableid: []
2022-11-10 03:45:05,978 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [StateChangeExecutor.notifyNewFETypeTransfer():45] notify new FE type transfer: UNKNOWN
2022-11-10 03:45:19,114 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [ColocateTableIndex.cleanupInvalidDbOrTable():879] remove 0 invalid tableid: []
2022-11-10 06:47:58,229 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [StateChangeExecutor.notifyNewFETypeTransfer():45] notify new FE type transfer: UNKNOWN
2022-11-10 06:48:11,664 WARN (UNKNOWN 172.16.62.201_9010_1667377631674(-1)|1) [ColocateTableIndex.cleanupInvalidDbOrTable():879] remove 0 invalid tableid: []

现在集群是什么状态,fe启动不起来?可以启动的话,show frontends 看下,ip请码住

image

连不上这台服务器

就这一直打印这些日志

fe集群全挂了,be也挂了,我想先启动fe 的leader节点
,就是一直打印上边哪些日志

这个是新部署的集群么?tail -f fe.warn.log 最新的日志您发下,三个fe都启动失败,fe.info日志中信息请发下

我也是这个问题,谢谢

1赞

请您单发一个帖子描述下您的问题

大佬,我也遇到,你有解决方法吗

现在这个问题解决了吗?我也遇到了

fe版本2.4.3,k8s中,delete 3个fe pod,节点启动失败,log一直报这个错误 2023-03-20 07:47:36,964 INFO (UNKNOWN starrockscluster-fe-0.fe-domain-search.tmp-mgr.svc.cluster.local_9010_1679293072192(-1)|1) [GlobalStateMgr.waitForReady():1019] wait globalStateMgr to be ready. FE type: INIT. is ready: false

现在刷的还是这个报错吗?这个是fe的角色还没有选出来,主节点的bdb文件夹数据量大吗?