[SERVER-23525] Mongo Replica Set unusable after Primary crashes with out of Memory, followed by Op Log out of Order on replica members Created: 05/Apr/16 Updated: 05/Apr/16 Resolved: 05/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | pavan | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Primary Out of Memory - crashes on large aggregation, about 360 K records. Replica set automatically elects new primary, Manual restart of crashed primary ( has higher priority), re-elects the primary, replica 1 and 2 crash with
|
| Comments |
| Comment by pavan [ 05/Apr/16 ] |
|
Thomas, thank your for the quick response, you are correct, apparently QA environment replica sets were still running on 3.2.1, this was where the errors happened The master has the update, 3.2.3. I was looking at the master when I reported the issues again, will upgrade the replica sets to the latest version and retest our scenarios. Regards |
| Comment by Kelsey Schubert [ 05/Apr/16 ] |
|
Hi ppeddada, The backtrace that you have provided indicates that this assertion occurred on MongoDB 3.2.1.
Can you please confirm the version you are currently using by providing the startup logs of the affected node? Since encountering this error have you upgraded your node and seen this error message again? Or have you seen this error on other nodes running on MongoDB 3.2.3? If so, can you please provide the logs of these nodes?
Kind regards, |
| Comment by pavan [ 05/Apr/16 ] |
|
Thomas, we are already on Mongo 3.2.3. Are you recommending that we upgrade to 3.2.4 ?. |
| Comment by Kelsey Schubert [ 05/Apr/16 ] |
|
Hi ppeddada, Thanks for reporting this issue. From the behavior you describe, I believe this a duplicate of Kind regards, |