tajo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-1321) Cli prints wrong response time
Date Sun, 01 Feb 2015 07:30:34 GMT

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

Jihoon Son commented on TAJO-1321:
----------------------------------

Ok. 
Allowing the Tajo master to set the start time and the finish time will be the better solution
because users think that a query starts when they submit the query, and finishes when they
get the results.

> Cli prints wrong response time
> ------------------------------
>
>                 Key: TAJO-1321
>                 URL: https://issues.apache.org/jira/browse/TAJO-1321
>             Project: Tajo
>          Issue Type: Bug
>          Components: cli
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>            Priority: Critical
>             Fix For: 0.10
>
>
> When I run Tajo on two different clusters, the cli prints wrong response time.
> Here is examples.
> - Cluster1: the response time decreases when the query is finished.
> {noformat}
> tpch100> select count(*) from customer;
> Progress: 30%, response time: 1.834 sec
> Progress: 30%, response time: 1.834 sec
> Progress: 30%, response time: 2.235 sec
> Progress: 30%, response time: 3.036 sec
> Progress: 43%, response time: 4.037 sec
> Progress: 43%, response time: 5.038 sec
> Progress: 100%, response time: 4.878 sec
> ?count
> -------------------------------
> 15000000
> (1 rows, 4.878 sec, 9 B selected)
> {noformat}
> - Cluster2: the response time jumps when the query is finished.
> {noformat}
> tpch_hdfs> select count(*) from customer;
> Progress: 0%, response time: 0.908 sec
> Progress: 0%, response time: 0.909 sec
> Progress: 0%, response time: 1.31 sec
> Progress: 0%, response time: 2.111 sec
> Progress: 48%, response time: 3.111 sec
> Progress: 100%, response time: 24.104 sec
> ?count
> -------------------------------
> 15000000
> (1 rows, 24.104 sec, 9 B selected)
> {noformat}
> I suspect that the wrong information is stored when the query history is written.



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

Mime
View raw message