[jira] [Resolved] (MAPREDUCE-4168) Support multiple network interfaces
[ https://issues.apache.org/jira/browse/MAPREDUCE-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved MAPREDUCE-4168. - Resolution: Not a Problem It is expected that an appropriate client config is used to submit jobs. Don't have to support submitting jobs with the RM config. Support multiple network interfaces --- Key: MAPREDUCE-4168 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4168 Project: Hadoop Map/Reduce Issue Type: New Feature Reporter: Tom White Assignee: Karthik Kambatla Umbrella jira to track the MapReduce side of HADOOP-8198. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MAPREDUCE-4150) Versioning and rolling upgrades for MR2
[ https://issues.apache.org/jira/browse/MAPREDUCE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned MAPREDUCE-4150: --- Assignee: (was: Karthik Kambatla) Versioning and rolling upgrades for MR2 --- Key: MAPREDUCE-4150 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4150 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.1 Reporter: Ahmed Radwan It doesn't seem that Yarn components, for example the ResourceManager or NodeManager, do build/package version checking before trying to communicate with each other. The objective of this ticket is to support the following requirements / use cases: - New versions can be marked incompatible with old versions, and services should be prevented from communicating with each other in such case. This will avoid non-deterministic behavior/problems resulting from incompatible components trying to communicate with each other. - Permitting a policy for running different - but compatible - versions on the same cluster (for example, in a rolling upgrade scenario). See HDFS-2983 for the corresponding HDFS implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MAPREDUCE-5384) Races in DelegationTokenRenewal
[ https://issues.apache.org/jira/browse/MAPREDUCE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned MAPREDUCE-5384: --- Assignee: (was: Karthik Kambatla) Races in DelegationTokenRenewal --- Key: MAPREDUCE-5384 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5384 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 1.2.0, 1.1.2, 1.2.1 Reporter: Karthik Kambatla Attachments: mr-5384-0.patch, mr-5384-1.patch, mr-5384-2.patch There are a couple of races in DelegationTokenRenewal. One of them was addressed by MAPREDUCE-4860, which introduced a deadlock while fixing this race. Opening a new JIRA per discussion in MAPREDUCE-5364, since MAPREDUCE-4860 is already shipped in a release. Races to fix: # TimerTask#cancel() disallows future invocations of run(), but doesn't abort an already scheduled/started run(). # In the context of DelegationTokenRenewal, RenewalTimerTask#cancel() only cancels that TimerTask instance. However, it has no effect on any other TimerTasks created for that token. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6204) TestJobCounters should use new properties instead JobConf.MAPRED_TASK_JAVA_OPTS
[ https://issues.apache.org/jira/browse/MAPREDUCE-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14259797#comment-14259797 ] sam liu commented on MAPREDUCE-6204: For many deprecated properties, hadoop code always set its value to its new version of property. Absolutely, this solution is clear and won't bring any misunderstanding on the conception of 'deprecation'. However, for the deprecated property mapred.child.java.opts, hadoop uses a different method: it won't update the value of its new versions MRJobConfig.MAP_JAVA_OPTS and MRJobConfig.REDUCE_JAVA_OPTS. Yes, finally hadoop will set a correct value on the classpath, however the program like MapReduce could not get correct value of MRJobConfig.MAP_JAVA_OPTS and MRJobConfig.REDUCE_JAVA_OPTS: it definately bring confusing to the users. Furthermore, this ut will fail without this patch on ppc64 platform, but could pass on the same env with this patch. Actually the root cause is the insuffcient completion of the deprecation of property mapred.child.java.opts. We could not say this patch is useless or simply pass the buck to 'env issue': if this is an env issue, this ut should fail on the ppc64 platform either with the deprecated property mapred.child.java.opts or with the new version of properties MRJobConfig.MAP_JAVA_OPTS and MRJobConfig.REDUCE_JAVA_OPTS. Therefore this patch is necessary and could remedy the insuffcient completion of the deprecation of property mapred.child.java.opts. TestJobCounters should use new properties instead JobConf.MAPRED_TASK_JAVA_OPTS --- Key: MAPREDUCE-6204 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6204 Project: Hadoop Map/Reduce Issue Type: Test Components: test Affects Versions: 2.6.0 Reporter: sam liu Assignee: sam liu Priority: Minor Attachments: MAPREDUCE-6204-1.patch, MAPREDUCE-6204.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MAPREDUCE-4168) Support multiple network interfaces
[ https://issues.apache.org/jira/browse/MAPREDUCE-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reopened MAPREDUCE-4168: - I'm re-opening this issue based upon the resolution it was closed. It has not and never will be acceptable to require different configs on different nodes for the software stack. (Hardware, specifically file system and memory configuration is obviously a different problem.) Making this a requirement to fix such a ho-hum issue greatly increases operational overhead. Support multiple network interfaces --- Key: MAPREDUCE-4168 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4168 Project: Hadoop Map/Reduce Issue Type: New Feature Reporter: Tom White Assignee: Karthik Kambatla Umbrella jira to track the MapReduce side of HADOOP-8198. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
