You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Vitalii Diravka (Jira)" <ji...@apache.org> on 2021/11/03 07:35:00 UTC

[jira] [Created] (DRILL-8030) Memory leak in TestDrillbitResilience

Vitalii Diravka created DRILL-8030:
--------------------------------------

             Summary: Memory leak in TestDrillbitResilience
                 Key: DRILL-8030
                 URL: https://issues.apache.org/jira/browse/DRILL-8030
             Project: Apache Drill
          Issue Type: Improvement
          Components: Tools, Build &amp; Test
    Affects Versions: 1.19.0
            Reporter: Vitalii Diravka
            Assignee: Vitalii Diravka
             Fix For: Future


DRILL-7908 fixes distributed deadlocks in _TestDrillbitResilience_ and add better timing for simulation the different Drill states. But sometimes tests indicate memory leak.
They are not there, looks like Drill just check actual memory to early, when dot all fragments are closed, so adding timeout before final _countAllocatedMemory_ fixes the issue. 
The other reason of test failures - the queries were not in expected state before cancelling (for instance in STARTING state instead of RUNNING), so adding timeout before starting cancellation thread allows to wait the proper drill query state, which is expected to be for Drill  in test case before cancellation.
I don't have anymore test failures with NUM_RUNS = 1000 (@RepeatedTest) for the problematic test cases.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)