> I am thinking if it is possible to have this flag as a mandatory one. I guess we could do this, but I'm not a fan of this approach. We should try to limit the required flags to those that can't have a reasonable default like the paths and addresses.
> Alternatively, we could think of reducing the value to 24 hours since that > seems to be a general backup schedule. This would still be a breaking change, even if it would break fewer use-cases. > Make the change now which could break existing workflows of backups OR Do not > make the change now leading to more and more users experiencing servers > crashing due to OOM (apart from performance overhead) under certain workloads Exactly. > perhaps we could have some message displayed in WebUI/logs/ksck by monitoring > diff scans. I like this approach. > We could take a step ahead and since this is marked as a runtime flag we might > as well lower it down to 15 minutes(or the longest time period seen in those > past 7 days) and log the configuration change. This is interesting, and probably a good idea to think about it, but I'm not convinced yet. I can think of some edge cases that this would break. For example, if there is an application that runs once a month, but requires historical data going back a day, this would break it. -- Attila
