[
https://issues.apache.org/jira/browse/FALCON-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953568#comment-14953568
]
Ajay Yadava commented on FALCON-1529:
-------------------------------------
Tested the change in distributed mode after the change.
{code}
bin/falcon entity -type feed -slaAlert -start 2000-10-01T00:00Z
No sla miss found!
Response: ua1/Success!
ua2/Success!
Request Id: ua1/3582372@qtp-1044388609-0 - 26ae9c02-67cd-4d69-9b45-02c4c14943b5
ua2/1533478516@qtp-1214239974-0 - c91e7071-90ac-4d77-8c16-23a4c99996f7
{code}
{code}
bin/falcon entity -type feed -name in -delete
falcon/ua1/in(feed) removed successfully (KILLED in ENGINE)
ua2/in(feed) removed successfully (KILLED in ENGINE)
prism/in(feed) removed successfully
{code}
{code}
bin/falcon entity -type feed -slaAlert -start 2000-10-01T00:00Z
No sla miss found!
Response: ua1/Success!
ua2/Success!
Request Id: ua1/1246191297@qtp-1370399357-0 -
a26142c2-823d-4797-be07-152da1114979
ua2/562266264@qtp-44054531-0 - 60b291bb-065c-47bf-ba16-d8c30e098435
{code}
> SLAMonitoring API non-intuitive response
> ----------------------------------------
>
> Key: FALCON-1529
> URL: https://issues.apache.org/jira/browse/FALCON-1529
> Project: Falcon
> Issue Type: Bug
> Reporter: Pragya Mittal
> Assignee: Ajay Yadava
>
> When we query falcon for sla miss and there are no SLA miss then response
> contains stack trace whichj is not very intuitive.
> {noformat}
> dataqa@lda01:~$ falcon entity -type feed -start 2015-10-12T11:50Z -slaAlert
> No sla miss found!
> Response:
> ua1/org.apache.falcon.FalconException::javax.ws.rs.WebApplicationException:
> javax.xml.bind.UnmarshalException: unexpected element (uri:"",
> local:"instancesResult"). Expected elements are <{}instances>,<{}result>
> ua3/Success!
> ua2/Success!
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
