Crash report
1:M 12 Jun 2023 22:18:26.030 * 1 changes in 3600 seconds. Saving...
1:M 12 Jun 2023 22:18:26.030 * Background saving started by pid 541
541:C 12 Jun 2023 22:18:26.079 * DB saved on disk
541:C 12 Jun 2023 22:18:26.079 * Fork CoW for RDB: current 4 MB, peak 4 MB, average 2 MB
1:M 12 Jun 2023 22:18:26.130 * Background saving terminated with success
1:M 12 Jun 2023 23:18:27.004 * 1 changes in 3600 seconds. Saving...
1:M 12 Jun 2023 23:18:27.004 * Background saving started by pid 542
542:C 12 Jun 2023 23:18:27.068 * DB saved on disk
542:C 12 Jun 2023 23:18:27.069 * Fork CoW for RDB: current 4 MB, peak 4 MB, average 2 MB
1:M 12 Jun 2023 23:18:27.105 * Background saving terminated with success
1:M 13 Jun 2023 00:18:28.026 * 1 changes in 3600 seconds. Saving...
1:C 13 Jun 2023 01:37:33.689 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 13 Jun 2023 01:37:33.689 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
...
Additional information
- redis:7.0-alpine in K8S
- After 1 hour period, Redis didn't start background saving expected. Besides, Redis "automatically" starting caused consumers to lose connection.