[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-02-01 Thread Sudheesh Katkam (JIRA) 

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

Sudheesh Katkam commented on DRILL-4249:


The output does not state there is a deadlock. It seems there is an error while 
trying to _detect deadlocks_.

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-02-01 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

Can some one please take a look at the stacktrace and confirm if this is a 
Drill issue or it is a filesystem issue ?

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-29 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

And this is from drillbit.out file, it looks to be related to mapr FS client.

{noformat}
2016-01-29 09:50:19,6724 ERROR Cidcache 
fs/client/fileclient/cc/cidcache.cc:1586 Thread: 8396 MoveToNextCldb: No CLDB 
entries, cannot run, sleeping 5 seconds!
2016-01-29 09:50:28,6736 ERROR Cidcache 
fs/client/fileclient/cc/cidcache.cc:1586 Thread: 8396 MoveToNextCldb: No CLDB 
entries, cannot run, sleeping 5 seconds!
2016-01-29 09:54:39
Full thread dump OpenJDK 64-Bit Server VM (25.65-b01 mixed mode):

"2954c936-769a-def3-e59b-70a29ace5af1:foreman" #95 daemon prio=10 os_prio=0 
tid=0x7fd3cc40 nid=0x1bd1 runnable [0x7fd3a1521000]
   java.lang.Thread.State: RUNNABLE
at com.mapr.fs.jni.MapRClient.readdirplus(Native Method)
at com.mapr.fs.MapRClientImpl.listStatus(MapRClientImpl.java:353)
at com.mapr.fs.MapRFileSystem.listMapRStatus(MapRFileSystem.java:1403)
at com.mapr.fs.MapRFileSystem.listStatus(MapRFileSystem.java:1436)
at com.mapr.fs.MapRFileSystem.listStatus(MapRFileSystem.java:78)
at org.apache.hadoop.fs.Globber.listStatus(Globber.java:69)
at org.apache.hadoop.fs.Globber.glob(Globber.java:218)
at org.apache.hadoop.fs.FileSystem.globStatus(FileSystem.java:1710)
at com.mapr.fs.MapRFileSystem.globStatus(MapRFileSystem.java:1270)
at 
org.apache.drill.exec.store.dfs.DrillFileSystem.addRecursiveStatus(DrillFileSystem.java:767)
at 
org.apache.drill.exec.store.dfs.DrillFileSystem.list(DrillFileSystem.java:754)
at 
org.apache.drill.exec.store.dfs.WorkspaceSchemaFactory$WorkspaceSchema.isHomogeneous(WorkspaceSchemaFactory.java:664)
at 
org.apache.drill.exec.store.dfs.WorkspaceSchemaFactory$WorkspaceSchema.dropTable(WorkspaceSchemaFactory.java:692)
at 
org.apache.drill.exec.planner.sql.handlers.DropTableHandler.getPlan(DropTableHandler.java:72)
at 
org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan(DrillSqlWorker.java:218)
at org.apache.drill.exec.work.foreman.Foreman.runSQL(Foreman.java:909)
at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:244)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

"qtp801808302-94" #94 prio=5 os_prio=0 tid=0x7fd3c8e58000 nid=0x15cb 
waiting on condition [0x7fd3a2824000]
   java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0007a42065d0> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at 
org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:389)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:513)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.access$700(QueuedThreadPool.java:48)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:569)
at java.lang.Thread.run(Thread.java:745)

"BitServer-4" #23 daemon prio=10 os_prio=0 tid=0x7fd3c89c9000 nid=0x3ac8 
runnable [0x7fd3a1221000]
   java.lang.Thread.State: RUNNABLE
at io.netty.channel.epoll.Native.epollWait0(Native Method)
at io.netty.channel.epoll.Native.epollWait(Native.java:148)
at 
io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:180)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:205)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
at java.lang.Thread.run(Thread.java:745)

"BitServer-3" #22 daemon prio=10 os_prio=0 tid=0x7fd412f42800 nid=0x3ac7 
runnable [0x7fd3a1322000]
   java.lang.Thread.State: RUNNABLE
at io.netty.channel.epoll.Native.epollWait0(Native Method)
at io.netty.channel.epoll.Native.epollWait(Native.java:148)
at 
io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:180)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:205)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
at java.lang.Thread.run(Thread.java:745)

"Curator-PathChildrenCache-2" #86 daemon prio=5 os_prio=0 
tid=0x7fd3cc578000 nid=0x20ca waiting on condition [0x7fd3a662a000]
   java.lang.Thread.State: WAITING (parking)
at

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-29 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

Yes the DROP TABLE hang is reproducible on my 4 node cluster, MapR Drill 1.4.0 
GA and MapR FS 5.0.0 GA and JDK8

kill -QUIT 5194 , did not output the stack trace of the hung process to 
standard output.

Doing this (Ctril+\) gave me the stack trace on sqlline prompt, for the hung 
drop table process

{noformat}
0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
2016-01-29 10:31:26
Full thread dump OpenJDK 64-Bit Server VM (25.65-b01 mixed mode):

"threadDeathWatcher-2-1" #29 daemon prio=1 os_prio=0 tid=0x7ffe40254000 
nid=0x1b51 waiting on condition [0x7ffe305db000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
io.netty.util.ThreadDeathWatcher$Watcher.run(ThreadDeathWatcher.java:137)
at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
at java.lang.Thread.run(Thread.java:745)

"Client-1" #27 daemon prio=10 os_prio=0 tid=0x7ffe90f01000 nid=0x1b3a 
runnable [0x7ffe30c8c000]
   java.lang.Thread.State: RUNNABLE
at io.netty.channel.epoll.Native.epollWait0(Native Method)
at io.netty.channel.epoll.Native.epollWait(Native.java:148)
at 
io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:180)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:205)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
at java.lang.Thread.run(Thread.java:745)

"Curator-ServiceCache-0" #26 daemon prio=5 os_prio=0 tid=0x7ffe90e2d000 
nid=0x1ae0 waiting on condition [0x7ffe30ae6000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0006c0033898> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

"Curator-Framework-0" #25 daemon prio=5 os_prio=0 tid=0x7ffe90dde800 
nid=0x1adf waiting on condition [0x7ffe30d8d000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0006c003b878> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:211)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:70)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:780)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:62)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:257)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

"main-EventThread" #24 daemon prio=5 os_prio=0 tid=0x7ffe90dc3000 
nid=0x1ade waiting on condition [0x7ffe30f33000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0006c00436a0> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:491)

"main-SendThread(centos-01.qa.lab:5181)" #23 daemon prio=5 os_prio=0 
tid=0x7ffe90dcf000 nid=0x1add runnable [0x7ffe4410c000]
   java.lang.Thread.State: RUNNABLE
at

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-22 Thread Sudheesh Katkam (JIRA) 

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

Sudheesh Katkam commented on DRILL-4249:


But the test framework has tests that work the same way: CTAS and then DROP 
TABLE. Why are those not failing? This seems like a simple case; what am I 
missing?

Also, is this problem reproducible? If so, can you post the jstack output when 
the hang happens?

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-22 Thread Jacques Nadeau (JIRA) 

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

Jacques Nadeau commented on DRILL-4249:
---

In any case of hangs, you should capture jstack as well as jmap dump. That way 
we can figure out what state the node or nodes are in.

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-21 Thread Sudheesh Katkam (JIRA) 

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

Sudheesh Katkam commented on DRILL-4249:


Shouldn't the test framework have captured this simple case? Is there any 
config change or something else that is missing in the description?

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-21 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

This was hit when executing a manual test, test framework is not involved here.

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-06 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

>From the UI Query state for that DROP TABLE statement is listed as PENDING.

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-06 Thread Rahul Challapalli (JIRA) 

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

Rahul Challapalli commented on DRILL-4249:
--

This could be failing during the planning state. It is possible that there is a 
specific timeout and until we wait for that specific time, drill might not 
throw any error or write anything in the logs. Did you wait long (~10 mins) 
enough before checking the logs?

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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

[jira] [Commented] (DRILL-4249) DROP TABLE HANGS indefinitely

2016-01-06 Thread Khurram Faraaz (JIRA) 

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

Khurram Faraaz commented on DRILL-4249:
---

DROP TABLE did not complete. I waited for over an hour and it was hung at the 
prompt, with nothing in the logs.

> DROP TABLE HANGS indefinitely
> -
>
> Key: DRILL-4249
> URL: https://issues.apache.org/jira/browse/DRILL-4249
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Flow
>Affects Versions: 1.4.0
> Environment: 4 node cluster on CentOS
>Reporter: Khurram Faraaz
>
> DROP TABLE hangs. Table was created using CTAS and the input to CTAS was a 
> directory that had 2000 JSON files.
> There is no Exception or error message on sqlline prompt nor in drillbit.log
> Drill 1.4.0, git commitID: 32b85160
> hadoop fs -ls /tmp shows that the directory exists (at the time when DROP 
> TABLE was hung)
> drwxr-xr-x   - mapr mapr   10550677 2016-01-05 12:14 /tmp/tblMD332_wp
> {noformat}
> Snippet from drillbit.log, there's no further information after the below 
> text in drillbit.log
> 2016-01-06 10:03:09,817 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 297319a1-fb9d-8247-7d12-c8d551d56d2d: drop table tblMD332_wp
> 2016-01-06 10:03:11,516 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.create() took 6 ms
> 2016-01-06 10:03:11,517 [297319a1-fb9d-8247-7d12-c8d551d56d2d:foreman] INFO  
> o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, 
> numFiles: 1
> {noformat}
> {noformat}
> Note that DROP TABLE commands hangs indefinitely.
> [root@centos-01 bin]# ./sqlline -u "jdbc:drill:schema=dfs.tmp -n mapr -p mapr"
> apache drill 1.4.0
> "got drill?"
> 0: jdbc:drill:schema=dfs.tmp> drop table tblMD332_wp;
> {noformat}



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