Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0, 3.1.1
    • Component/s: None
    • Labels:
      None

      Description

      We were seeing issues in the Service AM where memory usage would go beyond 1gb and AM container would get killed due to pmem check. We were not setting Xmx explicitly and hence it was getting defaulted to 32gb (based on the java version we were using and the available memory in the host). Hence even minor GC cycles were not kicking in and taking the usage beyond 1gb.

      We need to default Xmx to a reasonable value, ofcourse allowing it to be overridden by the service owner.

        Attachments

          Activity

            People

            • Assignee:
              jianhe Jian He
              Reporter:
              jianhe Jian He
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: