[SERVER-8487] Fix broken condition in oplog reader code. Created: 08/Feb/13  Updated: 11/Jul/16  Resolved: 08/Feb/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.2.4, 2.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Operating System: ALL
Participants:

 Description   

Failure to set last optime written can cause oplog reader to sleep up to 1 second.



 Comments   
Comment by auto [ 09/Feb/13 ]

Author:

{u'date': u'2013-02-08T21:10:27Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-8487 Fix broken condition in oplog reader code.
Branch: v2.2
https://github.com/mongodb/mongo/commit/139a5759a98d9b18b41499b3c7e4475e5fdb2566

Comment by auto [ 08/Feb/13 ]

Author:

{u'date': u'2013-02-08T21:10:27Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}

Message: SERVER-8487 Fix broken condition in oplog reader code.
Branch: master
https://github.com/mongodb/mongo/commit/cd93f5f2327addd5506d81e4ba71d652be9ae9d2

Comment by Eric Milkie [ 08/Feb/13 ]

Note: This only affects oplog readers on secondaries, from other secondaries ("chained replication"); oplog readers on primaries do not have the erroneous sleep delays.

Generated at Thu Feb 08 03:17:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.