It's definitely not the latter (requested memory for the node is 15GB total). It would almost certainly place B, then if A doesn't release memory it would be evicted because it is using the most over its request on the node and there is no other priority rules in place (guaranteed -> burstable -> best-effort)
On Wed, Apr 4, 2018 at 8:14 PM, Srinivas Naga Kotaru (skotaru) < [email protected]> wrote: > Want to validate a statement. > > > > Just assume, we have a only one node with 60 GB memory. Pod A scheduled > with request of 10 GB and no limit. After some time, it start using 55 GB ( > ignore systems reserves for now). system now has only left with 5 GB free. > If new podB scheduled with request of 10GB, what is systems behavior? > > > > - Will it place Pod A and evict PodB softly since it can’t accommodate > both pods on same node? > - Scheduling fail to pod B since it can’t accommodate since node > doesn’t enough requested memory? > > > > > > -- > > *Srinivas Kotaru* > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
