[jira] [Commented] (MAPREDUCE-4101) nodemanager depends on /bin/bash
[ https://issues.apache.org/jira/browse/MAPREDUCE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267256#comment-13267256 ] Radim Kolar commented on MAPREDUCE-4101: I will rework this patch but first i need to work on pluggable process tree > nodemanager depends on /bin/bash > > > Key: MAPREDUCE-4101 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4101 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: nodemanager >Affects Versions: 0.23.1, trunk > Environment: FreeBSD 8.2 / 64 bit >Reporter: Radim Kolar > Labels: patch > Attachments: bash-replace-by-sh.txt > > > Currently nodemanager depends on bash shell. It should be well documented for > system not having bash installed by default such as FreeBSD. Because only > basic functionality of bash is used, probably changing bash to /bin/sh would > work enough. > i found 2 cases: > 1. DefaultContainerExecutor.java creates file with /bin/bash hardcoded in > writeLocalWrapperScript. (this needs bash in /bin) > 2. yarn-hduser-nodemanager-ponto.amerinoc.com.log:2012-04-03 19:50:10,798 > INFO org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: > launchContainer: [bash, -c, > /tmp/nm-local-dir/usercache/hduser/appcache/application_1333474251533_0002/container_1333474251533_0002_01_12/default_container_executor.sh] > this created script is also launched by bash - bash anywhere in path works - > in freebsd it is /usr/local/bin/bash -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4221) Remove jquery theming support
[ https://issues.apache.org/jira/browse/MAPREDUCE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267245#comment-13267245 ] Eli Collins commented on MAPREDUCE-4221: +1 amen > Remove jquery theming support > - > > Key: MAPREDUCE-4221 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4221 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.0.0 >Reporter: Todd Lipcon > Labels: newbie > > As of today we have 9.4MB of JQuery themes in our code tree. In addition to > being a waste of space, it's a highly questionable feature. I've never heard > anyone complain that the Hadoop interface isn't themeable enough, and there's > far more value in consistency across installations than there is in > themeability. Let's rip it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4205) retrofit all JVM shutdown hooks to use ShutdownHookManager
[
https://issues.apache.org/jira/browse/MAPREDUCE-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267159#comment-13267159
]
Alejandro Abdelnur commented on MAPREDUCE-4205:
---
i've just tried applying it on trunk's HEAD and didn't complain at all
{code}
curl
https://issues.apache.org/jira/secure/attachment/12524918/MAPREDUCE-4205.patch
|patch -p0
{code}
> retrofit all JVM shutdown hooks to use ShutdownHookManager
> --
>
> Key: MAPREDUCE-4205
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4205
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
>Affects Versions: 2.0.0
>Reporter: Alejandro Abdelnur
>Assignee: Alejandro Abdelnur
> Fix For: 2.0.0
>
> Attachments: MAPREDUCE-4205.patch
>
>
> to avoid JVM shutdownhook race conditions, all shutdown hooks should be
> retrofitted to use ShutdownHookManager (HADOOP-8325)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4205) retrofit all JVM shutdown hooks to use ShutdownHookManager
[ https://issues.apache.org/jira/browse/MAPREDUCE-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267145#comment-13267145 ] Todd Lipcon commented on MAPREDUCE-4205: It seems like it failed to apply - does the patch apply against trunk? > retrofit all JVM shutdown hooks to use ShutdownHookManager > -- > > Key: MAPREDUCE-4205 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4205 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2 >Affects Versions: 2.0.0 >Reporter: Alejandro Abdelnur >Assignee: Alejandro Abdelnur > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4205.patch > > > to avoid JVM shutdownhook race conditions, all shutdown hooks should be > retrofitted to use ShutdownHookManager (HADOOP-8325) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267126#comment-13267126 ] xieguiming commented on MAPREDUCE-3873: --- Hi Vinod: Thanks for your testCase. TestResourceTrackerService is very good. At the beginning, I only focus on the NodesListManager:isValidNode function. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4221) Remove jquery theming support
Todd Lipcon created MAPREDUCE-4221: -- Summary: Remove jquery theming support Key: MAPREDUCE-4221 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4221 Project: Hadoop Map/Reduce Issue Type: Improvement Components: webapps Affects Versions: 2.0.0 Reporter: Todd Lipcon As of today we have 9.4MB of JQuery themes in our code tree. In addition to being a waste of space, it's a highly questionable feature. I've never heard anyone complain that the Hadoop interface isn't themeable enough, and there's far more value in consistency across installations than there is in themeability. Let's rip it out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267059#comment-13267059 ] Hadoop QA commented on MAPREDUCE-3873: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12525364/MAPREDUCE-3873-20120502.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. -1 javadoc. The javadoc tool appears to have generated 2 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2351//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2351//console This message is automatically generated. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267055#comment-13267055
]
Hudson commented on MAPREDUCE-4219:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #2193 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2193/])
MAPREDUCE-4219. make default container-executor.conf.dir be a path relative
to the container-executor binary. (rvs via tucu) (Revision 1333241)
Result = ABORTED
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333241
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.h
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/test/test-container-executor.c
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Status: Patch Available (was: Open) > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Attachment: MAPREDUCE-3873-20120502.txt Alright, that's buggy logic, cannot optimize the ip look up away. Reverting to old patch that [~xieguiming] wrote up. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Status: Open (was: Patch Available) > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-3863) 0.22 branch mvn deploy is not publishing hadoop-streaming JAR
[ https://issues.apache.org/jira/browse/MAPREDUCE-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reassigned MAPREDUCE-3863: -- Assignee: Benoy Antony (was: Konstantin Boudnik) Cos, you missed the new file hadoop-streaming-template.xml in the previous commit. I just committed it. Reassigning this to Benoy. > 0.22 branch mvn deploy is not publishing hadoop-streaming JAR > - > > Key: MAPREDUCE-3863 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3863 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: build >Affects Versions: 0.22.0, 0.22.1 >Reporter: Alejandro Abdelnur >Assignee: Benoy Antony >Priority: Critical > Fix For: 0.22.1 > > Attachments: MAPREDUCE-3863.patch, MAPREDUCE-3863.patch, > MAPREDUCE-3863.patch > > > Without this JAR Oozie cannot be built/tested against 0.22 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267026#comment-13267026
]
Hudson commented on MAPREDUCE-4219:
---
Integrated in Hadoop-Common-trunk-Commit #2175 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2175/])
MAPREDUCE-4219. make default container-executor.conf.dir be a path relative
to the container-executor binary. (rvs via tucu) (Revision 1333241)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333241
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.h
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/test/test-container-executor.c
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267022#comment-13267022
]
Hudson commented on MAPREDUCE-4219:
---
Integrated in Hadoop-Hdfs-trunk-Commit #2249 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2249/])
MAPREDUCE-4219. make default container-executor.conf.dir be a path relative
to the container-executor binary. (rvs via tucu) (Revision 1333241)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333241
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.h
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/test/test-container-executor.c
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated MAPREDUCE-4219:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Roman. Committed to trunk and branch-2.
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266987#comment-13266987
]
Hadoop QA commented on MAPREDUCE-4219:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525340/MAPREDUCE-4219.patch.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
-1 javadoc. The javadoc tool appears to have generated 2 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2350//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2350//console
This message is automatically generated.
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated MAPREDUCE-4219:
--
Status: Patch Available (was: Open)
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3377) Compatibility issue with 0.20.203.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266972#comment-13266972 ] Matt Foley commented on MAPREDUCE-3377: --- The merge to branch-1.0 included, apparently by accident, changes to build.xml that broke the native builds of task-controller and jsvc. I've reverted the build.xml change only. This error only affected branch-1.0, not branch-1 nor the other branches. > Compatibility issue with 0.20.203. > -- > > Key: MAPREDUCE-3377 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3377 > Project: Hadoop Map/Reduce > Issue Type: Bug >Affects Versions: 0.20.203.0 > Environment: 0.20.203.0 standalone JDK 1.6 Linux >Reporter: Jane Chen >Assignee: Jane Chen > Fix For: 1.0.3, 2.0.0 > > Attachments: err-after, err-before, mapreduce-3377-branch-1.patch, > mapreduce-3377-branch-1.patch, mapreduce-3377.patch, mapreduce-3377.patch, > mapreduce-3377.patch, mapreduce-3377.patch, out-after, out-before > > > I have an OutputFormat which implements Configurable. I set new config > entries to a job configuration during checkOutputSpec() so that the tasks > will get the config entries through the job configuration. This works fine > in 0.20.2, but stopped working starting from 0.20.203. With 0.20.203, my > OutputFormat still has the configuration set, but the copy a task gets does > not have the new entries that are set as part of checkOutputSpec(). > I believe that the problem is with JobClient. The job configuration needs to > wait till checkOutputSpec() is returned before being cloned and submitted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266966#comment-13266966 ] Hadoop QA commented on MAPREDUCE-3873: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12525352/MAPREDUCE-3873-20120502.1.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. -1 javadoc. The javadoc tool appears to have generated 2 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2349//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2349//console This message is automatically generated. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4163) consistently set the bind address
[
https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266961#comment-13266961
]
Daryn Sharp commented on MAPREDUCE-4163:
Javadoc warnings are from common. The findbugs failure is odd. Findbugs
appears to be pulling stale jars instead of using the ones it just built. It
failed to locate a new yarn method from an earlier patch, however, the compile
and tests succeeded.
> consistently set the bind address
> -
>
> Key: MAPREDUCE-4163
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4163
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
>Affects Versions: 0.23.0, 0.24.0, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-3659-1.patch, MAPREDUCE-3659-2.patch,
> MAPREDUCE-3659.patch
>
>
> Use {{NetUtils.getConnectAddress}} for determining the bind address used for
> setting a token's service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4152) map task left hanging after AM dies trying to connect to RM
[ https://issues.apache.org/jira/browse/MAPREDUCE-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266960#comment-13266960 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-4152: Going back and forth on this one, apologies. So the situation is that RM went down somehow and AM exited without killing its tasks. This is expected IIRC. Here's what I think: - When RM restart works, AMs should *never* exit because of connection issues. (Of course, there is a corner case of AMs network itself being down, we should handle that somehow) - Even in the short term, if RM goes down and AM exits in the mean while, whenever RM is back up, it will(should) kill all the containers of this application( by commanding the NMs to do so). Given above, I don't see why the AM needs to handle this specially. May be I am missing something? > map task left hanging after AM dies trying to connect to RM > --- > > Key: MAPREDUCE-4152 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4152 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.2 >Reporter: Thomas Graves >Assignee: Thomas Graves > Attachments: MAPREDUCE-4152.patch, MAPREDUCE-4152.patch > > > We had an instance where the RM went down for more then an hour. The > application master exited with "Could not contact RM after 36 > milliseconds" > 2012-04-11 10:43:36,040 INFO [AsyncDispatcher event handler] > org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: > job_1333003059741_15999Job Transitioned from RUNNING to ERROR -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Status: Patch Available (was: Open) > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Attachment: MAPREDUCE-3873-20120502.1.txt A minor fix to avoid the IP lookup in all cases. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Status: Open (was: Patch Available) > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.1.txt, > MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266945#comment-13266945
]
Roman Shaposhnik commented on MAPREDUCE-4219:
-
I tested Hadoop examples on the fully distributed secure cluster with ../conf
baked in as a HADOOP_CONF
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
[ https://issues.apache.org/jira/browse/MAPREDUCE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266925#comment-13266925 ] Jonathan Eagles commented on MAPREDUCE-4220: javadoc warnings are not in the mapreduce project and are preexisting. > RM apps page starttime/endtime sorts are incorrect > -- > > Key: MAPREDUCE-4220 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Attachments: MAPREDUCE-4220.patch > > > Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
[ https://issues.apache.org/jira/browse/MAPREDUCE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266924#comment-13266924 ] Jonathan Eagles commented on MAPREDUCE-4220: I have manually verified the two columns sorts correctly after the patch. > RM apps page starttime/endtime sorts are incorrect > -- > > Key: MAPREDUCE-4220 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Attachments: MAPREDUCE-4220.patch > > > Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266915#comment-13266915 ] Hadoop QA commented on MAPREDUCE-3873: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12525347/MAPREDUCE-3873-20120502.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. -1 javadoc. The javadoc tool appears to have generated 2 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2348//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2348//console This message is automatically generated. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Attachment: MAPREDUCE-3873-20120502.txt Patch with tests. Tests fail without the fix and pass with. Will push this in if/when Jenkins blesses.. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873-20120502.txt, MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3873) Nodemanager is not getting decommisioned if the absolute ip is given in exclude file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3873: --- Status: Open (was: Patch Available) Patch looks good. +1. It is easy to write a test, I already have one. Let me upload the patch with a test case. > Nodemanager is not getting decommisioned if the absolute ip is given in > exclude file. > - > > Key: MAPREDUCE-3873 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3873 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager >Affects Versions: 0.23.0 >Reporter: Nishan Shetty >Assignee: xieguiming >Priority: Minor > Attachments: MAPREDUCE-3873.patch > > > Configure absolute ip in "yarn.resourcemanager.nodes.exclude-path" and try to > decommission the node. > It is not getting decommisioned.But if the hostname is given, decommissioning > is happening. > I have also given the ip-host mapping of each machine in /etc/hosts.(i,e in > every machine the other machines ip-host mapping is specified). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
[ https://issues.apache.org/jira/browse/MAPREDUCE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266878#comment-13266878 ] Hadoop QA commented on MAPREDUCE-4220: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12525343/MAPREDUCE-4220.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated 2 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2347//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2347//console This message is automatically generated. > RM apps page starttime/endtime sorts are incorrect > -- > > Key: MAPREDUCE-4220 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Attachments: MAPREDUCE-4220.patch > > > Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4215) RM app page shows 500 error on appid parse error
[ https://issues.apache.org/jira/browse/MAPREDUCE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266869#comment-13266869 ] Jonathan Eagles commented on MAPREDUCE-4215: javadoc warnings are not in the mapreduce project > RM app page shows 500 error on appid parse error > > > Key: MAPREDUCE-4215 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4215 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4215.patch > > > For example, cluster/app/application_1335823499485_000a has displays this > error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
[ https://issues.apache.org/jira/browse/MAPREDUCE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated MAPREDUCE-4220: --- Target Version/s: 0.23.3, 2.0.0 (was: 2.0.0, 0.23.3) Status: Patch Available (was: Open) > RM apps page starttime/endtime sorts are incorrect > -- > > Key: MAPREDUCE-4220 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Attachments: MAPREDUCE-4220.patch > > > Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
[ https://issues.apache.org/jira/browse/MAPREDUCE-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated MAPREDUCE-4220: --- Attachment: MAPREDUCE-4220.patch > RM apps page starttime/endtime sorts are incorrect > -- > > Key: MAPREDUCE-4220 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Attachments: MAPREDUCE-4220.patch > > > Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4220) RM apps page starttime/endtime sorts are incorrect
Jonathan Eagles created MAPREDUCE-4220: -- Summary: RM apps page starttime/endtime sorts are incorrect Key: MAPREDUCE-4220 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4220 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.3, 2.0.0 Reporter: Jonathan Eagles Assignee: Jonathan Eagles Priority: Minor Attachments: MAPREDUCE-4220.patch Sorting by start time and end time sort lexically instead of temporally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4163) consistently set the bind address
[
https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266867#comment-13266867
]
Hadoop QA commented on MAPREDUCE-4163:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525321/MAPREDUCE-3659-2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 7 new or modified test
files.
-1 javadoc. The javadoc tool appears to have generated 2 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2345//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2345//console
This message is automatically generated.
> consistently set the bind address
> -
>
> Key: MAPREDUCE-4163
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4163
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
>Affects Versions: 0.23.0, 0.24.0, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-3659-1.patch, MAPREDUCE-3659-2.patch,
> MAPREDUCE-3659.patch
>
>
> Use {{NetUtils.getConnectAddress}} for determining the bind address used for
> setting a token's service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266863#comment-13266863
]
Hudson commented on MAPREDUCE-4210:
---
Integrated in Hadoop-Mapreduce-trunk-Commit #2190 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2190/])
MAPREDUCE-4210. Expose listener address for WebApp (Daryn Sharp via bobby)
(Revision 1333144)
Result = ABORTED
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333144
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/WebApp.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/TestWebApp.java
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3, 2.0.0, 3.0.0
>
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4215) RM app page shows 500 error on appid parse error
[ https://issues.apache.org/jira/browse/MAPREDUCE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266861#comment-13266861 ] Hadoop QA commented on MAPREDUCE-4215: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12525341/MAPREDUCE-4215.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated 2 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2346//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2346//console This message is automatically generated. > RM app page shows 500 error on appid parse error > > > Key: MAPREDUCE-4215 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4215 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4215.patch > > > For example, cluster/app/application_1335823499485_000a has displays this > error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266851#comment-13266851
]
Alejandro Abdelnur commented on MAPREDUCE-4219:
---
+1, pending feedback on test in a real cluster.
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4215) RM app page shows 500 error on appid parse error
[ https://issues.apache.org/jira/browse/MAPREDUCE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266849#comment-13266849 ] Jonathan Eagles commented on MAPREDUCE-4215: I haven't thought up a way to solve this issue generically. Perhaps, there could be a 'page not found' or 'internal error' concept. I added a small patch to fix this issue in a one off way so this use case better explanation of what happened. > RM app page shows 500 error on appid parse error > > > Key: MAPREDUCE-4215 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4215 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4215.patch > > > For example, cluster/app/application_1335823499485_000a has displays this > error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4215) RM app page shows 500 error on appid parse error
[ https://issues.apache.org/jira/browse/MAPREDUCE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated MAPREDUCE-4215: --- Target Version/s: 0.23.3, 2.0.0 (was: 2.0.0, 0.23.3) Status: Patch Available (was: Open) > RM app page shows 500 error on appid parse error > > > Key: MAPREDUCE-4215 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4215 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4215.patch > > > For example, cluster/app/application_1335823499485_000a has displays this > error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4215) RM app page shows 500 error on appid parse error
[ https://issues.apache.org/jira/browse/MAPREDUCE-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated MAPREDUCE-4215: --- Attachment: MAPREDUCE-4215.patch > RM app page shows 500 error on appid parse error > > > Key: MAPREDUCE-4215 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4215 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Fix For: 2.0.0 > > Attachments: MAPREDUCE-4215.patch > > > For example, cluster/app/application_1335823499485_000a has displays this > error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated MAPREDUCE-4219:
Attachment: MAPREDUCE-4219.patch.txt
Please take a look at the new patch.
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt, MAPREDUCE-4219.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4163) consistently set the bind address
[
https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4163:
---
Status: Patch Available (was: Open)
I've successfully tested this on a multi-node secure cluster.
> consistently set the bind address
> -
>
> Key: MAPREDUCE-4163
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4163
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
>Affects Versions: 0.23.0, 0.24.0, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-3659-1.patch, MAPREDUCE-3659-2.patch,
> MAPREDUCE-3659.patch
>
>
> Use {{NetUtils.getConnectAddress}} for determining the bind address used for
> setting a token's service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266809#comment-13266809
]
Hudson commented on MAPREDUCE-4210:
---
Integrated in Hadoop-Hdfs-trunk-Commit #2247 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2247/])
MAPREDUCE-4210. Expose listener address for WebApp (Daryn Sharp via bobby)
(Revision 1333144)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333144
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/WebApp.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/TestWebApp.java
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3, 2.0.0, 3.0.0
>
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266804#comment-13266804
]
Hudson commented on MAPREDUCE-4210:
---
Integrated in Hadoop-Common-trunk-Commit #2173 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2173/])
MAPREDUCE-4210. Expose listener address for WebApp (Daryn Sharp via bobby)
(Revision 1333144)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333144
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/WebApp.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/TestWebApp.java
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3, 2.0.0, 3.0.0
>
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-4210:
---
Resolution: Fixed
Fix Version/s: 3.0.0
2.0.0
0.23.3
Status: Resolved (was: Patch Available)
Thanks Daryn the changes look good +1.
I put this into trunk, branch-2, and branch-0.23
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3, 2.0.0, 3.0.0
>
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4163) consistently set the bind address
[
https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4163:
---
Status: Open (was: Patch Available)
> consistently set the bind address
> -
>
> Key: MAPREDUCE-4163
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4163
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
>Affects Versions: 0.23.0, 0.24.0, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-3659-1.patch, MAPREDUCE-3659-2.patch,
> MAPREDUCE-3659.patch
>
>
> Use {{NetUtils.getConnectAddress}} for determining the bind address used for
> setting a token's service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4163) consistently set the bind address
[
https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4163:
---
Attachment: MAPREDUCE-3659-2.patch
Waiting to submit patch until MAPREDUCE-4210 is committed.
> consistently set the bind address
> -
>
> Key: MAPREDUCE-4163
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4163
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
>Affects Versions: 0.23.0, 0.24.0, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-3659-1.patch, MAPREDUCE-3659-2.patch,
> MAPREDUCE-3659.patch
>
>
> Use {{NetUtils.getConnectAddress}} for determining the bind address used for
> setting a token's service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266686#comment-13266686
]
Alejandro Abdelnur commented on MAPREDUCE-4219:
---
+1, patched, built & tested native stuff.
Also, it would be great if you test it a deployed cluster before we commit it?
2 NITs:
* function name, IMO, *resolve_config_path* would be a more appropriate name.
* add a comment where *HADOOP_CONF* is used in *main.c* that the value comes
from the POM property *container-executor.conf.dir*
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266689#comment-13266689
]
Daryn Sharp commented on MAPREDUCE-4210:
Warnings came from common, not this patch.
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266673#comment-13266673
]
Hadoop QA commented on MAPREDUCE-4210:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525309/MAPREDUCE-4210.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
-1 javadoc. The javadoc tool appears to have generated 2 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2344//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2344//console
This message is automatically generated.
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Moved] (MAPREDUCE-4219) make default container-executor.conf.dir be a path relative to the container-executor binary
[
https://issues.apache.org/jira/browse/MAPREDUCE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur moved HADOOP-8332 to MAPREDUCE-4219:
---
Component/s: (was: security)
security
Fix Version/s: (was: 2.0.0)
2.0.0
Affects Version/s: (was: 0.23.1)
0.23.1
Key: MAPREDUCE-4219 (was: HADOOP-8332)
Project: Hadoop Map/Reduce (was: Hadoop Common)
> make default container-executor.conf.dir be a path relative to the
> container-executor binary
>
>
> Key: MAPREDUCE-4219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4219
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
>Affects Versions: 0.23.1
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.0.0
>
> Attachments: HADOOP-8332.patch.txt
>
>
> Currently, container-executor binary has an absolute pathname of its
> configuration file baked in. This prevents an easy relocation of the
> configuration files when dealing with multiple Hadoop installs on the same
> node. It would be nice to at least allow for a relative path resolution
> starting from the location of the container-executor binary itself. Something
> like
> {noformat}
> ../etc/hadoop/
> {noformat}
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4210:
---
Status: Patch Available (was: Open)
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4210:
---
Status: Open (was: Patch Available)
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4210) Expose listener address for WebApp
[
https://issues.apache.org/jira/browse/MAPREDUCE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated MAPREDUCE-4210:
---
Attachment: MAPREDUCE-4210.patch
Resubmitting patch to kick the build.
> Expose listener address for WebApp
> --
>
> Key: MAPREDUCE-4210
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4210
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: webapps
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Attachments: MAPREDUCE-4210.patch, MAPREDUCE-4210.patch
>
>
> It should be possible to get the listener address from a {{WebApp}} instance.
> This will greatly simplify some of the yarn host/port manipulation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3173) MRV2 UI doesn't work properly without internet
[
https://issues.apache.org/jira/browse/MAPREDUCE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-3173:
---
Resolution: Fixed
Fix Version/s: 3.0.0
2.0.0
Status: Resolved (was: Patch Available)
Thanks Devaraj,
I put this into trunk and branch-2.
> MRV2 UI doesn't work properly without internet
> --
>
> Key: MAPREDUCE-3173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3173
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.0, 3.0.0
>Reporter: Devaraj K
>Assignee: Devaraj K
>Priority: Critical
> Fix For: 2.0.0, 3.0.0
>
> Attachments: MAPREDUCE-3173.patch, jquery-images.tgz,
> jquery-ui.min-1.8.16.js.gz, jquery.min-1.6.4.js.gz, themeswitcher-images.tgz,
> themeswitcher.js.gz
>
>
> When we try access the MRV2 UI, it is always giving the below message in the
> UI even if the java script enabled in the browser.
> {code:xml}
> This page works best with javascript enabled.
> {code}
> It is trying to download these below css/js files from internet and finally
> ending up with the above message. For loading the page also it is taking long
> time.
> {code:title=JQueryUI.java|borderStyle=solid}
> html.
>
> link(join("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/themes/";,
> getTheme(), "/jquery-ui.css")).
> link("/static/dt-1.7.5/css/jui-dt.css").
>
> script("https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js";).
>
> script("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/jquery-ui.min.js";).
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3173) MRV2 UI doesn't work properly without internet
[
https://issues.apache.org/jira/browse/MAPREDUCE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266564#comment-13266564
]
Robert Joseph Evans commented on MAPREDUCE-3173:
Thanks for the explination. I will try and integrate/test it today so I can
check it in.
> MRV2 UI doesn't work properly without internet
> --
>
> Key: MAPREDUCE-3173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3173
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.0, 3.0.0
>Reporter: Devaraj K
>Assignee: Devaraj K
>Priority: Critical
> Attachments: MAPREDUCE-3173.patch, jquery-images.tgz,
> jquery-ui.min-1.8.16.js.gz, jquery.min-1.6.4.js.gz, themeswitcher-images.tgz,
> themeswitcher.js.gz
>
>
> When we try access the MRV2 UI, it is always giving the below message in the
> UI even if the java script enabled in the browser.
> {code:xml}
> This page works best with javascript enabled.
> {code}
> It is trying to download these below css/js files from internet and finally
> ending up with the above message. For loading the page also it is taking long
> time.
> {code:title=JQueryUI.java|borderStyle=solid}
> html.
>
> link(join("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/themes/";,
> getTheme(), "/jquery-ui.css")).
> link("/static/dt-1.7.5/css/jui-dt.css").
>
> script("https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js";).
>
> script("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/jquery-ui.min.js";).
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4202) TestYarnClientProtocolProvider is broken
[ https://issues.apache.org/jira/browse/MAPREDUCE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266548#comment-13266548 ] Hudson commented on MAPREDUCE-4202: --- Integrated in Hadoop-Mapreduce-trunk #1067 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1067/]) MAPREDUCE-4202. Updating changes to just be branch-2 (Revision 1332731) MAPREDUCE-4202. TestYarnClientProtocolProvider is broken (Daryn Sharp via bobby) (Revision 1332716) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332731 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332716 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapred/LocalClientProtocolProvider.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/TestYarnClientProtocolProvider.java > TestYarnClientProtocolProvider is broken > > > Key: MAPREDUCE-4202 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4202 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: test >Affects Versions: 0.24.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Fix For: 2.0.0, 3.0.0 > > Attachments: MAPREDUCE-4202-1.patch, MAPREDUCE-4202.patch > > > The test fails because a cluster is unexpectedly created with an empty conf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4211) Error conditions (missing appid, appid not found) are masked in the RM app page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266547#comment-13266547 ] Hudson commented on MAPREDUCE-4211: --- Integrated in Hadoop-Mapreduce-trunk #1067 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1067/]) MAPREDUCE-4211. Error conditions (missing appid, appid not found) are masked in the RM app page (Jonathan Eagles via bobby) (Revision 1332701) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332701 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/AppBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java > Error conditions (missing appid, appid not found) are masked in the RM app > page > --- > > Key: MAPREDUCE-4211 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4211 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Fix For: 0.23.3, 2.0.0, 3.0.0 > > Attachments: MAPREDUCE-4211.patch, MAPREDUCE-4211.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4212) TestJobClientGetJob sometimes fails
[
https://issues.apache.org/jira/browse/MAPREDUCE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266550#comment-13266550
]
Hudson commented on MAPREDUCE-4212:
---
Integrated in Hadoop-Mapreduce-trunk #1067 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1067/])
MAPREDUCE-4212. TestJobClientGetJob sometimes fails (Daryn Sharp via
tgraves) (Revision 1332665)
Result = FAILURE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332665
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapred/TestJobClientGetJob.java
> TestJobClientGetJob sometimes fails
> ---
>
> Key: MAPREDUCE-4212
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4212
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: test
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3
>
> Attachments: MAPREDUCE-4212.patch
>
>
> {{TestJobClientGetJob}} sometimes fails because it doesn't delete the job's
> output dir prior to submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4211) Error conditions (missing appid, appid not found) are masked in the RM app page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266529#comment-13266529 ] Hudson commented on MAPREDUCE-4211: --- Integrated in Hadoop-Hdfs-trunk #1032 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1032/]) MAPREDUCE-4211. Error conditions (missing appid, appid not found) are masked in the RM app page (Jonathan Eagles via bobby) (Revision 1332701) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332701 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/AppBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java > Error conditions (missing appid, appid not found) are masked in the RM app > page > --- > > Key: MAPREDUCE-4211 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4211 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Fix For: 0.23.3, 2.0.0, 3.0.0 > > Attachments: MAPREDUCE-4211.patch, MAPREDUCE-4211.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4212) TestJobClientGetJob sometimes fails
[
https://issues.apache.org/jira/browse/MAPREDUCE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266532#comment-13266532
]
Hudson commented on MAPREDUCE-4212:
---
Integrated in Hadoop-Hdfs-trunk #1032 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1032/])
MAPREDUCE-4212. TestJobClientGetJob sometimes fails (Daryn Sharp via
tgraves) (Revision 1332665)
Result = FAILURE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332665
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapred/TestJobClientGetJob.java
> TestJobClientGetJob sometimes fails
> ---
>
> Key: MAPREDUCE-4212
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4212
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: test
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3
>
> Attachments: MAPREDUCE-4212.patch
>
>
> {{TestJobClientGetJob}} sometimes fails because it doesn't delete the job's
> output dir prior to submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4202) TestYarnClientProtocolProvider is broken
[ https://issues.apache.org/jira/browse/MAPREDUCE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266530#comment-13266530 ] Hudson commented on MAPREDUCE-4202: --- Integrated in Hadoop-Hdfs-trunk #1032 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1032/]) MAPREDUCE-4202. Updating changes to just be branch-2 (Revision 1332731) MAPREDUCE-4202. TestYarnClientProtocolProvider is broken (Daryn Sharp via bobby) (Revision 1332716) Result = FAILURE bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332731 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332716 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapred/LocalClientProtocolProvider.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/TestYarnClientProtocolProvider.java > TestYarnClientProtocolProvider is broken > > > Key: MAPREDUCE-4202 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4202 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: test >Affects Versions: 0.24.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Fix For: 2.0.0, 3.0.0 > > Attachments: MAPREDUCE-4202-1.patch, MAPREDUCE-4202.patch > > > The test fails because a cluster is unexpectedly created with an empty conf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4212) TestJobClientGetJob sometimes fails
[
https://issues.apache.org/jira/browse/MAPREDUCE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266518#comment-13266518
]
Hudson commented on MAPREDUCE-4212:
---
Integrated in Hadoop-Hdfs-0.23-Build #245 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/245/])
merge -r 1332666:1332667 from branch-2. FIXES: MAPREDUCE-4212 (Revision
1332668)
Result = SUCCESS
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332668
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapred/TestJobClientGetJob.java
> TestJobClientGetJob sometimes fails
> ---
>
> Key: MAPREDUCE-4212
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4212
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: test
>Affects Versions: 0.24.0, 0.23.3, 2.0.0
>Reporter: Daryn Sharp
>Assignee: Daryn Sharp
> Fix For: 0.23.3
>
> Attachments: MAPREDUCE-4212.patch
>
>
> {{TestJobClientGetJob}} sometimes fails because it doesn't delete the job's
> output dir prior to submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4211) Error conditions (missing appid, appid not found) are masked in the RM app page
[ https://issues.apache.org/jira/browse/MAPREDUCE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266517#comment-13266517 ] Hudson commented on MAPREDUCE-4211: --- Integrated in Hadoop-Hdfs-0.23-Build #245 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/245/]) svn merge -c 1332701 FIXES: MAPREDUCE-4211. Error conditions (missing appid, appid not found) are masked in the RM app page (Jonathan Eagles via bobby) (Revision 1332704) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332704 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/AppBlock.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java > Error conditions (missing appid, appid not found) are masked in the RM app > page > --- > > Key: MAPREDUCE-4211 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4211 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 0.23.3, 2.0.0 >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Minor > Fix For: 0.23.3, 2.0.0, 3.0.0 > > Attachments: MAPREDUCE-4211.patch, MAPREDUCE-4211.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3173) MRV2 UI doesn't work properly without internet
[
https://issues.apache.org/jira/browse/MAPREDUCE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266499#comment-13266499
]
Devaraj K commented on MAPREDUCE-3173:
--
{quote}
Like I said before I don't know how critical these are because everything looks
OK on the web page for the most part. It looks like they are trying to be
loaded by some of the css that is tied to ui-state-error, ui-widget-content,
ui-widget-header and ui-state-default, but I don't know for sure. Some of them
are also referenced directly by jquery.min-1.6.4.js.
{quote}
I couldn't notice these files because there was no effect in the page due to
these files not present. Thanks for noticing and giving clear details. I think
it is better to have all these image files. I have attached jquery-images.tgz
for all these images. Please extract it and add all the files in the directory
'hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/webapps/static/jquery/themes-1.8.16'.
{quote}
Also I am rather curious about the changes that you made to
themeswitcher.js.gz. Did you just upgrade to a newer one, or is it modified in
some way. If it is modified it is important that we document it so that when we
upgrade we can replicate those changes.
{quote}
Here I have modified the themeswitcher.js file to use the local css files
present in
'hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/webapps/static/jquery/themes-1.8.16'
instead of accessing from web.
\\
*Before the change:*
{code:title=themeswitcher.js|borderStyle=solid}http://jqueryui.com/themeroller/css/parseTheme.css.php?ffDefault=Trebuchet+MS,+Tahoma,+Verdana,+Arial,+sans-serif&fwDefault=bold&fsDefault=1.1em&cornerRadius=4px&bgColorHeader=f6a828&bgTextureHeader=12_gloss_wave.png&bgImgOpacityHeader=35&borderColorHeader=e78f08&fcHeader=ff&iconColorHeader=ff&bgColorContent=ee&bgTextureContent=03_highlight_soft.png&bgImgOpacityContent=100&borderColorContent=dd&fcContent=33&iconColorContent=22&bgColorDefault=f6f6f6&bgTextureDefault=02_glass.png&bgImgOpacityDefault=100&borderColorDefault=cc&fcDefault=1c94c4&iconColorDefault=ef8c08&bgColorHover=fdf5ce&bgTextureHover=02_glass.png&bgImgOpacityHover=100&borderColorHover=fbcb09&fcHover=c77405&iconColorHover=ef8c08&bgColorActive=ff&bgTextureActive=02_glass.png&bgImgOpacityActive=65&borderColorActive=fbd850&fcActive=eb8f00&iconColorActive=ef8c08&bgColorHighlight=ffe45c&bgTextureHighlight=03_highlight_soft.png&bgImgOpacityHighlight=75&borderColorHighlight=fed22f&fcHighlight=363636&iconColorHighlight=228ef1&bgColorError=b81900&bgTextureError=08_diagonals_thick.png&bgImgOpacityError=18&borderColorError=cd0a0a&fcError=ff&iconColorError=ffd27a&bgColorOverlay=66&bgTextureOverlay=08_diagonals_thick.png&bgImgOpacityOverlay=20&opacityOverlay=50&bgColorShadow=00&bgTextureShadow=01_flat.png&bgImgOpacityShadow=10&opacityShadow=20&thicknessShadow=5px&offsetTopShadow=-5px&offsetLeftShadow=-5px&cornerRadiusShadow=5px";>
UI lightness
{code}
\\
\\
*After the change:*
{code:title=themeswitcher.js|borderStyle=solid}
UI
lightness
{code}
The same change has been done for all the themes in themeswitcher.js.
Thanks...
> MRV2 UI doesn't work properly without internet
> --
>
> Key: MAPREDUCE-3173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3173
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.0, 3.0.0
>Reporter: Devaraj K
>Assignee: Devaraj K
>Priority: Critical
> Attachments: MAPREDUCE-3173.patch, jquery-images.tgz,
> jquery-ui.min-1.8.16.js.gz, jquery.min-1.6.4.js.gz, themeswitcher-images.tgz,
> themeswitcher.js.gz
>
>
> When we try access the MRV2 UI, it is always giving the below message in the
> UI even if the java script enabled in the browser.
> {code:xml}
> This page works best with javascript enabled.
> {code}
> It is trying to download these below css/js files from internet and finally
> ending up with the above message. For loading the page also it is taking long
> time.
> {code:title=JQueryUI.java|borderStyle=solid}
> html.
>
> link(join("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/themes/";,
> getTheme(), "/jquery-ui.css")).
> link("/static/dt-1.7.5/css/jui-dt.css").
>
> script("https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js";).
>
> script("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/jquery-ui.min.js";).
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
ht
[jira] [Commented] (MAPREDUCE-3173) MRV2 UI doesn't work properly without internet
[
https://issues.apache.org/jira/browse/MAPREDUCE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266500#comment-13266500
]
Hadoop QA commented on MAPREDUCE-3173:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525278/jquery-images.tgz
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2343//console
This message is automatically generated.
> MRV2 UI doesn't work properly without internet
> --
>
> Key: MAPREDUCE-3173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3173
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.0, 3.0.0
>Reporter: Devaraj K
>Assignee: Devaraj K
>Priority: Critical
> Attachments: MAPREDUCE-3173.patch, jquery-images.tgz,
> jquery-ui.min-1.8.16.js.gz, jquery.min-1.6.4.js.gz, themeswitcher-images.tgz,
> themeswitcher.js.gz
>
>
> When we try access the MRV2 UI, it is always giving the below message in the
> UI even if the java script enabled in the browser.
> {code:xml}
> This page works best with javascript enabled.
> {code}
> It is trying to download these below css/js files from internet and finally
> ending up with the above message. For loading the page also it is taking long
> time.
> {code:title=JQueryUI.java|borderStyle=solid}
> html.
>
> link(join("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/themes/";,
> getTheme(), "/jquery-ui.css")).
> link("/static/dt-1.7.5/css/jui-dt.css").
>
> script("https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js";).
>
> script("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/jquery-ui.min.js";).
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3173) MRV2 UI doesn't work properly without internet
[
https://issues.apache.org/jira/browse/MAPREDUCE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj K updated MAPREDUCE-3173:
-
Attachment: jquery-images.tgz
> MRV2 UI doesn't work properly without internet
> --
>
> Key: MAPREDUCE-3173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3173
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.0, 3.0.0
>Reporter: Devaraj K
>Assignee: Devaraj K
>Priority: Critical
> Attachments: MAPREDUCE-3173.patch, jquery-images.tgz,
> jquery-ui.min-1.8.16.js.gz, jquery.min-1.6.4.js.gz, themeswitcher-images.tgz,
> themeswitcher.js.gz
>
>
> When we try access the MRV2 UI, it is always giving the below message in the
> UI even if the java script enabled in the browser.
> {code:xml}
> This page works best with javascript enabled.
> {code}
> It is trying to download these below css/js files from internet and finally
> ending up with the above message. For loading the page also it is taking long
> time.
> {code:title=JQueryUI.java|borderStyle=solid}
> html.
>
> link(join("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/themes/";,
> getTheme(), "/jquery-ui.css")).
> link("/static/dt-1.7.5/css/jui-dt.css").
>
> script("https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js";).
>
> script("https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.9/jquery-ui.min.js";).
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
[ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266491#comment-13266491 ] xieguiming commented on MAPREDUCE-4124: --- By the Yarn design goal, the AM can support multiple jobs. If like this, the priority also need pass to the AM. > Job Priority is not changing > - > > Key: MAPREDUCE-4124 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 >Affects Versions: 3.0.0 >Reporter: Nishan Shetty >Priority: Critical > > 1.Submit job > 2.Change the job priority using setPriority() or CLI command ./mapred > job-set-priority > Observe that Job priority is not changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
