beatum opened a new issue, #70285: URL: https://github.com/apache/doris/issues/70285
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version ## Environment - **Operating system:** CentOS Linux 8 - **Docker version:** 26.1.3 - **Affected image:** `apache/doris:be-4.1.5` - **Working image:** `apache/doris:4.0.3-all-slim` - **Deployment type:** Docker, single-node deployment ### What's Wrong? The container created from `apache/doris:be-4.1.5` starts the BE process, but the Docker entrypoint continues displaying: ```text Waiting for BE node... ``` After approximately 60 seconds, the entrypoint reports: ```text [ERROR] BE node failed to start ``` The container then exits or restarts according to its Docker restart policy. The BE logs appear to show that the BE process is running during this period. For example, it processes workload-group updates, reports WAL status, checks dictionary status, and reads storage information. I do not see an obvious fatal error or crash in the provided BE log before the entrypoint timeout occurs. The older image `apache/doris:4.0.3-all-slim` works correctly in the same environment. ## Relevant logs ```text 2026-11-05T17:28:46+08:00 [INFO] [Entrypoint]: Waiting for BE node... (21/60) I20261105 17:28:49.594726 753 backend_service.cpp:1293] query for dictionary status, return 0 rows I20261105 17:28:49.608986 753 workload_group_manager.cpp:144] workload group's id changed, before: 1, after:1793352304968 I20261105 17:28:49.609093 753 topic_subscriber.cpp:47] [topic_publish]finish handle topic WORKLOAD_GROUP, size=1 I20261105 17:28:49.939105 753 olap_server.cpp:1201] cooldown producer get tablet num: 0 I20261105 17:28:50.832597 753 wal_manager.cpp:505] Scheduled(every 10s) WAL info: [/opt/apache-doris/be/storage/wal: limit 108459401625 Bytes, used 0 Bytes, estimated wal bytes 0 Bytes, available 108459401625 Bytes.]; I20261105 17:29:00.454471 753 data_dir.cpp:893] path: /opt/apache-doris/be/storage total capacity: 2074772647936, available capacity: 1084592963584, usage: 0.477247, in_use: 1 2026-11-05T17:29:07+08:00 [INFO] [Entrypoint]: Waiting for BE node... (41/60) I20261105 17:29:19.458489 753 backend_service.cpp:1163] get_batch stream_load_record rocksdb successfully. records size: 0, last_stream_load_timestamp: -1 I20261105 17:29:20.885912 753 wal_manager.cpp:505] Scheduled(every 10s) WAL info: [/opt/apache-doris/be/storage/wal: limit 108459296358 Bytes, used 0 Bytes, estimated wal bytes 0 Bytes, available 108459296358 Bytes.]; 2026-11-05T17:29:27+08:00 [ERROR] [Entrypoint]: BE node failed to start ``` ## Comparison Using the following older image in the same environment works correctly: ```text apache/doris:4.0.3-all-slim ``` The problem occurs after switching to: ```text apache/doris:be-4.1.5 ``` ### What You Expected? The BE startup check should detect that the BE node is running and allow the container to remain in the running state. ### How to Reproduce? _No response_ ### Anything Else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
