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 load cases).
-- Jacques Nadeau CTO and Co-Founder, Dremio On Tue, Jul 26, 2016 at 7:20 AM, scott <[email protected]> wrote: > 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 <[email protected]> > wrote: > > > > > 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: { > > batch.size : 4000, > > group.size : 100, > > threshold : 200, > > directories : [ "/var/mapr/local/Hostname/drillspill" ], > > fs : "maprfs:///" > > } > > } > > } > > > > > On 25 Jul 2016, at 16:44, scott <[email protected]> wrote: > > > > > > 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: > > > /tmp/libnetty-transport-native-epoll5743269078378802025.so: > > > /tmp/libnetty-transport-native-epoll5743269078378802025.so: failed to > map > > > segment from shared object: Operation not permitted > > > > > > Does anyone know of a way to configure Drill to use a different tmp > > > location? > > > > > > Thanks, > > > Scott > > > > >
