Hi, we see this warning in our sentinel redis clusters that have save config. when this happens failover is performed and we have interuption for several minutes. in this case the master has 9 slaves and DB contains around 20M keys.
What does it mean and how can we fix it?
1:S 12 Jun 2023 05:10:32.064 * 1000 changes in 10800 seconds. Saving...
1:S 12 Jun 2023 05:10:32.212 * Background saving started by pid 218143
1:S 12 Jun 2023 05:10:32.313 # Warning, detected child with unmatched pid: 181469
1:S 12 Jun 2023 05:10:32.413 # Warning, detected child with unmatched pid: 181470
1:S 12 Jun 2023 05:10:32.513 # Warning, detected child with unmatched pid: 181467
1:S 12 Jun 2023 05:10:32.613 # Warning, detected child with unmatched pid: 181472
1:S 12 Jun 2023 05:10:32.714 # Warning, detected child with unmatched pid: 181473
1:S 12 Jun 2023 05:10:32.814 # Warning, detected child with unmatched pid: 181474
1:S 12 Jun 2023 05:10:32.915 # Warning, detected child with unmatched pid: 181481
1:S 12 Jun 2023 05:10:33.015 # Warning, detected child with unmatched pid: 181485
1:S 12 Jun 2023 05:10:33.116 # Warning, detected child with unmatched pid: 181486
1:S 12 Jun 2023 05:10:33.216 # Warning, detected child with unmatched pid: 181487
1:S 12 Jun 2023 05:10:33.320 # Warning, detected child with unmatched pid: 181488
1:S 12 Jun 2023 05:10:33.422 # Warning, detected child with unmatched pid: 181484
1:S 12 Jun 2023 05:10:33.523 # Warning, detected child with unmatched pid: 181507
1:S 12 Jun 2023 05:10:33.626 # Warning, detected child with unmatched pid: 181505
1:S 12 Jun 2023 05:10:33.726 # Warning, detected child with unmatched pid: 181509
1:S 12 Jun 2023 05:10:33.826 # Warning, detected child with unmatched pid: 181511
1:S 12 Jun 2023 05:10:33.927 # Warning, detected child with unmatched pid: 181512
1:S 12 Jun 2023 05:10:34.028 # Warning, detected child with unmatched pid: 181508
1:S 12 Jun 2023 05:10:34.128 # Warning, detected child with unmatched pid: 181524
1:S 12 Jun 2023 05:10:34.230 # Warning, detected child with unmatched pid: 181525
1:S 12 Jun 2023 05:10:34.332 # Warning, detected child with unmatched pid: 181526
1:S 12 Jun 2023 05:10:34.432 # Warning, detected child with unmatched pid: 181527
1:S 12 Jun 2023 05:10:34.532 # Warning, detected child with unmatched pid: 181523
1:S 12 Jun 2023 05:10:34.632 # Warning, detected child with unmatched pid: 181520
1:S 12 Jun 2023 05:10:34.732 # Warning, detected child with unmatched pid: 181546
1:S 12 Jun 2023 05:10:34.832 # Warning, detected child with unmatched pid: 181547
1:S 12 Jun 2023 05:10:34.934 # Warning, detected child with unmatched pid: 181544
1:S 12 Jun 2023 05:10:35.036 # Warning, detected child with unmatched pid: 181549
1:S 12 Jun 2023 05:10:35.136 # Warning, detected child with unmatched pid: 181550
1:S 12 Jun 2023 05:10:35.237 # Warning, detected child with unmatched pid: 181551
218143:C 12 Jun 2023 05:11:43.024 * DB saved on disk
218143:C 12 Jun 2023 05:11:43.245 * RDB: 172 MB of memory used by copy-on-write
1:S 12 Jun 2023 05:11:43.602 * Background saving terminated with success
Redis Version:
Redis server v=6.0.16 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=f7b6ec69a8fa9847
Spotahome Chart Version:3.2.4
Operator Version:redis-operator:v1.2.2
Hi, we see this warning in our sentinel redis clusters that have
save
config. when this happens failover is performed and we have interuption for several minutes. in this case the master has 9 slaves and DB contains around 20M keys. What does it mean and how can we fix it?Redis Config: