[AMBARI-15953] NameNode Last Checkpoint script alert definition does not trigger based on uncommitted transactions - ASF JIRA

XML

Word

Printable

JSON

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

- Sort By Name
- Sort By Date
- Ascending
- Descending

AMBARI-15953.patch
19/Apr/16 00:25
9 kB
Siddharth Wagle

Issue Links

links to

Review board

Activity

People

Assignee:: Siddharth Wagle

Reporter:: Siddharth Wagle

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 18/Apr/16 22:52

Updated:: 20/Apr/16 03:35

Resolved:: 19/Apr/16 22:50