Hey guys, if you have a question or want to have a discussion about something, please ask the question on the user list. The overhead of managing jiras when someone doesn't understand something is too high.
The first question here is: what does drill-env.sh set the jvm memory settings to? This is a jvm failure which means your jvm settings are set too high for your hardware. You probably need to set the settings lower. Separately, I could see an enhancement request for a separate client package that can have different configuration settings for the cli when in client only mode versus embedded mode. ---------- Forwarded message ---------- From: "Daniel Barclay (Drill) (JIRA)" <[email protected]> Date: Aug 23, 2015 4:01 PM Subject: [jira] [Created] (DRILL-3693) SQLLine/drill-localhost seems to demand 2.9GB just to start To: <[email protected]> Cc: Daniel Barclay (Drill) created DRILL-3693: --------------------------------------------- Summary: SQLLine/drill-localhost seems to demand 2.9GB just to start Key: DRILL-3693 URL: https://issues.apache.org/jira/browse/DRILL-3693 Project: Apache Drill Issue Type: Bug Reporter: Daniel Barclay (Drill) Starting SQLLine/drill-localhost when not enough virtual memory is available seems to indicate that Drill's _client-side_ code is trying to allocate almost 2.9 GB: {noformat} $ ./distribution/target/apache-drill-1.2.0-SNAPSHOT/apache-drill-1.2.0-SNAPSHOT/bin/drill-localhost Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000006fff80000, 2863661056, 0) failed; error='Cannot allocate memory' (errno=12) # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 2863661056 bytes for committing reserved memory. # An error report file with more information is saved as: # /home/dbarclay/work/git/incubator-drill/hs_err_pid21405.log $ {noformat} Is that intended? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
