Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-19690

NM Memory can end up being too high on nodes with many components

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      Ambari's Stack Advisor has a static method to compute OS/component overheads when computing the YARN config 'yarn.nodemanager.resource.memory-mb' for NM

      We should add validation to check if there are any NodeManagers that would have high memory usage based on co-located service components and report a warning.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jluniya Jayush Luniya Assign to me
            jluniya Jayush Luniya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment