Open IanWhalen opened 7 years ago
Thanks, I'm looking into this.
Hey @IanWhalen, this failure seems to come from a change https://github.com/mongodb/mongo/commit/77dc6917428ffad4b9ff2d54d78fa9b225f78a4b, which redesigned how mongo handles visibility of oplog and capped collection updates. This is also most likely the cause of https://github.com/mongodb-partners/mongo-rocks/issues/102.
Since it's a bigger change I might need some more time to understand it and port to MongoRocks. If you have any materials that explain the redesign please let me know.
Hey Igor, I've attached a design doc to https://jira.mongodb.org/browse/SERVER-28620. Hopefully that helps? If you've got any further questions based I'd recommend taking it to the mongodb-dev channel and someone from the Storage team can answer you there.
@IanWhalen very helpful, thanks! I'll sort it out this week hopefully.
just a heads up for y'all that we're seeing a pretty consistent failure in the rocksdb buildvariant:
https://jira.mongodb.org/browse/SERVER-31230