Hi Sanjiv, Drill should have written a log file. Does the log file contain an entry for the exception? Perhaps post the first five or so lines from that log entry (the whole stack trace can be pretty long.)
Was this a fatal exception from Drill or did the JVM itself die? (If the JVM dies, it often prints a log file that tells you it was a JVM issue.) The memory limit impact rather depends on the kind of query you ran. Different bits of Drill have different memory demands. Please tell us a bit more about your query and the “shape” of your data: number of columns, width of the larger columns, etc. With that info we may be able to suggest settings to work around the issue. - Paul > On Jan 3, 2017, at 6:31 AM, Sanjiv Kumar <[email protected]> wrote: > > Hello > I am using drill latest version (1.9) in embedded mode in Ubuntu > system. > My query is :- > If i run query having less number of records, drill > working fine. > But If i run long query having (8124042 records), drill > stopped without throwing any error. > > NOTE:- My Ubuntu Server memory is 4GB. Is this cause problem? If not then > please tell me the solution.
