Thanks Abhishek. We will handle the cancelled part and resubmit the query again.
We found this issue after using drill for more than 3 years now. Any help with drill memory issues ? We are kind of stuck now that we could not upgrade drill to 1.16 and all the new code had to be rolled back. Thanks, Nitin On Wed, Jan 8, 2020 at 12:24 AM Abhishek Girish <[email protected]> wrote: > Thanks Nitin. > > As mentioned on Slack, Drill would not resubmit the queries. If any > drillbit being used in query execution goes down, the query in question is > cancelled. > > On Tue, Jan 7, 2020 at 10:51 AM Nitin Pawar <[email protected]> > wrote: > > > I have created DRILL-7517 < > > https://issues.apache.org/jira/browse/DRILL-7517> > > this for drill shutting down issue. > > > > DRILL setup > > MAX Memory given : 56GB > > HEAP-12GB > > Direct memory: 40GB > > > > Thanks, > > Nitin > > > > On Tue, Jan 7, 2020 at 10:15 PM Nitin Pawar <[email protected]> > > wrote: > > > > > Hello Team > > > We have recently upgraded to drill-1.16 from drill-1.13 version > > > and we have started to notice lots of OOM issues .. its same setup with > > > changed binaries > > > till we figured out what’s the issue, we wanted to keep restarting > > > drillbits with cronjobs > > > > > > my question is : *If a drill is restarted .. would the queries with > this > > > node as foreman be resubmitted automatically ?* > > > > > > Also we have a 64GB RAM machines. Can someone recommend memory setting > > for > > > this environment > > > > > > -- > > > Nitin Pawar > > > > > > > > > -- > > Nitin Pawar > > > -- Nitin Pawar
