falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-721) Add SLA for Feeds
Date Tue, 28 Oct 2014 19:43:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187350#comment-14187350

Shaik Idris Ali commented on FALCON-721:

{quote}I agree with you that having a slaHigh more than retention limit doesn't make much
sense but this doesn't break anything in the system {quote}

Agree that it does not break anything, but I prefer Falcon warning user during the configuration
phase itself.

If a feed has retention of 6 hours and the SLA is 8 hours. 
I assume Falcon or any other service monitoring service will make a call at 8th hour to check
for the feed availability in which case it will always Alert as retention would have deleted

> Add SLA  for Feeds
> ------------------
>                 Key: FALCON-721
>                 URL: https://issues.apache.org/jira/browse/FALCON-721
>             Project: Falcon
>          Issue Type: Sub-task
>            Reporter: Ajay Yadav
>            Assignee: Ajay Yadav
>         Attachments: FALCON-721-v2.patch, FALCON-721.patch
> Add two new xml Tags slaLow and slaHigh for the feeds.
> slaLow is intended to be used as watermark for triggering alert and slaHigh is intended
to be used as watermark for finding breach of SLA.

This message was sent by Atlassian JIRA

View raw message