The ES pod went to Error state and after few hours the elasticsearch containers not running in the ES pods

modules/cluster-logging-elasticsearch-limits.adoc

@@ -9,6 +9,9 @@ Each component specification allows for adjustments to both the CPU and memory l
 You should not have to manually adjust these values as the Elasticsearch
 Operator sets values sufficient for your environment.
 
+Each Elasticsearch node can operate with a lower memory setting though this is *not* recommended for production deployments. 
+For production use, you should have no less than the default 16Gi allocated to each Pod. Preferably you should allocate as much as possible, up to 64Gi per Pod.
+
 .Prerequisites
 
 * Cluster logging and Elasticsearch must be installed.
@@ -34,11 +37,10 @@ spec:
       elasticsearch:
         resources: <1>
           limits:
-            cpu: "4000m"
-            memory: "4Gi"
+            memory: "16Gi"
           requests:
-            cpu: "4000m"
-            memory: "1Gi"
+            cpu: "1"
+            memory: "16Gi"
 ----
 <1> Specify the CPU and memory limits as needed. If you leave these values blank,
 the Elasticsearch Operator sets default values that should be sufficient for most deployments.