Add a Snapshot Repository page to the Operate section #518
Conversation
Deploying documentation with
|
| Latest commit: |
11bbbd8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4e3a2183.documentation-beg.pages.dev |
| Branch Preview URL: | https://feat-snapshot-repository.documentation-beg.pages.dev |
pcholakov
force-pushed
the
feat/snapshot-repository
branch
2 times, most recently
from
595462f to
24f4225
Compare
There was a problem hiding this comment.
Well written snapshot documentation @pcholakov 👏. It reads really nicely! LGTM. +1 for merging.
Before merging, could you fix the link to the snapshotting documentation on the cluster deployment page?
docs/operate/snapshot-repository.mdx
Outdated
| When a node starts up with pre-existing partition state and finds that the partition's log has been trimmed to a point beyond the most recent locally-applied LSN, the node will attempt to download the latest snapshot from the configured repository. If a suitable snapshot is available, the processor will re-bootstrap its local state and resume applying the log. | ||
|
|
||
| <Admonition type="note" title="Handling log trim gap startup errors"> | ||
| If you observe repeated `Shutting partition processor down because it encountered a trim gap in the log.` errors in the Restate server log, that is an indication that a processor is failing to start up due to missing log records. In order to record, you must ensure that a snapshot repository is correctly configured and accessible from the the node experiencing errors. If no snapshots were taken previously, you will need to configure another node which has the necessary state, to first publish a snapshot for the affected partition(s). |
There was a problem hiding this comment.
"In order to resolve this failure, you must ..."?
There was a problem hiding this comment.
I think I meant to write "recover" there 😅 Yours reads better, thank you!
pcholakov
force-pushed
the
feat/snapshot-repository
branch
2 times, most recently
from
6cc3901 to
a4c3b84
Compare
pcholakov
force-pushed
the
feat/cluster-into
branch
from
7d2e325 to
5b9af60
Compare
pcholakov
force-pushed
the
feat/snapshot-repository
branch
from
a4c3b84 to
7a761be
Compare
pcholakov
force-pushed
the
feat/snapshot-repository
branch
from
7a761be to
11bbbd8
Compare
Thanks @tillrohrmann - I split the initial page in two, a short one on configuring the repository that I put under |
Builds on #515
Closes #509