Snapshotting recovery issues #248
Replies: 1 comment
-
|
Hi @MattySimpLush, has the operator successfully formed a quorum? Is the cluster operational? If the answer to both questions is yes, then:
If you determine that neither Kubernetes nor the operator appears to be the cause, it is most likely an issue specific to Typesense. In that case, you should reach out directly to the Typesense team for further assistance. If the answer to any of the initial questions is no, then please post the logs of the operator so we can inspect them. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are seeing an issue where we are stuck with snapshot recovery. The total snapshot size is roughly 2GB and we are seeing the log lines for loading collections but never one for the index. Example below
Do you know why this could be? We are monitoring RAM, CPU and Disk space and we have plenty available to the node.
Any help would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions