Comment 1 for bug 484727

Hmm. Looking at the scenario I find this:

- The recovery itself should not fail. It also does see the new transactions that were written to zeo2 - that's what ZEO is for after all.

- However, the backends definitely will get out of sync immediately if someone writes to zeoraid1 because all writes of zeoraid2 only will target zeo2 that will cause zeoraid1 to either degrade zeo1 very quickly or even become inconsistent and shut down.

- Interestingly enough, zeoraid2 will continue to function properly on the remaining zeo2.

I think what we can learn from this is: during recovery you can only run a single zeoraid server where all new transactions go to because otherwise as soon as recovery is finished the redundant zeoraid servers won't know about the recovered storage. This needs documentation.

I was also able to see the failed lastTransaction call. I did not expect this so I need to look where that actually came from.