Loading...

XML

Word

Printable

JSON

Operating System:
ALL
Steps To Reproduce:

Hide

Server details:
RAM: 14GB
Data Size: 47.5GB (storage size ~15GB)
cacheSizeGB: 7
4 Cores
3.0.8
CentOS Linux release 7.2.1511 (Core): Azure, Linux version 3.10.0-229.11.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP

Replica set: Primary, Secondary and Arbiter.
Engine: WiredTiger

Show
Server details: RAM: 14GB Data Size: 47.5GB (storage size ~15GB) cacheSizeGB: 7 4 Cores 3.0.8 CentOS Linux release 7.2.1511 (Core): Azure, Linux version 3.10.0-229.11.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Replica set: Primary, Secondary and Arbiter. Engine: WiredTiger

A replica-set in Azure that was deployed few months ago.
This setup was started to crash since Fri, Jan 8 (log example attached).
No upgrade/change to the system or application was done in the last week.
The crash happens only when instance is primary, after few hours of operation. You can see that during these hours memory usage increases, while all other parameters like connections remain constant (see the attached files).
The replica set was 3.0.6, and was upgraded it today to 3.0.8. We also removed it from the replica set and recreated it. Yet the problem continues to happen on this machine.
This one of few replica sets in Azure (where this is not recreated), yet it is the most active one.