-
I've noticed that the v1.8.0 version behaves differently. We just had a Kubernetes pod crash with the following error: Our configuration doesn't specify any snapshot / save schedule.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
@roehnan this is not an error, this is a warning. I wonder what's the real reason for the crash. Can you paste the whole log? |
Beta Was this translation helpful? Give feedback.
-
To your question, Dragonfly saves a snapshot on shutdown and the instance has been actively shutdown via a command or the process signal. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the clarification. I think there was an error in our environment that caused the pod to shutdown and subsequently it was unable to write the snapshot. I don't think I can get at the logs now (since the pod was removed), but I will keep an eye out. Please close the issue and I'll reach out in Discord if I have any other information. Thanks! |
Beta Was this translation helpful? Give feedback.
Finally, you can force Dragonfly to omit snapshotting altogether by passing
--dbfilename=
in the flag file