【已解决】wait catalog to be ready. feType:UNKNOWN isReady:false

Viewed 149

大家好:
请教下,我用官方推荐的Helm部署的doris,chart版本是1.6.0,doris版本是2.1.2,目前只配置了1个fe和1个be,启动没有问题,但是重启doris fe后因pod IP变了导致启动不了,具体信息如下:

2024-08-15 03:50:16,138 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1 reason:
2024-08-15 03:50:26,145 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:101 reason:
2024-08-15 03:50:36,152 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:201 reason:
2024-08-15 03:50:46,159 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:301 reason:
2024-08-15 03:50:56,167 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:401 reason:
2024-08-15 03:51:06,174 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:501 reason:
2024-08-15 03:51:16,180 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:601 reason:
2024-08-15 03:51:26,188 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:701 reason:
2024-08-15 03:51:36,195 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:801 reason:
2024-08-15 03:51:46,202 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:901 reason:
2024-08-15 03:51:56,209 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1001 reason:
2024-08-15 03:52:06,216 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1101 reason:
2024-08-15 03:52:16,223 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1201 reason:
2024-08-15 03:52:26,230 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1301 reason:
2024-08-15 03:52:36,238 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1401 reason:
2024-08-15 03:52:46,245 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1501 reason:
2024-08-15 03:52:56,252 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1601 reason:
2024-08-15 03:53:06,260 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1701 reason:
2024-08-15 03:53:16,267 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1801 reason:
2024-08-15 03:53:26,275 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:1901 reason:
2024-08-15 03:53:36,282 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2001 reason:
2024-08-15 03:53:46,290 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2101 reason:
2024-08-15 03:53:56,297 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2201 reason:
2024-08-15 03:54:06,305 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2301 reason:
2024-08-15 03:54:16,312 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2401 reason:
2024-08-15 03:54:26,319 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2501 reason:
2024-08-15 03:54:36,327 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2601 reason:
2024-08-15 03:54:46,334 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2701 reason:
2024-08-15 03:54:56,340 INFO (UNKNOWN fe_6c1f1e68_4e90_476d_a96f_040cda03b469(-1)|1) [Env.waitForReady():1063] wait catalog to be ready. feType:UNKNOWN isReady:false, counter:2801 reason:
/opt/apache-doris/fe/bin/start_fe.sh: line 265: 119 Killed ${LIMIT:+${LIMIT}} "${JAVA}" ${final_java_opt:+${final_java_opt}} -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError="kill -9 %p" ${coverage_opt:+${coverage_opt}} org.apache.doris.DorisFE ${HELPER:+${HELPER}} ${OPT_VERSION:+${OPT_VERSION}} "${METADATA_FAILURE_RECOVERY}" "$@" < /dev/null

我的疑问是如何解决k8s重启doris fe后pod IP变动,导致doris fe无法启动的问题,有人遇到过吗?求教

1 Answers

你有没有configmap 挂载 fe.conf?在里面需要添加 开启 fqdn的 配置,可以避免这个问题