Smooth Rebuild
Perform a smooth rebuild in Optimizely Graph to update your deployment using a Blue-Green model that enables testing and promotion without downtime.
Smooth rebuild lets you refresh your Optimizely Graph deployment without downtime. It follows a blue-green deployment model, where a new deployment (green slot) is created while your current deployment (blue slot) stays active. You can test new configurations or data models in the green slot and then promote them to live when verified.
A smooth rebuild is useful when you need to:
- Refresh your deployment from a clean state to resolve legacy issues.
- Test new or updated data models in parallel with the production environment.
- Upgrade configurations that introduce new features, fixes, or performance improvements.
Smooth rebuild process
When you start a smooth rebuild in Optimizely Graph, a new deployment slot is created. The system begins syncing content from your CMS to this new slot.
After the data sync from the CMS database is completed at least once, the status changes to DELTA SYNCING. This means any content changes made since you started the rebuild are only synced to the new slot, ensuring the new deployment stays up to date before promotion.
You can monitor rebuild progress in your Optimizely Graph environment, including:
- Rebuild start time
- Number of pending and synced items
- Number of failed items
Querying slots during rebuild
You can test and verify the new slot before promoting it to a live environment.
Using GraphQL GraphiQL
- Open Optimizely Graph playground.
- Enable the New option to query the new slot.
- Run your test queries and compare results with the live slot.
Using the GraphQL API
To query the new slot through the API, include the following HTTP header:
cg-query-new: true
This directs your request to the new (green) slot while keeping the live (blue) slot unaffected.
Finalize or abandon the rebuild
After testing the new slot:
- Accept – Promotes the new slot to a live state. Optimizely Graph routes all requests to this slot.
- Abandon – Discards the new slot and keeps the existing deployment. All content changed since the smooth rebuild was started will be synced back to the new slot from cms.
WarningOnce accepted, reverting is only possible to the state before the rebuild started. Any changes made since then are lost.
When you click Accept, the system promotes the new slot and sets the rebuild status to IDLE. You can later choose to start another smooth rebuild if needed.
Learn more on how to Smooth rebuild is used in:
- CMS 12
- CMS SaaS
Updated 16 days ago
