mirror of
https://github.com/zitadel/zitadel.git
synced 2025-01-07 22:37:40 +00:00
docs: fix init-projections flag value (#7325)
This commit is contained in:
parent
6f3f67cde7
commit
6bfa66cfa3
@ -65,7 +65,7 @@ The init phase is idempotent if executed with the same binary version.
|
|||||||
|
|
||||||
### The Setup Phase
|
### The Setup Phase
|
||||||
|
|
||||||
During `zitadel setup`, ZITADEL creates projection tables and migrates existing data, if `--init-projections` is set.
|
During `zitadel setup`, ZITADEL creates projection tables and migrates existing data, if `--init-projections=true` is set.
|
||||||
Depending on the ZITADEL version and the runtime resources,
|
Depending on the ZITADEL version and the runtime resources,
|
||||||
this step can take several minutes.
|
this step can take several minutes.
|
||||||
When deploying a new ZITADEL version,
|
When deploying a new ZITADEL version,
|
||||||
@ -85,4 +85,4 @@ Beware, in the background, out-of-date projections
|
|||||||
[recompute their state by replaying all missed events](/docs/concepts/eventstore/implementation#projections).
|
[recompute their state by replaying all missed events](/docs/concepts/eventstore/implementation#projections).
|
||||||
If a new ZITADEL version is deployed, this can take quite a long time,
|
If a new ZITADEL version is deployed, this can take quite a long time,
|
||||||
depending on the amount of events to catch up.
|
depending on the amount of events to catch up.
|
||||||
You probably should consider providing `--init-projections`-flag to the [Setup Phase](#the-setup-phase) to shift the synchronization time to previous steps and delay the startup phase until events are caught up.
|
You probably should consider providing `--init-projections=true`-flag to the [Setup Phase](#the-setup-phase) to shift the synchronization time to previous steps and delay the startup phase until events are caught up.
|
@ -27,13 +27,13 @@ If you use different configurations on `setup` and `start` and have overwritten
|
|||||||
|
|
||||||
## Statement
|
## Statement
|
||||||
|
|
||||||
Filling of projections can get time consuming as your system grows and this can cause downtime of self hosted installations of ZITADEL because queries first need to ensure data consistency.
|
Filling of projections can get time-consuming as your system grows and this can cause downtime of self-hosted installations of ZITADEL because queries first need to ensure data consistency.
|
||||||
|
|
||||||
Before this release, this step was executed after the start of ZITADEL and therefore lead to inconsistent retrieval of data until the projections were up-to-date.
|
Before this release, this step was executed after the start of ZITADEL and therefore lead to inconsistent retrieval of data until the projections were up-to-date.
|
||||||
|
|
||||||
## Mitigation
|
## Mitigation
|
||||||
|
|
||||||
Enable the `--init-projections`-flag in setup phase and make sure the previous deployment of ZITADEL remains active until the new revision started properly.
|
Enable the flag (`--init-projections=true`) in setup phase and make sure the previous deployment of ZITADEL remains active until the new revision started properly.
|
||||||
|
|
||||||
## Impact
|
## Impact
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user