Memory limit on K8S pod is not honored for WiredTigerCacheSize calculation

Ops and Admin
,
6

@Anton_Lisovenko I am not using the enterprise operator rather just the mongodb container.

Also as a small “nit” - the wired tiger memory shown in the logs is 32 MB, not GB.

Yes, you are right about the failed memory allocation, it failed while allocating a chunk of 32M. But my concern is about the ‘cache size’ wired tiger has decided to build (see the part in bold)

{“t”:{“$date”:“2020-11-02T12:50:01.089+00:00”},“s”:“I”, “c”:“STORAGE”, “id”:22315, “ctx”:“initandlisten”,“msg”:“Opening WiredTiger”,“attr”:{“config”:“create,

cache_size=3071M

,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],”}}

1 Like