drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-1513) sqlline Console Freezes On Executing Queries Using More Than One Drillbit
Date Mon, 17 Nov 2014 01:41:36 GMT

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

Jacques Nadeau commented on DRILL-1513:
---------------------------------------

Believe resolved recent fixes and removal of UDP requirement.

> sqlline Console Freezes On Executing Queries Using More Than One Drillbit
> -------------------------------------------------------------------------
>
>                 Key: DRILL-1513
>                 URL: https://issues.apache.org/jira/browse/DRILL-1513
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - CLI
>    Affects Versions: 0.5.0
>            Reporter: MUFEED USMAN
>            Assignee: Ramana Inukonda Nagaraj
>
> While querying a data (sample below):
> [root@n69 ~]# head webdata.tbl
> 1.1.11.1.1234567890123456|user123|www.abcd.com/en/US/abcde/|www.abcd.com/en/US/abcde/|2014-01-09|pg|meta.handheldfriendly|true|4
> on a 3-node running Drill 0.5.0
> select columns[0], count(*) as CNT from dfs.`/user/webdata.tbl` group by columns[0] order
by CNT desc limit 10;
> And the query console shows no signs of breakage (that from an end-user
> perspective is bad).
> Only a kill <sqlline PID> gets me out of the unresponsive sqlline console.
> Whereas a simple count(*) on the same data works just fine.
> 0: jdbc:drill:zk=n69:5181,n72:5181,n73:5181> select count(*) from
> dfs.`/user/webdata.tbl`;
> +------------+
> |   EXPR$0   |
> +------------+
> | 23719188   |
> +------------+
> 1 row selected (20.278 seconds)
> Following can be seen in the drillbit logs:
> 2014-10-09 16:20:57,560 [4fd32d44-ffd0-4351-829f-bfa5c6accdcd:frag:0:0] ERROR o.a.drill.exec.ops.FragmentContext
- Fragment Context received failure.
> 2014-10-09 16:20:57,561 [4fd32d44-ffd0-4351-829f-bfa5c6accdcd:frag:0:0] ERROR o.a.d.e.w.f.AbstractStatusReporter
- Error ad4b0e49-e6f6-4561-8930-5169b98fc14e: Failure while running fragment.
> 2014-10-09 16:20:57,563 [WorkManager-58] ERROR o.apache.drill.exec.work.WorkManager -
Failure while running wrapper [FragmentExecutor: 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:0:0]
> 2014-10-09 16:19:02,249 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:1
> 2014-10-09 16:19:02,250 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:3
> 2014-10-09 16:19:02,251 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:1
> 2014-10-09 16:19:02,253 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:3
> 2014-10-09 16:19:02,254 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:3
> 2014-10-09 16:19:02,256 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:1
> 2014-10-09 16:19:02,257 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:3
> 2014-10-09 16:19:02,258 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:1
> 2014-10-09 16:19:02,260 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:1
> 2014-10-09 16:19:02,261 [BitServer-6] ERROR o.a.drill.exec.rpc.data.DataServer - Failure
while getting fragment manager. 4fd32d44-ffd0-4351-829f-bfa5c6accdcd:1:3



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

Mime
View raw message