Dear all,
0.20.204.0 will hopefully finish the release process soon, and it is time to
start talking about 205. As Owen mentioned,
I would like to volunteer as the Release Manager for 0.20.2xx, if that is
acceptable to the community. I would also like
to suggest some process changes.
By continuing to provide sustaining releases of 0.20-security, the community
helps production users until later versions (v22
and v23) reach stability. At the same time, we certainly do not wish
0.20-security to be viewed as a "trunk"; it is important
that all patches go in trunk first, and only patches of manageable risk and
high value to production users, should go into
the sustaining releases.
The goal of the following is to assure adequate community participation in
the release process, rather than just a bunch of
Jiras followed by last-minute debate in a Vote thread :-)
It seems that the default assumption has been that any patch committed to
0.20-security would go into the next sustaining
release. In theory, contributors and committers have the opportunity to
comment in the Jiras if they disagreed. However,
in practice most people don't follow Jiras for patches other than trunk, and
the number of such patches can add up.
So, to start discussion for the 205 release, I propose the following:
1. Let us look at the list of patches applied to 0.20-security so far, since
204 (see attached document).
2. Contributors and production users who want the various patches should
speak up for them, providing information such as
- Jira number and title
- Value to production users
- Risk and Testability
3. If there are other patches desired in 205 that have not yet been
committed to 0.20-security, potential contributors should
also speak up, providing the same information, and opening new Jiras if
necessary.
Hopefully over the coming week or so we can share all the inputs, and people
will have time to review them and comment.
After the 205 release, I hope we can discuss potential content for 206 in
advance. Perhaps we can also circulate some
improvements to the Sustaining Release process currently documented in the
wiki.
Thoughts and feedback welcome,
thanks,
--Matt
Release 0.20.205.0 - unreleased
NEW FEATURES
HDFS-2202. Add a new DFSAdmin command to set balancer bandwidth of
datanodes without restarting. (Eric Payne via szetszwo)
BUG FIXES
MAPREDUCE-2324. Removed usage of broken
ResourceEstimator.getEstimatedReduceInputSize to check against usable
disk-space on TaskTracker. (Robert Evans via acmurthy)
MAPREDUCE-2729. Ensure jobs with reduces which can't be launched due to
slow-start do not count for user-limits. (Sherry Chen via acmurthy)
HADOOP-6833. IPC leaks call parameters when exceptions thrown.
(Todd Lipcon via eli)
HADOOP-7400. Fix HdfsProxyTests fails when the -Dtest.build.dir
and -Dbuild.test is set a dir other than build dir (gkesavan).
MAPREDUCE-2650. back-port MAPREDUCE-2238 to 0.20-security.
(Sherry Chen via mahadev)
HDFS-2053. Bug in INodeDirectory#computeContentSummary warning
(Michael Noll via eli)
HDFS-2117. DiskChecker#mkdirsWithExistsAndPermissionCheck may
return true even when the dir is not created. (eli)
MAPREDUCE-2489. Jobsplits with random hostnames can make the
queue unusable. (Jeffrey Naisbitt via mahadev)
HDFS-2190. NN fails to start if it encounters an empty or malformed fstime
file. (atm)
HDFS-2259. DN web-UI doesn't work with paths that contain html. (eli)
HDFS-561. Fix write pipeline READ_TIMEOUT.
(Todd Lipcon via dhruba)
HDFS-606. Fix ConcurrentModificationException in invalidateCorruptReplicas.
(Todd Lipcon via dhruba)
HDFS-1118. Fix socketleak on DFSClient.
(Zheng Shao via dhruba)
IMPROVEMENTS
MAPREDUCE-2187. Reporter sends progress during sort/merge. (Anupam Seth via
acmurthy)
MAPREDUCE-2705. Implements launch of multiple tasks concurrently.
(Thomas Graves via ddas)
MAPREDUCE-7343. Make the number of warnings accepted by test-patch
configurable to limit false positives. (Thomas Graves via cdouglas)
HDFS-1836. Thousand of CLOSE_WAIT socket. Contributed by Todd Lipcon,
ported to security branch by Bharath Mundlapudi. (via mattf)
HADOOP-7432. Back-port HADOOP-7110 to 0.20-security: Implement chmod
in NativeIO library. (Sherry Chen via mattf)
HADOOP-7314. Add support for throwing UnknownHostException when a host
doesn't resolve. Needed for MAPREDUCE-2489. (Jeffrey Naisbitt via mattf)
MAPREDUCE-2494. Make the distributed cache delete entires using LRU
priority (Robert Joseph Evans via mahadev)
HADOOP-6889. Make RPC to have an option to timeout - backport to
0.20-security. (John George and Ravi Prakash via mattf)
MAPREDUCE-2780. Use a utility method to set service in token.
(Daryn Sharp via jitendra)
HADOOP-7472. RPC client should deal with IP address change.
(Kihwal Lee via suresh)
MAPREDUCE-2489. Jobsplits with random hostnames can make the queue unusable
(Jeffrey Naisbit via mahadev)
MAPREDUCE-2852. Jira for YDH bug 2854624. (Kihwal Lee via eli)
HDFS-1210. DFSClient should log exception when block recovery fails.
(Todd Lipcon via dhruba)
HDFS-1211. Block receiver should not log "rewind" packets at INFO level.
(Todd Lipcon)
HDFS-1164. TestHdfsProxy is failing. (Todd Lipcon)
