Hello guys,

I have found the supposed error. It was because the /tmp directory in the 
Amazon webservice instance is limited to 8 GB.

Best regards,
Chris

> Am 29.10.2014 um 00:41 schrieb Christian Schwabe <[email protected]>:
> 
> 
> Hello guys,
> 
> Due to the weak hardware available to me I have now leased AWS (Amazon Web 
> Services) instances. The adjustment is now quitesimple and was done quickly.
> What I would like to mention is that some queries previously have been run 
> successful
> BUT... ;) 
> 
> 
> For a query with a large selection and great Joins I received the following 
> exception:
> 
> 
> 2014-10-28 22:57:46,793 ERROR org.apache.tajo.master.GlobalEngine: 
> Stack Trace:
> LINE 1:0 Caused by: java.io.IOException: No space left on device
>          ^^^^^^
>     at org.apache.tajo.engine.parser.SQLAnalyzer.parse(SQLAnalyzer.java:65)
>     at 
> org.apache.tajo.master.GlobalEngine.buildExpressionFromSql(GlobalEngine.java:196)
>     at org.apache.tajo.master.GlobalEngine.executeQuery(GlobalEngine.java:164)
>     at 
> org.apache.tajo.master.TajoMasterClientService$TajoMasterClientProtocolServiceHandler.submitQuery(TajoMasterClientService.java:265)
>     at 
> org.apache.tajo.ipc.TajoMasterClientProtocol$TajoMasterClientProtocolService$2.callBlockingMethod(TajoMasterClientProtocol.java:527)
>     at 
> org.apache.tajo.rpc.BlockingRpcServer$ServerHandler.messageReceived(BlockingRpcServer.java:103)
>     at 
> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
>     at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
>     at 
> org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:70)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
>     at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
>     at 
> org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
>     at 
> org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
>     at 
> org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
>     at 
> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
>     at 
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
>     at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
>     at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
>     at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
>     at 
> org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
>     at 
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
>     at 
> org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
>     at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
>     at 
> org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>     at 
> org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>     at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:745)
> 
> 
> I know this exception describes quite accurately what is wrong here, but this 
> exception is mistaken, because there is enough free space as you can see:
> 
> ubuntu_master@ip-xx-xx-xxx-xx:~$ df -h
> Filesystem          Size    Used    Avail   Use%     Mounted on
> /dev/xvda1         7.8G    3.1G    4.3G    42%       /
> none                  4.0K     0        4.0K     0%        /sys/fs/cgroup
> udev                  7.4G    12K      7.4G    1%        /dev
> tmpfs                 1.5G    372K    1.5G    1%        /run
> none                 5.0M     0         5.0M   0%        /run/lock
> none                 7.4G      0         7.4G   0%        /run/shm
> none                 100M     0        100M   0%        /run/user
> /dev/xvdb            37G    15G       21G  42%        /mnt
> 
> 
> ubuntu_slave@ip-xx-xx-xxx-xx:~$ df -h
> Filesystem      Size     Used    Avail         Use%     Mounted on
> /dev/xvda1      7.8G     2.6G    4.9G         35%       /
> none               4.0K       0       4.0K          0%        /sys/fs/cgroup
> udev               7.4G     12K      7.4G         1%         /dev
> tmpfs              1.5G    356K     1.5G         1%         /run
> none               5.0M     0         5.0M        0%          /run/lock
> none               7.4G      0         7.4G        0%           /run/shm
> none               100M     0        100M        0%           /run/user
> /dev/xvdb        37G      15G        21G       42%          /mnt
> 
> 
> Unfortunately I really don't know what should I do except ensure sufficient 
> free space. Hope you guys have any ideas.
> 
> The whole community do a great job for Apache Tajo! Thanks a lot!
> 
> 
> 
> Best regards,
> Chris

Reply via email to