2018-12-03 10:38:38 UTC
much older version of Mongo as well, using MongoDB 2.4.The Problem 1. Write
to primary replica set member - Successful2. Write to Oplog - Fails3. Write
to secondary replica set members - Fails- Never happens due to no Oplog
entry4. Secondary becomes Primary - Data loss for this write- Since the
document does not exist on the secondary, when it becomes the primary, my
interpretation is this data will be lost.- The below error is returned due
to the Oplog write failure but the write persists on the primary.Error
returnedWriteConcernError(passes >= maxPasses in
NamespaceDetails::cappedAlloc: ns: local.oplog.rs, len: 461696, maxPasses:
15391, _maxDocsInCapped: 2147483647, nrecords: 820038, datasize:
2478185272)Related JIRA - https://jira.mongodb.org/browse/SERVER-6981
*Will setting a write concern of > 1 reverse the replica set primary write
when Oplog write fails?*
*If you think my understanding is incorrect or have any details on this,
any help would be greatly appreciated.*
You received this message because you are subscribed to the Google Groups "mongodb-user"
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/697b489b-8e2c-466f-9e43-26325cc371d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.