<p dir="auto"><a href="https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/6632/" rel="nofollow">https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/6632/</a></p>
<p dir="auto">Failed: [k8s.io] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both. [Slow] {Kubernetes e2e suite}</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/pd.go:179
Expected error:
    &lt;*errors.errorString | 0xc8200e00c0&gt;: {
        s: &quot;timed out waiting for the condition&quot;,
    }
    timed out waiting for the condition
not to have occurred"><pre class="notranslate"><code class="notranslate">/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/pd.go:179
Expected error:
    &lt;*errors.errorString | 0xc8200e00c0&gt;: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
</code></pre></div>
<p dir="auto">12500 might be too large for, say, an n1-standard-4 master which has 3G of ram (i.e I don't think the estimate of: an object+metadata needed by etcd + duplication in apiserver cache = 256k is always going to be accurate). I think we came across a case where just 10,000 failed pods were enough to oom master components. Obviously 10,000 non-terminated pods can still oom it, but that's a DOS issue (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="139147331" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/22679" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/22679/hovercard" href="https://github.com/kubernetes/kubernetes/issues/22679">#22679</a>).</p>