drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tushar Pathare (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-4947) Multiple inner join drill query fails to return result for jdbc connector
Date Sat, 15 Oct 2016 13:02:20 GMT

     [ https://issues.apache.org/jira/browse/DRILL-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tushar Pathare updated DRILL-4947:
----------------------------------
    Summary: Multiple inner join drill query fails to return result for jdbc connector  (was:
Multiple inner join drill query fails to return result)

> Multiple inner join drill query fails to return result for jdbc connector
> -------------------------------------------------------------------------
>
>                 Key: DRILL-4947
>                 URL: https://issues.apache.org/jira/browse/DRILL-4947
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - RPC, Functions - Drill, Query Planning & Optimization
>    Affects Versions: 1.8.0, 1.9.0
>         Environment: RHEL 6.4 
> 32 Cores 256GB RAM
>            Reporter: Tushar Pathare
>            Priority: Blocker
>         Attachments: Screen Shot 2016-10-15 at 4.00.33 PM.png, drilllog_jira
>
>
> Huge query fails to return results.
> The query is related to a couple of data bases in the ORACLE DB.
> We are using ojdbc7.jar as 3rd party jars
> The query looks has about 11 inner joins or joins
> The Query and Planning page just mentions 
> Major fragment showing all the columns 'SENDING'
> Minor Fragment ID	Host Name	Start	End	Runtime	Max Records	Max Batches	Last Update	Last
Progress	Peak Memory	State
> 0-0	SENDING	SENDING	SENDING	SENDING	SENDING	SENDING	SENDING	SENDING	SENDING	SENDING
> the last log is as below 
> 016-10-15 15:11:24,924 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.d.exec.rpc.control.WorkEventBus
- Adding fragment status listener for queryId 27fde379-3cf4-c429-8d42-470f55c5fead.
> 2016-10-15 15:11:24,924 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.drill.exec.work.foreman.Foreman
- Submitting fragments to run.
> 2016-10-15 15:11:24,927 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.drill.exec.ops.FragmentContext
- Getting initial memory allocation of 113000000
> 2016-10-15 15:11:24,928 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.drill.exec.ops.FragmentContext
- Fragment max allocation: 930093368854
> 2016-10-15 15:11:24,932 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.d.e.work.batch.IncomingBuffers
- Came up with a list of 0 required fragments.  Fragments {}
> 2016-10-15 15:11:24,941 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.drill.exec.work.foreman.Foreman
- 27fde379-3cf4-c429-8d42-470f55c5fead: State change requested STARTING --> RUNNING
> 2016-10-15 15:11:24,942 [27fde379-3cf4-c429-8d42-470f55c5fead:foreman] DEBUG o.a.drill.exec.work.foreman.Foreman
- Fragments running.
> 2016-10-15 15:11:25,265 [27fde379-3cf4-c429-8d42-470f55c5fead:frag:0:0] DEBUG o.a.d.e.p.i.s.RemovingRecordBatch
- Created.
> 2016-10-15 15:11:25,390 [27fde379-3cf4-c429-8d42-470f55c5fead:frag:0:0] DEBUG o.a.d.e.p.i.s.RemovingRecordBatch
- Created.
> <doesnt proceed from here>



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

Mime
View raw message