[
https://issues.apache.org/jira/browse/FALCON-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095709#comment-15095709
]
Peeyush Bishnoi commented on FALCON-1747:
-----------------------------------------
On debugging this issue, I have found that Falcon could not able to list the
instances status from the API because specified value of numResults is huge i.e
Integer.MAX_VALUE. This numResults value used as dateMultiplier to calculate
the startDate of process Entity and thus resultant in out of range for
startDate, due to which instance status API failed with the exception mentioned
in the original comment.
When I set the numResults value like 10,50,100,1000, Falcon instance status API
is successful.
On further analyzing this issue, I found that initially dateMultiplier value
used to be 10. But in FALCON-1244 the value of numResults is assigned to
dateMultiplier.
> Falcon instance status listing is throwing error message.
> ---------------------------------------------------------
>
> Key: FALCON-1747
> URL: https://issues.apache.org/jira/browse/FALCON-1747
> Project: Falcon
> Issue Type: Bug
> Components: prism
> Reporter: Peeyush Bishnoi
> Assignee: Peeyush Bishnoi
> Fix For: trunk
>
>
> When trying to do listing of Falcon instance, following error message appears:
> {code:java}
> ERROR: Bad Request;default/Specified End date 2016-01-12T10:20Z is before the
> entity was scheduled 221558424-03-21T20:03Z
> {code}
> Process entity validity start date and end date is valid.
> This issue has been reported by one of the user internally at Hortonworks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
