-
Type:
Question
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.4.1
-
Component/s: None
-
None
-
Environment:Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.14.31
Architecture: x86-64
-----------------------------------
WiredTiger
db version v3.4.1
git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
allocator: tcmalloc
modules: none
build environment:
distmod: rhel70
distarch: x86_64
target_arch: x86_64Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.14.31 Architecture: x86-64 ----------------------------------- WiredTiger db version v3.4.1 git version: 5e103c4f5583e2566a45d740225dc250baacfbd7 OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013 allocator: tcmalloc modules: none build environment: distmod: rhel70 distarch: x86_64 target_arch: x86_64
Hi!
Could you help me please to analyze diagnostic.data from shard?
Today my mongod process was killed by OOM. So far, I don't know what I should change that avoid this behavior. Maybe after you see diagnostic data and config for shards you will can advise me what I should change. Also, we don't use swap and we increase cacheSizeGB, available RAM is 47G. Thanks.