Use machine type n1-standard-2 to avoid OOM killing

Jobs that create 105 pods on COS are regularly triggering kernel OOM killer. That causes job falures. Used n1-standard-2 instance type with 7.5 Gb RAM to give tests processes more memory.
kubernetes · May 28, 2020 · 794a164 · 794a164
1 parent 822ccd5
commit 794a164
Showing 1 changed file with 10 additions and 10 deletions.
diff --git a/jobs/e2e_node/benchmark-config.yaml b/jobs/e2e_node/benchmark-config.yaml
@@ -17,7 +17,7 @@ images:
   cosstable2-resource3:
     image: cos-77-12371-251-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'resource tracking for 105 pods per node \[Benchmark\]'
@@ -31,13 +31,13 @@ images:
   cosstable2-density2:
     image: cos-77-12371-251-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     tests:
       - 'create 105 pods with 0s? interval \[Benchmark\]'
   cosstable2-density2-qps60:
     image: cos-77-12371-251-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     tests:
       - 'create 105 pods with 0s? interval \(QPS 60\) \[Benchmark\]'
   cosstable2-density3:
@@ -49,7 +49,7 @@ images:
   cosstable2-density4:
     image: cos-77-12371-251-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     tests:
       - 'create 105 pods with 100ms interval \[Benchmark\]'
 
@@ -70,7 +70,7 @@ images:
   cosstable1-resource3:
     image: cos-stable-81-12871-103-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'resource tracking for 105 pods per node \[Benchmark\]'
@@ -91,7 +91,7 @@ images:
   cosbeta-resource3:
     image: cos-beta-81-12871-44-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'resource tracking for 105 pods per node \[Benchmark\]'
@@ -106,14 +106,14 @@ images:
   cosbeta-density2:
     image: cos-beta-81-12871-44-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'create 105 pods with 0s? interval \[Benchmark\]'
   cosbeta-density2-qps60:
     image: cos-beta-81-12871-44-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'create 105 pods with 0s? interval \(QPS 60\) \[Benchmark\]'
@@ -127,7 +127,7 @@ images:
   cosbeta-density4:
     image: cos-beta-81-12871-44-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'create 105 pods with 100ms interval \[Benchmark\]'
@@ -149,7 +149,7 @@ images:
   cosdev-resource3:
     image: cos-dev-83-13020-12-0
     project: cos-cloud
-    machine: n1-standard-1
+    machine: n1-standard-2
     metadata: "user-data<test/e2e_node/jenkins/gci-init.yaml,gci-update-strategy=update_disabled"
     tests:
       - 'resource tracking for 105 pods per node \[Benchmark\]'