[jira] [Created] (MAPREDUCE-7117) NoClassDefFoundError when running mapreduce examples
Charan Hebri created MAPREDUCE-7117:
---
Summary: NoClassDefFoundError when running mapreduce examples
Key: MAPREDUCE-7117
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7117
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Charan Hebri
Seeing this on latest trunk while running map reduce client examples,
{noformat}
java.lang.NoClassDefFoundError: junit/framework/TestCase
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.apache.hadoop.test.MapredTestDriver.(MapredTestDriver.java:109)
at org.apache.hadoop.test.MapredTestDriver.(MapredTestDriver.java:61)
at org.apache.hadoop.test.MapredTestDriver.main(MapredTestDriver.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: java.lang.ClassNotFoundException: junit.framework.TestCase
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 21 more
{noformat}
--
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] [Commented] (MAPREDUCE-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389059#comment-16389059
]
Charan Hebri commented on MAPREDUCE-7062:
-
[~rohithsharma] could you help review this patch?
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Assignee: Charan Hebri
>Priority: Major
> Attachments: MAPREDUCE-7062.001.patch
>
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charan Hebri updated MAPREDUCE-7062:
Status: Patch Available (was: In Progress)
Added notes in mapred-default.xml
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Assignee: Charan Hebri
>Priority: Major
> Attachments: MAPREDUCE-7062.001.patch
>
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charan Hebri updated MAPREDUCE-7062:
Attachment: MAPREDUCE-7062.001.patch
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Assignee: Charan Hebri
>Priority: Major
> Attachments: MAPREDUCE-7062.001.patch
>
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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] [Work started] (MAPREDUCE-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAPREDUCE-7062 started by Charan Hebri.
---
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Assignee: Charan Hebri
>Priority: Major
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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] [Assigned] (MAPREDUCE-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charan Hebri reassigned MAPREDUCE-7062:
---
Assignee: Charan Hebri
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Assignee: Charan Hebri
>Priority: Major
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
[
https://issues.apache.org/jira/browse/MAPREDUCE-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charan Hebri updated MAPREDUCE-7062:
Description:
When applications are submitted to YARN, tags are generated in the format
TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
However, MR applications don't follow this format and the tags submitted via
the property mapreduce.job.tags are of the format,
{flow_name} ,\{flow_version},\{flow_run_id}
Due to this, YARN falls back to default values for flow name, flow version and
flow run id which in turn are used in ATSv2.
There are 2 approaches that could be taken to make MR tags compatible with
ATSv2,
Fix in the MR code
-
Prefix any tags specified with the ones needed by the YARN Timeline Service
v2. But MR is legacy code and hence these changes could affect how users are
using these tags.
Add a note in mapred-default.xml
Add notes in the property name, mapreduce.job.tags mentioning that for
purposes of ATSv2, prefixes need to be added to the tag names.
was:
When applications are submitted to YARN, tags are generated in the format
TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},
TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
However, MR applications don't follow this format and the tags submitted via
the property mapreduce.job.tags are of the format,
{flow_name},\{flow_version},\{flow_run_id}
Due to this, YARN falls back to default values for flow name, flow version and
flow run id which in turn are used in ATSv2.
There are 2 approaches that could be taken to make MR tags compatible with
ATSv2,
Fix in the MR code
-
Prefix any tags specified with the ones needed by the YARN Timeline Service v2.
But MR is legacy code and hence these changes could affect how users are using
these tags.
Add a note in mapred-default.xml
Add notes in the property name, mapreduce.job.tags mentioning that for purposes
of ATSv2, prefixes need to be added to the tag names.
> MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow
> versions
> -
>
> Key: MAPREDUCE-7062
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Charan Hebri
>Priority: Major
>
> When applications are submitted to YARN, tags are generated in the format
>
> TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
> However, MR applications don't follow this format and the tags submitted via
> the property mapreduce.job.tags are of the format,
> {flow_name} ,\{flow_version},\{flow_run_id}
> Due to this, YARN falls back to default values for flow name, flow version
> and flow run id which in turn are used in ATSv2.
> There are 2 approaches that could be taken to make MR tags compatible with
> ATSv2,
> Fix in the MR code
> -
> Prefix any tags specified with the ones needed by the YARN Timeline Service
> v2. But MR is legacy code and hence these changes could affect how users are
> using these tags.
> Add a note in mapred-default.xml
>
> Add notes in the property name, mapreduce.job.tags mentioning that for
> purposes of ATSv2, prefixes need to be added to the tag names.
--
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] [Created] (MAPREDUCE-7062) MR job tags not compatible with YARN ATSv2 flow names, flow run ids and flow versions
Charan Hebri created MAPREDUCE-7062:
---
Summary: MR job tags not compatible with YARN ATSv2 flow names,
flow run ids and flow versions
Key: MAPREDUCE-7062
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Charan Hebri
When applications are submitted to YARN, tags are generated in the format
TIMELINE_FLOW_NAME_TAG:\{flow_name},TIMELINE_FLOW_VERSION_TAG:\{flow_version},
TIMELINE_FLOW_RUN_ID_TAG:\{flow_run_id}
However, MR applications don't follow this format and the tags submitted via
the property mapreduce.job.tags are of the format,
{flow_name},\{flow_version},\{flow_run_id}
Due to this, YARN falls back to default values for flow name, flow version and
flow run id which in turn are used in ATSv2.
There are 2 approaches that could be taken to make MR tags compatible with
ATSv2,
Fix in the MR code
-
Prefix any tags specified with the ones needed by the YARN Timeline Service v2.
But MR is legacy code and hence these changes could affect how users are using
these tags.
Add a note in mapred-default.xml
Add notes in the property name, mapreduce.job.tags mentioning that for purposes
of ATSv2, prefixes need to be added to the tag names.
--
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
