If using `db-s3-object`, does KeyDB uses that as a seed on startup?
Eg: Running KeyDB on AWS, the EC2 instance fails and is replaced by another one running the same config. Will it read the last S3 dump on startup?
Eg: Running KeyDB on AWS, the EC2 instance fails and is replaced by another one running the same config. Will it read the last S3 dump on startup?
Hardcoding "aws" in the core seems like an odd choice though. Wouldn't it be better to make it agnostic and provide some sort of a trigger where a an external script or util to handle backups? That is, why S3 and why not any other service?
I mostly use slaves for recovery with the database dumps as a last resort. So I overlooked that.
Do you have any special config to sync to replica before accepting incoming connections in a straightforward manner?
Its currently in the unstable branch, once it gets shaken out a bit I'll release 0.9.3 with it included.