[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated MAPREDUCE-6052: --- Resolution: Fixed Fix Version/s: 2.6.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk, branch-2 and branch-2.6. Thanks, Junping! Also thanks contributing ur ideas, Xuan and Vinod! > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Fix For: 2.6.0 > > Attachments: MAPREDUCE-6052-v2.patch, MAPREDUCE-6052-v3.patch, > MAPREDUCE-6052-v4.patch, MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6052: -- Attachment: MAPREDUCE-6052-v4.patch > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Attachments: MAPREDUCE-6052-v2.patch, MAPREDUCE-6052-v3.patch, > MAPREDUCE-6052-v4.patch, MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6052: -- Attachment: MAPREDUCE-6052-v3.patch > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Attachments: MAPREDUCE-6052-v2.patch, MAPREDUCE-6052-v3.patch, > MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6052: -- Attachment: MAPREDUCE-6052-v2.patch > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Attachments: MAPREDUCE-6052-v2.patch, MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6052: -- Status: Patch Available (was: Open) > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Attachments: MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MAPREDUCE-6052) Support overriding log4j.properties per job
[ https://issues.apache.org/jira/browse/MAPREDUCE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated MAPREDUCE-6052: -- Attachment: MAPREDUCE-6052.patch Attache a quick patch to fix it. > Support overriding log4j.properties per job > --- > > Key: MAPREDUCE-6052 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6052 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Junping Du >Assignee: Junping Du > Attachments: MAPREDUCE-6052.patch > > > For current MR application, the "log4j.configuration" is hard coded to > container-log4j.properties within each node. We still need flexibility to > override it per job like what we do in MRV1. > {code} > public static void addLog4jSystemProperties( > String logLevel, long logSize, int numBackups, List vargs) { > vargs.add("-Dlog4j.configuration=container-log4j.properties"); > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)