@David, the warning "Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0" might be indicative of something here. Java 8 moved away from PermGen to MetaSpace. So I'm guessing there could be mismatch of Java versions (Drill build + env of Drill server + env of Drill client).
I'm not an expert on this, but a simple suggestion - could you match Java versions on the client and server (say all to JDK 8), rebuild Drill if necessary and give it another try? Some references: [1] http://stackoverflow.com/questions/27131165/what-is-the-difference-between-permgen-and-metaspace [2] https://dzone.com/articles/java-8-permgen-metaspace [2] http://stackoverflow.com/questions/31455644/should-i-set-a-maxmetaspacesize/31463972#31463972 On Mon, Apr 17, 2017 at 1:34 PM Lee, David <[email protected]> wrote: > Still doesn't work.. Added the following to sqlline.bat > > set DRILL_JAVA_OPTS=%DRILL_JAVA_OPTS% -XX:MaxPermSize=512M > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > MaxPermSize=512M; support was removed in 8.0 > > This is also a problem trying to connect a Windows JDBC program to a 1.10 > Drillbit running on Linux. > > The only success I've had is to use the old drill-jdbc-all-1.9.0.jar with > a 1.10 Drillbit. > > -----Original Message----- > From: Abhishek Girish [mailto:[email protected]] > Sent: Monday, April 17, 2017 11:07 AM > To: [email protected] > Subject: Re: Windows system Initiation Error > > Could you try bumping up the PermGen space [1]? On Windows, since the > https://urldefense.proofpoint.com/v2/url?u=http-3A__drill-2Denv.sh&d=DwIFaQ&c=zUO0BtkCe66yJvAZ4cAvZg&r=SpeiLeBTifecUrj1SErsTRw4nAqzMxT043sp_gndNeI&m=bsY3U2vW9rEUUwlUU8cIDxfZjFYfTixWbzh-gHIZrlM&s=WifyWd6PMT4kPGsa9nHKXbCWQJ_2SX67khzvnQKA9N4&e= > file doesn't take effect, you might need to set an env variable, or update > the Sqlline.bat file. > > [1] Update "-XX:MaxPermSize=512M" in DRILL_JAVA_OPTS > > On Mon, Apr 17, 2017 at 10:44 AM Lee, David <[email protected]> > wrote: > > > Drill embedded runs fine.. > > > > Trying to connect to a Drill 1.10 session from any JDBC Business Tool > > using the Drill 1.10 provided jar fails.. If I remember correctly the > > error was related to some "java.lang.OutOfMemoryError: PermGen space" > error. > > > > -----Original Message----- > > From: Abhishek Girish [mailto:[email protected]] > > Sent: Monday, April 17, 2017 10:35 AM > > To: [email protected] > > Subject: Re: Windows system Initiation Error > > > > Thanks for that, David. > > > > Regarding the JDBC issue, I'm not able to reproduce it. Drill comes up > > fine in embedded mode. Can you share more details? > > > > On Mon, Apr 17, 2017 at 10:24 AM Lee, David <[email protected]> > > wrote: > > > > > This is what I use for Drill 1.9 and Drill 1.10 > > > > > > drill.exec: { > > > cluster-id: "drillbits1", > > > zk.connect: "localhost:2181", > > > udf.directory.root: "/C:/Temp/" > > > } > > > > > > However, Drill 1.10 has other problems.. > > > > > > The drill-jdbc-all-1.10.0.jar doesn’t work for me and I think I get > > > some sort of Java memory error. I had to use the 1.9 Jar with Drill > > 1.10.. > > > > > > > > > From: Abhishek Girish [mailto:[email protected]] > > > Sent: Monday, April 17, 2017 10:15 AM > > > To: [email protected] > > > Subject: Re: Windows system Initiation Error > > > > > > Can you try providing the path in UNIX style? Say like this: > > > > > > drill.exec: { > > > ... > > > udf.directory.local: "/udf" > > > ... > > > } > > > > > > I could reproduce the issue with "C:\\udf". Updating it as shown > > > above fixed it. Also make sure the user has write permissions on > > > that dir - if not, provide a dir path which is writable. > > > > > > On Mon, Apr 17, 2017 at 8:17 AM Vignesh K. > > > <[email protected] <mailto:[email protected]>> > > wrote: > > > > > > Hi Team, > > > > > > I started to use Apache Drill recently. Initially I was running > > > through an Linux system and everything was working fine. But when I > > > try to run through a window system by following the steps in the > > > site > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__drill.apache.or > > > g_ > > > docs_drill-2Din-2D10-2Dminutes_&d=DwIFaQ&c=zUO0BtkCe66yJvAZ4cAvZg&r= > > > Sp > > > eiLeBTifecUrj1SErsTRw4nAqzMxT043sp_gndNeI&m=FnkrjUQLNEICQltoINYwKRGR > > > fG > > > fOxC8ADSgNcLY9uwU&s=mkprm2H6AqdqRiJjaEZV_VQvDSeujioUPc2GnI5x6zo&e= < > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__drill.apache.or > > > g_ > > > docs_drill-2Din-2D10-2Dminutes_&d=DwMFaQ&c=zUO0BtkCe66yJvAZ4cAvZg&r= > > > Sp > > > eiLeBTifecUrj1SErsTRw4nAqzMxT043sp_gndNeI&m=3XDIRQvkUebJWZIx2QprREJ7 > > > dV > > > mxKKh70tj7KWfdlFg&s=9i3U6ENSJMWVZ1W2eL1GeoQ5mciFjde6uvqPJYN3eI4&e=> > > > I faced issues stating Local UDF directory must exist. > > > > > > I tried changing drill.exec.udf.directory.local:"C:\\UDF" but > > > then too there was a backward slash in the beginning "\C:\\UDF" so > > > it still showed the error. > > > > > > Could you guys please let me know what is the issue? > > > > > > [cid:[email protected]] > > > > > > Thanks and Regards, > > > > > > Vignesh K > > > > > > This message may contain information that is confidential or > privileged. > > > If you are not the intended recipient, please advise the sender > > > immediately and delete this message. See > > > http://www.blackrock.com/corporate/en-us/compliance/email-disclaimer > > > s for further information. Please refer to > > > http://www.blackrock.com/corporate/en-us/compliance/privacy-policy > > > for more information about BlackRock’s Privacy Policy. > > > For a list of BlackRock's office addresses worldwide, see > > > http://www.blackrock.com/corporate/en-us/about-us/contacts-locations. > > > > > > © 2017 BlackRock, Inc. All rights reserved. > > > > > >
