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

Posted to issues@tez.apache.org by "Ashutosh Chauhan (Jira)" <ji...@apache.org> on 2020/03/19 18:46:00 UTC

[jira] [Commented] (TEZ-4087) Shuffle: Fix shuffle cleanup to prevent thread leaks

    [ https://issues.apache.org/jira/browse/TEZ-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062859#comment-17062859 ] 

Ashutosh Chauhan commented on TEZ-4087:
---------------------------------------

[~rajesh.balamohan] you want to add your patch on jira so we get a TezQA run on it.

> Shuffle: Fix shuffle cleanup to prevent thread leaks
> ----------------------------------------------------
>
>                 Key: TEZ-4087
>                 URL: https://issues.apache.org/jira/browse/TEZ-4087
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In certain cases, Shuffle's cleanupIgnoreErrors() is not called. This leaves 4 threads (inmem, diskmerger, Referee, ShuffleAndMergeRunner) run forever.
> When these are run in long running processes (e.g LLAP in Hive), they reach the thread limits over time.
> Note: Root cause why cleanupIgnoreErrors() is not invoked is not yet known. I will share the details when i get more details on this. Creating this ticket to add additional safety knobs to ensure that thread leaks do not happen.
>  



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