UIMA
  1. UIMA
  2. UIMA-1666

CasPoolSize should equal numberOfInstances when deploying a primitive component

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3AS
    • Component/s: Async Scaleout
    • Labels:
      None

      Description

      When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong.

        Activity

        Hide
        Joern Kottmann added a comment -

        Warnings are easily overseen, wouldn't it be better to not start at all if this setting is wrong ?

        Show
        Joern Kottmann added a comment - Warnings are easily overseen, wouldn't it be better to not start at all if this setting is wrong ?
        Hide
        Marshall Schor added a comment -

        I agree that warnings can be overlooked. In this case, since we "recover" this error with no adverse consequences, I don't see the value in not starting.

        We can add a comment that if the user is trying to control the size of the pool because otherwise too much memory is used, they must do it by changing the number of instances.

        The <caspool> element is needed to specify the initial CAS heap size, so the user might have this element for a legitimate reason.

        -Marshall

        Show
        Marshall Schor added a comment - I agree that warnings can be overlooked. In this case, since we "recover" this error with no adverse consequences, I don't see the value in not starting. We can add a comment that if the user is trying to control the size of the pool because otherwise too much memory is used, they must do it by changing the number of instances. The <caspool> element is needed to specify the initial CAS heap size, so the user might have this element for a legitimate reason. -Marshall
        Hide
        Marshall Schor added a comment -

        Bhavani, can you verify this fix?

        Show
        Marshall Schor added a comment - Bhavani, can you verify this fix?

          People

          • Assignee:
            Marshall Schor
            Reporter:
            Bhavani Iyer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development