Bug: Tile38 followers can get out of sync with leaders about tile38 HOT 1 OPEN

If your data is ephemeral tie the health of your followers to the health of your leader. Therefor if your leader restarts, so do your followers. That’s an option if your architecture supports a downtime of a couple of seconds. As your leader loses it’s aoffile, so should your followers.

that is not to say that I would consider this expected behavior.

We host our tile38 instances on an extra node pool, to avoid unnecessary restarts like that. Also while our leader has its private volume, followers use the node volume, and therefor have ephemeral storage.

edit:
I tried to take a look and tracked it down to this:

There is no complete checksum between leader and follower, yet I am wondering why in your case the follower aof is not recreated as there is unlikely to even be a partial match between the old leader aof/current follower aof and the new leader aof.

Can you please try to replicate this behaviour with Tile38 1.32.2? @danwit-at-lytx

from tile38.