Details
-
Question
-
Resolution: Incomplete
-
Major - P3
-
None
-
3.0.14, 3.2.13
-
None
Description
Updating MongoDB setup from version 3.0.14 to 3.2.13.
Running two node replicaset on EC2 m3.large instances using Amazon Linux.
CPU usage on primary jumps and stays to ~100% when new node (version 3.2.13) is added to replicaset and initial sync is started.
Using WiredTiger as storage engine for both versions.
Same pattern is observed in existing secondary (v3.0.14) when it's used as initial sync source. (Btw. it's not easy to setup properly).
Didn't experience this while upgrading from 2.6.x to 3.0.x.
Is it expected behaviour?
Would it be still an issue when updating from 3.2.x to 3.4.x?