SERVER-121956ClosedFixed
Adding a new node/shard to a replica may cause "ChangeStreamHistoryLost"
Adding a new node to a replica set and making it primary may cause "ChangeStreamHistoryLost" error when trying to resume from it, because the new node's oplog will neither contain past events nor "initiating set" entry. This is a known limitation of change streams, but it could be somewhat surprising to the user. We can improve the situation in a several ways: Option 1: better error diagnostics pointing at this situation, e.g., "your primary does not have the same history as your secondari