FAQ
MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
--------------------------------------------------------------------------------------------

Key: HADOOP-5932
URL: https://issues.apache.org/jira/browse/HADOOP-5932
Project: Hadoop Core
Issue Type: Bug
Components: contrib/capacity-sched
Affects Versions: 0.20.0
Reporter: Karam Singh


MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Vinod K V (JIRA) at May 28, 2009 at 9:32 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Vinod K V updated HADOOP-5932:
    ------------------------------

    Attachment: HADOOP-5932-20090528.txt

    Discussed with Karam regarding this and looked at the logs. The bug happened due to a misplaced local variable myVmem initialization in MemoryMatcher.getMemReservedForTasks().

    Quick patch for testing.
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Attachments: HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Vinod K V (JIRA) at May 28, 2009 at 11:28 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Vinod K V updated HADOOP-5932:
    ------------------------------

    Attachment: HADOOP-5932-20090528.1.txt

    Updated patch that completes the test-cases.
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at May 29, 2009 at 5:38 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714304#action_12714304 ]

    Hemanth Yamijala commented on HADOOP-5932:
    ------------------------------------------

    +1 for the fix. There are comments I stumbled upon independently in the test cases which I've already raised in HADOOP-5934. So, I am not repeating those here under the assumption these will be fixed there.

    Can you please upload the results of test-patch and capacity scheduler tests ?
    Also, can you please make sure there's a patch that works for the 20 branch ?
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Vinod K V (JIRA) at May 29, 2009 at 8:16 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714355#action_12714355 ]

    Vinod K V commented on HADOOP-5932:
    -----------------------------------

    ant test-patch passed. All capacity scheduler tests passed except TestQueueCapacities which is tracked at HADOOP-5646.
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Vinod K V (JIRA) at May 29, 2009 at 8:24 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Vinod K V reassigned HADOOP-5932:
    ---------------------------------

    Assignee: Vinod K V
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Assignee: Vinod K V
    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Vinod K V (JIRA) at May 29, 2009 at 8:25 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714359#action_12714359 ]

    Vinod K V commented on HADOOP-5932:
    -----------------------------------

    The same patch applies for branch-0.20 also.
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at May 29, 2009 at 8:32 am
    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Hemanth Yamijala resolved HADOOP-5932.
    --------------------------------------

    Resolution: Fixed
    Fix Version/s: 0.20.1
    Hadoop Flags: [Reviewed]

    I committed this to trunk and branch 0.20. Thanks, Vinod !
    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --------------------------------------------------------------------------------------------

    Key: HADOOP-5932
    URL: https://issues.apache.org/jira/browse/HADOOP-5932
    Project: Hadoop Core
    Issue Type: Bug
    Components: contrib/capacity-sched
    Affects Versions: 0.20.0
    Reporter: Karam Singh
    Assignee: Vinod K V
    Fix For: 0.20.1

    Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt


    MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedMay 28, '09 at 9:08a
activeMay 29, '09 at 8:32a
posts8
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hemanth Yamijala (JIRA): 8 posts

People

Translate

site design / logo © 2022 Grokbase