falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-2128) Status api shows timeout instances as failed
Date Fri, 26 Aug 2016 11:03:23 GMT

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

ASF GitHub Bot commented on FALCON-2128:
----------------------------------------

GitHub user sandeepSamudrala reopened a pull request:

    https://github.com/apache/falcon/pull/276

    FALCON-2128 Status api shows timeout instances as failed

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandeepSamudrala/falcon FALCON-2128

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/276.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #276
    
----
commit 9e68a578328e284dcdf845ce32a0c48ac8dba36c
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-07-25T06:36:59Z

    FALCON-298. Feed update with replication delay creates holes

commit a94d4fe07f0da2606fc1c9009ba9a2d62643b728
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T10:57:34Z

    rebasing from master

commit 271318b9cadde6f4341d3c02e9e71838db490023
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T10:58:13Z

    FALCON-2097. Adding UT to the new method for getting next instance time with Delay.

commit 1a4dcd234e8fe849ad415e8c9681a7d00395a107
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T11:03:55Z

    rebased and resolved the conflicts from master

commit c06556623e87cbc52f6b01d44cc420bbb92c72e9
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T11:05:08Z

    reverting last line changes made

commit 1bb8d3c72a97835b88320ce482c5f472e00fb7cd
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-09T06:05:15Z

    Merge branch 'master' of https://github.com/apache/falcon

commit d6dc8bfaa6811fe3a97f1223fd962ab8fa083b47
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-14T08:16:50Z

    Merge branch 'master' of https://github.com/apache/falcon

commit f4c6850362e04723c4d648eff0174c881b6e3f76
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-26T07:03:31Z

    Merge branch 'master' of https://github.com/apache/falcon into FALCON-2128

commit 3d47a11078e2feeee20ab3b9be601474a6da0368
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-26T08:24:32Z

    FALCON-2128 Status api shows timeout instances as failed

----


> Status api shows timeout instances as failed
> --------------------------------------------
>
>                 Key: FALCON-2128
>                 URL: https://issues.apache.org/jira/browse/FALCON-2128
>             Project: Falcon
>          Issue Type: Bug
>          Components: prism
>    Affects Versions: trunk, 0.10
>            Reporter: Pragya Mittal
>            Assignee: sandeep samudrala
>
> If instances timedout falcon status api shows the status as FAILED. In my opinion we
should differentiate FAILED instances from TIMEDOUT instances for better user understanding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message