[SERVER-6762] Assertion failure cursor.get() db/repl/../oplogreader.h 93 Created: 14/Aug/12 Updated: 11/Jul/16 Resolved: 05/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | 2.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Roderic Liu | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
SLES 11 |
||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | Linux | ||||
| Participants: | |||||
| Description |
|
We have a 5 servers replset in our production enviroment. But recently, it got a huge replication lag frequently. Mon Aug 13 22:46:36 [rsSync] Socket recv() timeout 10.20.1.18:27017 Once the connection timeout, mongodb stopped pulling oplog from the primary node for some time until the connection is re-established. Because the replset is using a Chained replication, if the first secondary node in the chain has a timeout connection with the primary node, then all the other secondary nodes connect to it became lag too. This happened so often and we didn't manage to find anything about this, can you help us checking if it's a bug or not. |
| Comments |
| Comment by auto [ 05/Sep/12 ] |
|
Author: {u'date': u'2012-09-05T07:11:55-07:00', u'email': u'kristina@10gen.com', u'name': u'Kristina'}Message: Check repl cursor before using |
| Comment by Kristina Chodorow (Inactive) [ 14/Aug/12 ] |
|
Yes, this is a bug. Triaging... |