Re: tmp noexec

Good idea. I should have thought of that :) -- Jacques Nadeau CTO and Co-Founder, Dremio On Fri, Jul 29, 2016 at 10:12 AM, scott wrote: > Thanks Jacques. I think I have solved my immediate problem. I added > -Djava.io.tmpdir=/newtmp to the DRILL_JAVA_OPTS variable in

Re: tmp noexec

Thanks Jacques. I think I have solved my immediate problem. I added -Djava.io.tmpdir=/newtmp to the DRILL_JAVA_OPTS variable in drill-env.sh. I am now able to start drillbit without error. Scott On Fri, Jul 29, 2016 at 4:29 PM, Jacques Nadeau wrote: > Unfortunately, the

Re: tmp noexec

Unfortunately, the issue is underlying libraries tendancy to extract native libraries into tmp. For most individual libraries, there are system properties you can set to change but there is no global option. I'm guessing that you might have one more after this one: Snappy. For Snappy, the info for

Re: tmp noexec

epoll was supposed to be disabled as part of this PR [1] pending perf. tests; IIRC test clusters were busy then, and I lost track of this change. I’ll post an update soon. Thank you, Sudheesh [1] https://github.com/apache/drill/pull/486 > On Jul 26,

Re: tmp noexec

I don't think this will fix your issue since this is a internal extraction. Try using: -Ddrill.exec.enable-epoll=false in your drill-env. That should (hopefully) disable the extraction of epoll drivers (which should actually be disabled by default I believe due to disconnection problems in heavy

Re: tmp noexec

Thanks Leon for the suggestion, but do you think this config change will help with my startup problem? It looks like it changes operations for sort after startup. Scott On Mon, Jul 25, 2016 at 3:55 PM, Leon Clayton wrote: > > I move the /tmp off local disk into the

Re: tmp noexec

I move the /tmp off local disk into the distributed FS on a node local volume on MapR. Other file systems can be inserted. Open up drill-override.conf on all of the nodes, and insert this : sort: { purge.threshold : 100, external: { batch.size : 4000, spill: {

tmp noexec

Hello, I've run into an issue where Drill will not start if mount permissions are set on /tmp to noexec. The permissions were set to noexec due to security concerns. I'm using Drill version 1.7. The error I get when starting Drill is: Exception in thread "main" java.lang.UnsatisfiedLinkError: