Query the oplog to find the ts we should tail from (instead of using "now") #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we do not have a known last timestamp in the oplog tailer we use the func .BsonTimestampNow() to find a place in the oplog. "now" isn't a very useful place to start tailing from, at least in this use case.
This PR moves to doing a .Find() query to find the "tail" timestamp of the oplog. When we do not have a known place to start tailing this will cause the code to start at the oldest/tail point in the oplog. This will guarantee we have all the data better than using "now".
If the .Find() query fails we fallback to bson.MongoTimestamp(0) which should equal the epoch (January 1970?), which will still work in the .Find() as a good fallback - the "ts" index will still do a $gt/$gte on this fine.
@percona-csalguero: feel free to propose any style changes, thoughts, etc.