bitflicker64 commented on PR #3187: URL: https://github.com/apache/hugegraph/pull/3187#issuecomment-5550447211
Tested on Kubernetes on 2026-09-05, with this branch merged into the hugegraph/hugegraph testing tree. **Build under test.** Tag [`helm-dev-20260905`](https://github.com/hugegraph/hugegraph/releases/tag/helm-dev-20260905), commit `6ec19838`: apache master `36811483` plus this PR at `0ba30a1e`, #3185 and #3189. The Server image was built from that tree with `docker buildx bake -f docker/bake.hcl server-hstore` (linux/amd64) and carries `org.opencontainers.image.revision=6ec1983889f58a52995b27a4e1ea89bd00932396`, read back from the running pods. The #3132 chart set `HG_SERVER_STARTUP_TIMEOUT_S=450` through `server.extraEnv`, matching its 450 s startup probe. - Invalid value: a one-off Pod from the same image with `HG_SERVER_STARTUP_TIMEOUT_S=abc` exited 1 with `ERROR: HG_SERVER_STARTUP_TIMEOUT_S must be a whole number of seconds from 1 to 86400, got 'abc'`, before init-store ran. - Valid value: after deleting a Server Pod, `ps` in the replacement 2 s into its start showed `./bin/start-hugegraph.sh -j ... -t 450`, and `/proc/1/environ` carried `HG_SERVER_STARTUP_TIMEOUT_S=450`. Three Servers, two Server rollouts and one image roll all started clean. - Not observed: a start slower than 120 s, so the last link, the start script honouring `-t`, rests on this PR's own tests rather than on this run. The old self-termination did not appear anywhere. One note for whoever merges second: #3189 makes the Compose files require `HG_PD_AUTH_SECRET_KEY`, so `render_with_timeout` in `docker/test-compose.sh` needs `HG_PD_AUTH_SECRET_KEY="${PD_SECRET}"` in its `env` list, or `test-compose.sh render` fails on the two HStore topologies. That is how the tag resolves it. -- 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]
