Is there another stack trace after this line? This stack trace is actually very generic in Drill, it's just the codepath taken when a client receives a message. I was looking for an error from the filesystem itself.
On Fri, Jan 22, 2016 at 3:57 PM, Kumiko Yada <[email protected]> wrote: > Jason, > > Here is the callstack: > > [Error Id: 12e9ba22-271f-4b73-897e-186bf320f9d3 on > blvkydevbfd01.ds-iq.corp:31010] > at > org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(QueryResultHandler.java:119) > [drill-java-exec-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.user.UserClient.handleReponse(UserClient.java:113) > [drill-java-exec-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicClientWithConnection.java:46) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicClientWithConnection.java:31) > [drill-rpc-1.4.0.jar:1.4.0] > at org.apache.drill.exec.rpc.RpcBus.handle(RpcBus.java:69) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.RpcBus$RequestEvent.run(RpcBus.java:400) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.common.SerializedExecutor$RunnableProcessor.run(SerializedExecutor.java:105) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.RpcBus$SameExecutor.execute(RpcBus.java:264) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.common.SerializedExecutor.execute(SerializedExecutor.java:142) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:298) > [drill-rpc-1.4.0.jar:1.4.0] > at > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:269) > [drill-rpc-1.4.0.jar:1.4.0] > at > io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:89) > [netty-codec-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:254) > [netty-handler-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > [netty-codec-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:242) > [netty-codec-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:847) > [netty-transport-4.0.27.Final.jar:4.0.27.Final] > at > io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:618) > [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na] > at > io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:329) > [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na] > at > io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:250) > [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na] > at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111) > [netty-common-4.0.27.Final.jar:4.0.27.Final] > at java.lang.Thread.run(Thread.java:745) [na:1.7.0_71] > 2016-01-22 23:16:45,852 [Client-1] INFO > o.a.drill.exec.rpc.user.UserClient - Channel closed /192.168.200.129:57436 > <--> /192.168.200.129:31010. > 2016-01-22 23:16:45,853 [qtp1683069650-5882] ERROR > o.a.d.e.server.rest.QueryResources - Query from Web UI Failed > org.apache.drill.common.exceptions.UserRemoteException: DATA_WRITE ERROR: > Failed to drop table > > -Kumiko > -----Original Message----- > From: Jason Altekruse [mailto:[email protected]] > Sent: Friday, January 22, 2016 3:52 PM > To: user <[email protected]> > Cc: Kevin Verhoeven <[email protected]>; Ki Kang < > [email protected]> > Subject: Re: DATA_WRITE ERROR: Failed to drop table > > Looking at where this message is produced, there was likely a lower level > filesystem error that was not related to permissions. Can you check the > logs for more info? > > The error message you see on the command line should have an error ID you > can use to search the logs. > > - Jason > > On Fri, Jan 22, 2016 at 3:22 PM, Kumiko Yada <[email protected]> > wrote: > > > Hello, > > > > I created the table using CREATE TABLE AS (CTAS) command, then I tried > > to DROP this directory with DROP TABLE command, I'm getting the error > > "DATA_WRITE ERROR: Failed to drop table". > > > > I verified that I have a full permission to the directory. Has anyone > > seen this? > > > > Thanks > > Kumiko > > >
