Aias00 opened a new issue, #1954: URL: https://github.com/apache/rocketmq-dashboard/issues/1954
### Track RocketMQ Studio Track 1: deployable unified control plane. ### Problem Studio exposes the aggregate Spring Boot Actuator health endpoint and Docker Compose uses it to decide whether the backend is healthy. The aggregate endpoint does not distinguish two different orchestration decisions: - liveness: whether the Studio process should be restarted - readiness: whether Studio can currently serve control-plane requests Without dedicated probes, an external dependency failure can be treated like a process failure, while a started JVM may be marked ready before the database-backed control plane is usable. ### Expected behavior - expose dedicated liveness and readiness probes on the application port - liveness depends only on the application liveness state and excludes the database and RocketMQ endpoints - readiness includes the application readiness state and the database because Studio cannot provide its core persisted control plane without it - Docker Compose waits for readiness before starting the web container - the edge proxy exposes only the dedicated health paths and keeps all other Actuator endpoints blocked ### Proposed scope - configure Spring Boot Actuator health probe groups and additional paths - update the backend Compose healthcheck to use `/readyz` - expose `/livez` and `/readyz` through Nginx while retaining the Actuator deny rule - add an integration test for endpoint availability and health group membership - document the operational probe contract ### Out of scope RocketMQ Broker, NameServer, Proxy, Prometheus, cloud provider, or LLM availability. Those dependencies must not restart the Studio process and are diagnosed by their own control-plane views. ### Verification - `/livez` and `/readyz` return UP in the development test context - the liveness group excludes `db` - the readiness group includes `db` - Compose and Nginx configuration validation passes -- 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]
