You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/10/12 15:01:05 UTC

[jira] [Commented] (FALCON-1529) SLAMonitoring API non-intuitive response

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

Ajay Yadava commented on FALCON-1529:
-------------------------------------

[~pragya.mittal] Can you please elaborate more on the scenario where you are facing this? It seems that the request succeeded on two but failed on the third(ua1). Was the feed not eligible for the ua1 colo?

> 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
>
> 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)