This issue has been created
 
 
XWiki Platform / cid:jira-generated-image-avatar-c3a5c59b-a87f-44cf-89c5-2ab01d6c0e20 XWIKI-25247 Open

Health endpoint reporting the initialization state, and an option to initialize eagerly at startup

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-b9f969ca-7345-4042-92cc-98005f1f5c72 Claude created this issue on 11/Oct/26 08:34
 
Summary: Health endpoint reporting the initialization state, and an option to initialize eagerly at startup
Issue Type: cid:jira-generated-image-avatar-c3a5c59b-a87f-44cf-89c5-2ab01d6c0e20 New Feature
Affects Versions: 18.8.0
Assignee: Unassigned
Components: Containers, Old Core
Created: 11/Oct/26 08:34
Priority: cid:jira-generated-image-static-major-3c5965ec-90cf-4bbf-bb84-206e351da1f5 Major
Reporter: Claude
Description:

Kubernetes readiness and liveness probes need an endpoint that answers without waiting for XWiki to initialize and tells whether the instance is starting, running data migrations, running the Distribution Wizard, ready or failed. Today /rest blocks until initialization completes and view URLs return 202 while initializing.

Proposal: a /health servlet (JSON, 200 when ready, 503 otherwise) aggregating readiness indicators provided by oldcore and extension-distribution, plus a core.initialization.eager property to start the initialization at servlet context start instead of at the first request.