-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: 1.8.2
-
Component/s: Replication, Stability
-
None
-
Environment:Ubuntu EC2 Linux on m2.4xlarge
-
ALL
The Primary of one of our replica sets suddenly died with the attached stack trace (mongocrash.log) and now refuses to start, throwing stack traces like the one in mongocrash2.log.
- duplicates
-
SERVER-3447 journal exception during large operations within db.eval (multi update)
- Closed