drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victoria Markman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-4266) Possible memory leak (fragmentation ?) in rpc layer
Date Tue, 12 Jan 2016 17:28:40 GMT
Victoria Markman created DRILL-4266:

             Summary: Possible memory leak (fragmentation ?)  in rpc layer
                 Key: DRILL-4266
                 URL: https://issues.apache.org/jira/browse/DRILL-4266
             Project: Apache Drill
          Issue Type: Bug
          Components: Execution - RPC
    Affects Versions: 1.5.0
            Reporter: Victoria Markman

I have executed 5 tests from Advanced/mondrian test suite in a loop overnight.
My observation is that memory steadily grew from 117MB to 1.8GB and remained on that level
for 14875 iteration of the tests.

My question is: why do 5 queries that were able to execute with 117MB of memory require 1.8GB
of memory after 5 hours of execution ?

* Memory used after each test iteration : memComsumption_framework.output_Tue_Jan_12_06:31:24_UTC_2016
* Log of the framework run: drill.log.2016-01-12-16
* Tests: test.tar

Single node 32 core box. 
0: jdbc:drill:schema=dfs> select * from sys.options where status like '%CHANGED%';
|               name                |   kind   |  type   |  status  | num_val  | string_val
 | bool_val  | float_val  |
| planner.enable_decimal_data_type  | BOOLEAN  | SYSTEM  | CHANGED  | null     | null    
   | true      | null       |
1 row selected (1.309 seconds)


* tar xvd test.tar into Functional/test directory 
* ./run.sh -s Functional/test -g regression -t 180 -n 5 -i 10000000 -m

This is very similar behavior as Hakim and I observed long time ago with window functions.
Now, that new allocator is in place we rerun this test and we see the similar things, and
allocator does not seem to think that we have a memory leak. Hence the speculation that memory
is leaked in RPC layer.

I'm going to reduce planner.width.max_per_node and see if it has any effect on memory allocation
(speculating again ...)

This message was sent by Atlassian JIRA

View raw message