We're updating the issue view to help you get more done. 

Elastic Processing Unit failed to fully deploy with service-limit=1 even when there were empty GSCs running

Description

Deployment of Elastic Processing Unit with partitioned 2,1 on 3 machines with serviceLimit of 1 results in a placement which contradicts the SLA (e.g. max-instances-per-machine).

ESM starts two containers on one of the three machines, but instance 2.2 can't be deployed on it, since instance 2.1 is already on that machine (max-instances-per-machine).

Workaround

None

Acceptance Test

test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitFOTest.java
test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitTest.java

Status

Assignee

Meron Avigdor

Reporter

Meron Avigdor

Labels

Priority

Medium

SalesForce Case ID

00011584

Fix versions

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Premium

Platform

All

Sprint

None