[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilun Fan updated MAPREDUCE-6925: -- Target Version/s: 3.5.0 (was: 3.4.0) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov >Priority: Major > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated MAPREDUCE-6925: Target Version/s: 3.4.0 (was: 3.3.0) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov >Priority: Major > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated MAPREDUCE-6925: -- Target Version/s: 3.3.0 (was: 3.2.0) Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker. > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov >Priority: Major > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated MAPREDUCE-6925: --- Target Version/s: 3.1.0 (was: 2.9.0, 3.0.0) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated MAPREDUCE-6925: --- Target Version/s: 2.9.0, 3.0.0 (was: 2.9.0, 3.0.0-beta1) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6925: -- Fix Version/s: (was: 3.0.0-alpha1) (was: 2.9.0) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6925: -- Target Version/s: 2.9.0, 3.0.0-beta1 (was: 2.7.0) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Updated] (MAPREDUCE-6925) CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
[ https://issues.apache.org/jira/browse/MAPREDUCE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6925: -- Hadoop Flags: (was: Reviewed) > CLONE - Make Counter limits consistent across JobClient, MRAppMaster, and > YarnChild > --- > > Key: MAPREDUCE-6925 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6925 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, client, task >Affects Versions: 2.4.0 >Reporter: Gera Shegalov >Assignee: Gera Shegalov > > Currently, counter limits "mapreduce.job.counters.*" handled by > {{org.apache.hadoop.mapreduce.counters.Limits}} are initialized > asymmetrically: on the client side, and on the AM, job.xml is ignored whereas > it's taken into account in YarnChild. > It would be good to make the Limits job-configurable, such that max > counters/groups is only increased when needed. With the current Limits > implementation relying on static constants, it's going to be challenging for > tools that submit jobs concurrently without resorting to class loading > isolation. > The patch that I am uploading is not perfect but demonstrates the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org