[SERVER-18762] Mongo 3.0 crashes while replicating map reduce collections Created: 01/Jun/15 Updated: 15/Nov/21 Resolved: 18/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Amit Karan | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1. Setup a primary DB with enough data - my DB is 200GB+ |
||||||||
| Participants: | |||||||||
| Description |
|
Mongo DB keeps crashing while replicating in startup2 phase. Primary Mongo DB is version 2.6.9. New replica set added are 3.0.3 version with WiredTiger storage. It seems it crashes while creating index for temporary collections used for map reduce.
|
| Comments |
| Comment by Ramon Fernandez Marina [ 18/Jun/15 ] |
|
akaran, I'm convinced this ticket is a duplicate of Thanks, |
| Comment by Ramon Fernandez Marina [ 08/Jun/15 ] |
|
akaran@mobeam.com, I believe you're running into If you can't wait for 3.0.4-rc0 I can point you to a nightly build on the v3.0 branch that includes a fix for this bug; otherwise I'd recommend you download and install 3.0.4-rc0 when it becomes available, and once you've confirmed that this bug is fixed you can move to the upcoming 3.0.4 release which, of everything goes according to plan, should be available in a week or two. Regards, |
| Comment by Amit Karan [ 08/Jun/15 ] |
|
We had another crash. Here are log files from primary and secondary DBs - primary.crash.log & secondary.crash.log. Our Primary DB has also been upgraded to 3.0.3 with WiredTiger storage. |
| Comment by Amit Karan [ 01/Jun/15 ] |
|
I have attached the crash logs from two data centers secondary servers here. I am unable to attach logs from primary DB (around 8 GB) and another secondary (around 900 MB) that were being used to replicate data. I will put link to dropbox here. |
| Comment by Ramon Fernandez Marina [ 01/Jun/15 ] |
|
akaran, can you please upload full logs from startup until the moment you see the backtrace above for both your primary and the secondary that crashes? Thanks, |