Can you provide more details for a repro? Multiple issues can potentially cause or (incorrectly) report a memory leak.
If you notice, the 'Actual' value is zero, so there isn't really a leak, but the resources were not closed properly. What does the stack trace say? On 6/7/2018 11:05:32 PM, Nitin Pawar <[email protected]> wrote: Hi .. Any help on this? This is happening in our production environment so if we have any configurations to avoid this ?? Thanks, Nitin On Tue, Jun 5, 2018 at 8:21 AM, Nitin Pawar wrote: > > > Hi we are seeing memory leak in apache drill 1.13.0 version > > According to https://issues.apache.org/jira/browse/DRILL-6079, says it is > fixed but it is not. > > Is there way we can avoid this error by setting any config variables?? > > SYSTEM ERROR: IllegalStateException: Memory was leaked by query. Memory > leaked: (2097152) > Allocator(op:1:0:7:ParquetRowGroupScan) 1000000/0/64856064/10000000000 > (res/actual/peak/limit) > > > Fragment 1:0 > > [Error Id: 1b712605-ca3d-45cb-9c61-224b190ab4b2 on > ip-10-0-101-247.ec2.internal:31010] > Caused By: SYSTEM ERROR: IllegalStateException: Memory was leaked by > query. Memory leaked: (2097152) > Allocator(op:1:0:7:ParquetRowGroupScan) 1000000/0/64856064/10000000000 > (res/actual/peak/limit) > > > Fragment 1:0 > > [Error Id: 1b712605-ca3d-45cb-9c61-224b190ab4b2 on > ip-10-0-101-247.ec2.internal:31010] > > -- > Nitin Pawar > -- Nitin Pawar
