Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 3 Apr 2013 20:49:16 +0000 (UTC)
From: "Omkar Vinit Joshi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12640594.1365022063104.101394.1365022156050@arcas>
In-Reply-To: <JIRA.12640594.1365022063104@arcas>
References: <JIRA.12640594.1365022063104@arcas>
Subject: [jira] [Created] (YARN-539) Memory leak in case resource
 localization fails. LocalizedResource remains in memory.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Omkar Vinit Joshi created YARN-539:
--------------------------------------

             Summary: Memory leak in case resource localization fails. LocalizedResource remains in memory.
                 Key: YARN-539
                 URL: https://issues.apache.org/jira/browse/YARN-539
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Omkar Vinit Joshi
            Assignee: Omkar Vinit Joshi


If resource localization fails then resource remains in memory and is
1) Either cleaned up when next time cache cleanup runs and there is space crunch. (If sufficient space in cache is available then it will remain in memory).
2) reused if LocalizationRequest comes again for the same resource.

I think when resource localization fails then that event should be sent to LocalResourceTracker which will then remove it from its cache.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira