Hey Matt. You're pretty close.
And you're referring to the resulting fact that one could take an image ending with txn 100, jump into the middle of a log file that went from txn 50 to 170
In theory, yes. In the current implementation, images are only saved at boundaries of edit log segments. So if you have an image with txn 100, then you'll have some edit log file which starts at 101, so the "jump into the middle" part isn't necessary.
Although it doesn't hurt to also clear the edits logs, once you have multiple copies of the fsimage. Does your log-rolling logic automatically delete log chunk files older than available fsimage files?
It's not implemented yet, but the idea is that a separate background thread would be responsible for handling management of old files based on various policies (eg remove old ones, or perhaps archive to some other location)
So, sounds like we're in agreement. Thanks.