falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeyush Bishnoi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1747) Falcon instance status listing is throwing error message.
Date Thu, 14 Jan 2016 09:17:39 GMT

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

Peeyush Bishnoi commented on FALCON-1747:

I thought to add upper bound to numResults value but question is what should be the upper
bound value on numResults for listing the instances status. As users may pass different value
to numResults like 10,50,100 etc. depending on their use case/purpose and we will not be aware
of this all the time.

You have mentioned that the provided fix can introduce OOM, if the calculated start and end
date diff is too much. But without this patch as well, users has option to provide any start
and end date on CLI to get the list of instances status and with that also start and end date
diff can become too much.

Moreover, I have seen that even if specified numResults value is in few hundreds or less,
calculated start date still go much beyond the entity start date and diff become too much.
But we have a check and restrict it to entity start date only.

So in the provided patch if start date is empty, it is required to calculate start date in
function getStartAndEndDate()/getStartDate() of class AbstractInstanceManager. If calculated
start go beyond entity dates, then we restrict to entity start date.

> 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: 0.9
>         Attachments: FALCON-1747.patch
> 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

View raw message