Log error when changes forced to rewind to beginning #1568
During a recent rolling upgrade, we observed the changes feed rewinding to a very old version, which caused performance issues for the client since it had to slog through millions of previously seen changes. Unfortunately, there is no logging when the changes endpoint is forced to rewind, so this adds such logging .
Unfortunately, this is not trivial to test.
Related Issues or Pull Requests