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 Tue, 15 Sep 2015 12:12:46 GMT

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

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

Github user asfgit closed the pull request at:

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


> 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: Deneche A. Hakim
>             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