[jira] [Created] (MAPREDUCE-5612) Document TaskAttemptCompletionStatuses
Sandy Ryza created MAPREDUCE-5612: - Summary: Document TaskAttemptCompletionStatuses Key: MAPREDUCE-5612 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5612 Project: Hadoop Map/Reduce Issue Type: Improvement Affects Versions: 2.2.0 Reporter: Sandy Ryza Priority: Minor What's the difference between FAILED and TIPFAILED? What is OBSOLETE? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (MAPREDUCE-5613) DefaultSpeculator.statusUpdate wastes CPU for task attempt id hashing and lookups in an unused empty CHM
Gera Shegalov created MAPREDUCE-5613:
Summary: DefaultSpeculator.statusUpdate wastes CPU for task
attempt id hashing and lookups in an unused empty CHM
Key: MAPREDUCE-5613
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5613
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: applicationmaster
Reporter: Gera Shegalov
The only way pendingSpeculations is used:
{code}
// If the task is already known to be speculation-bait, don't do anything
if (pendingSpeculations.get(task) != null) {
if (pendingSpeculations.get(task).get()) {
return;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Next releases
Gang, Thinking through the next couple of releases here, appreciate f/b. # hadoop-2.2.1 I was looking through commit logs and there is a *lot* of content here (81 commits as on 11/7). Some are features/improvements and some are fixes - it's really hard to distinguish what is important and what isn't. I propose we start with a blank slate (i.e. blow away branch-2.2 and start fresh from a copy of branch-2.2.0) and then be very careful and meticulous about including only *blocker* fixes in branch-2.2. So, most of the content here comes via the next minor release (i.e. hadoop-2.3) In future, we continue to be *very* parsimonious about what gets into a patch release (major.minor.patch) - in general, these should be only *blocker* fixes or key operational issues. # hadoop-2.3 I'd like to propose the following features for YARN/MR to make it into hadoop-2.3 and punt the rest to hadoop-2.4 and beyond: * Application History Server - This is happening in a branch and is close; with it we can provide a reasonable experience for new frameworks being built on top of YARN. * Bug-fixes in RM Restart * Minimal support for long-running applications (e.g. security) via YARN-896 * RM Fail-over via ZKFC * Anything else? HDFS??? Overall, I feel like we have a decent chance of rolling hadoop-2.3 by the end of the year. Thoughts? thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
release-2.2.0 tag?
Hi, I could not find out any release tag for 2.2.0. Which branch should I use instead for latest released version? branch-2.2.0 or branch-2.2? Regards, Mohammad
[jira] [Created] (MAPREDUCE-5614) job history file name should escape queue name
Liyin Liang created MAPREDUCE-5614: -- Summary: job history file name should escape queue name Key: MAPREDUCE-5614 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5614 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 2.2.0 Reporter: Liyin Liang Assignee: Liyin Liang Our cluster's queue name contains hyphen e.g. cug-taobao. Because hyphen is the delimiter of job history file name, JobHistoryServer shows cug as the queue name. To fix this problem, we should escape queuename in job history file name. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: release-2.2.0 tag?
Hi Mohammad, IIUC, 2.2.0 is the latest released version. branch-2.2 is the latest branch under development. On Fri, Nov 8, 2013 at 11:52 AM, Mohammad Islam misla...@yahoo.com wrote: Hi, I could not find out any release tag for 2.2.0. Which branch should I use instead for latest released version? branch-2.2.0 or branch-2.2? Regards, Mohammad -- - Tsuyoshi
