7 ms·
Looks remarkably similar to this bug, which they claim is fixed: https://jira.mongodb.org/browse/SERVER-6228 https://jira.mongodb.org/browse/SERVER-6228 Though
by leothekim 14y ago
Looks remarkably similar to this bug, which they claim is fixed: https://jira.mongodb.org/browse/SERVER-6228 https://jira.mongodb.org/browse/SERVER-6228
Though the error in that bug was due to a regular replication event ("Fatal Assertion 16360") and this one was happening during an initial sync ("Fatal Assertion 16361"). Maybe the bug was fixed in one and not the other.