[
https://issues.apache.org/jira/browse/FALCON-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated FALCON-1476:
--------------------------------
Attachment: FALCON-1476-v1.patch
Duplicate instances are never generated, but I have still added the check to
check for duplicates before adding.
I discovered two other issues:
a) A corner case in adding instances.
b) since blocking queue retains the same size limit after deserialization, the
change in the queue size wouldn't have reflected through the restarts.
Fixed them as well.
> Maintaining threshold on monitoring entities for SLA service
> ------------------------------------------------------------
>
> Key: FALCON-1476
> URL: https://issues.apache.org/jira/browse/FALCON-1476
> Project: Falcon
> Issue Type: Sub-task
> Environment: QA
> Reporter: Pragya Mittal
> Assignee: Ajay Yadava
> Fix For: 0.8
>
> Attachments: FALCON-1476-v1.patch, FALCON-1476.patch
>
>
> Currently SLA Monitoring service keeps on logging indefinitely for a given
> entity until it gets data for that entity. In case user gives wrong data
> path, monitoring service will look for the entity infinitely as data path
> will never be there for it. It is better to introduce a threshold which user
> can use to define how long he wants the service to run (with a default value
> set to a long interval).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
