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

NameNode Last Checkpoint script alert definition does not trigger based on uncommitted transactions

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.4.0
    • Component/s: None
    • Labels:
      None

      Description

      The 'NameNode Last Checkpoint' alert description says "This service-level alert will trigger if the last time that the NameNode performed a checkpoint was too long ago. It will also trigger if the number of uncommitted transactions is beyond a certain threshold."

      But the default alert definition seems to miss the threshold parameters for alerting the number of uncommitted transactions.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                swagle Siddharth Wagle
                Reporter:
                swagle Siddharth Wagle
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: