drill-issues 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] (DRILL-2650) Cancelled queries json profile shows query end time occurs before fragments end time
Date Wed, 08 Jul 2015 17:05:04 GMT

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

ASF GitHub Bot commented on DRILL-2650:
---------------------------------------

GitHub user sudheeshkatkam opened a pull request:

    https://github.com/apache/drill/pull/80

    DRILL-2650: Mark query end time when closing the Foreman

    @jacques-n @cwestin please review.

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

    $ git pull https://github.com/sudheeshkatkam/drill DRILL-2650

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

    https://github.com/apache/drill/pull/80.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 #80
    
----
commit 1ad9c5ad8d70947f029132ff1abfd03d02f464c0
Author: Sudheesh Katkam <skatkam@maprtech.com>
Date:   2015-07-07T21:08:09Z

    DRILL-2650: Mark query end time when closing the Foreman

----


> Cancelled queries json profile shows query end time occurs before fragments end time

> -------------------------------------------------------------------------------------
>
>                 Key: DRILL-2650
>                 URL: https://issues.apache.org/jira/browse/DRILL-2650
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - HTTP
>    Affects Versions: 0.9.0
>            Reporter: Krystal
>            Assignee: Sudheesh Katkam
>             Fix For: 1.2.0
>
>         Attachments: DRILL-2650.1.patch.txt
>
>
> I have a query that was successfully cancelled.  The query start and end time is as follows:
> "type": 1,
>     "start": 1427839192049,
>     "end": 1427839194966,
> This translates to a query duration of about 3 seconds.  However, the duration of the
query's fragments are much longer up to more than 6 seconds.  Here is an entry for majorFragmentId=0
with a duration of 6.6 seconds:
>  "startTime": 1427839192796,
>  "endTime": 1427839199408,
> 8 out of 11 major fragments have duration greater than the query itself.  To an end user,
this is confusing and does not make sense.  We should wait for all of the major fragments
to be completely cancelled before updating the the "end" time of the query.



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

Mime
View raw message