-
Type: Bug
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: 3.2.13
-
Component/s: Networking
-
None
-
Fully Compatible
-
ALL
-
v3.4, v3.2
Our database is divided into 4 shards, each having one primary, secondary and arbiter. Primaries are r4.2xlarge servers on AWS EC2, and secondaries are r4.xlarge.
Our work load is intensive in both reads and writes, but these servers usually handle the load without a problem. However during their regular work, primaries of 3 of the 4 shards suddenly crashed, within a very short time of each other. We don't know what could have caused this.
Attached are the logs of the segfaults from the primary servers. The one from shard1 seems different that the other two.
- is duplicated by
-
SERVER-29510 mongos on all servers crash when adding an index
- Closed
-
SERVER-29310 server crash during chunk split
- Closed
- related to
-
SERVER-29377 Make the logging subsystem immortal
- Closed