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

AMS does not start up after cluster redeploy because of invalid ownership of its directories.

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: None
    • Labels:
      None

      Description

      PROBLEM
      Steps:
      Deployed cluster via blueprints.
      Reset cluster (reset ambari-server, host cleanup).
      Deployed cluster via UI.
      Result: Ambari Metrics Service go down.

      BUG
      AMS scripts do not change the ownership of certain directories to AMS user if they exist already.

      FIX
      Adding an explicit chown to take ownership of the required directories (collector conf, collector checkpoint, HBase tmp, HBase conf, HBase root)

        Attachments

        1. AMBARI-14350.patch
          5 kB
          Aravindan Vijayan

          Activity

            People

            • Assignee:
              avijayan Aravindan Vijayan
              Reporter:
              avijayan Aravindan Vijayan

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment