falcon-dev mailing list archives

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

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

Ajay Yadav commented on FALCON-721:
-----------------------------------

[~shaik.idris]

I think sla has no natural association with feed retention and hence there should be no validation
on basis of that. e.g. we might want to move to a disk quota based retention and in such case
it will not be possible to have sla to be associated with that. 

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. sla values are supposed to be watermarks against
which the user wants to get the metrics and should follow garbage in garbage out. 

> 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
(v6.3.4#6332)

Mime
View raw message