You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pragya Mittal (JIRA)" <ji...@apache.org> on 2015/10/12 15:38:05 UTC
[jira] [Comment Edited] (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=14953121#comment-14953121 ]
Pragya Mittal edited comment on FALCON-1529 at 10/12/15 1:37 PM:
-----------------------------------------------------------------
It is a distributed setup with 3 colos - ua1, ua2, ua3. Although feed was intended for ua1 colo only so it failed on ua1 only.
was (Author: pragya.mittal):
The feed was intended for ua1 only so it failed on ua1 only.
> 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)