Uploaded image for project: 'InsightEdge Platform'
  1. GS-13454

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 10.2.0-patch1, 12.3
    • Labels:
    • Platform:
      All
    • SalesForce Case ID:
      00011584
    • Acceptance Test:
      Hide
      test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitFOTest.java
      test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitTest.java
      Show
      test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitFOTest.java test/gsm/datagrid/eager/EagerDataGridDeploymentWithServiceLimitTest.java
    • Sprint:
      12.3-M12, 12.3-M19
    • Product:
      XAP
    • Edition:
      Premium

      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).


        Attachments

          Issue links

            Activity

              People

              • Assignee:
                moran Moran Avigdor
                Reporter:
                moran Moran Avigdor
                Participants of an issue:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: