http://git-wip-us.apache.org/repos/asf/hadoop/blob/19041008/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.3-alpha/RELEASENOTES.2.0.3-alpha.md ---------------------------------------------------------------------- diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.3-alpha/RELEASENOTES.2.0.3-alpha.md b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.3-alpha/RELEASENOTES.2.0.3-alpha.md index f924b91..e22f889 100644 --- a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.3-alpha/RELEASENOTES.2.0.3-alpha.md +++ b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.3-alpha/RELEASENOTES.2.0.3-alpha.md @@ -23,44 +23,42 @@ These release notes cover new developer and user-facing incompatibilities, impor --- -* [HADOOP-9147](https://issues.apache.org/jira/browse/HADOOP-9147) | *Trivial* | **Add missing fields to FIleStatus.toString** +* [HDFS-3703](https://issues.apache.org/jira/browse/HDFS-3703) | *Major* | **Decrease the datanode failure detection time** -Update FileStatus.toString to include missing fields +This jira adds a new DataNode state called "stale" at the NameNode. DataNodes are marked as stale if it does not send heartbeat message to NameNode within the timeout configured using the configuration parameter "dfs.namenode.stale.datanode.interval" in seconds (default value is 30 seconds). NameNode picks a stale datanode as the last target to read from when returning block locations for reads. + +This feature is by default turned \* off \*. To turn on the feature, set the HDFS configuration "dfs.namenode.check.stale.datanode" to true. --- -* [HADOOP-9119](https://issues.apache.org/jira/browse/HADOOP-9119) | *Minor* | **Add test to FileSystemContractBaseTest to verify integrity of overwritten files** +* [MAPREDUCE-4123](https://issues.apache.org/jira/browse/MAPREDUCE-4123) | *Critical* | **./mapred groups gives NoClassDefFoundError** -Patches adds more tests to verify overwritten and more complex operations -write-delete-overwrite. By using differently sized datasets and different data inside, these tests verify that the overwrite really did take place. While HDFS meets all these requirements directly, eventually consistent object stores may not -hence these tests. +**WARNING: No release note provided for this change.** --- -* [HADOOP-9118](https://issues.apache.org/jira/browse/HADOOP-9118) | *Trivial* | **FileSystemContractBaseTest test data for read/write isn't rigorous enough** +* [MAPREDUCE-3678](https://issues.apache.org/jira/browse/MAPREDUCE-3678) | *Major* | **The Map tasks logs should have the value of input split it processed** -Resolved as part of HADOOP-9119 -it's test data generator creates more bits in every test byte +A map-task's syslogs now carries basic info on the InputSplit it processed. --- -* [HADOOP-9106](https://issues.apache.org/jira/browse/HADOOP-9106) | *Major* | **Allow configuration of IPC connect timeout** - -This jira introduces a new configuration parameter "ipc.client.connect.timeout". This configuration defines the Hadoop RPC connection timeout in milliseconds for a client to connect to a server. For details see the description associated with this configuration in core-default.xml. +* [HDFS-4059](https://issues.apache.org/jira/browse/HDFS-4059) | *Minor* | **Add number of stale DataNodes to metrics** +This jira adds a new metric with name "StaleDataNodes" under metrics context "dfs" of type Gauge. This tracks the number of DataNodes marked as stale. A DataNode is marked stale when the heartbeat message from the DataNode is not received within the configured time ""dfs.namenode.stale.datanode.interval". ---- -* [HADOOP-9070](https://issues.apache.org/jira/browse/HADOOP-9070) | *Blocker* | **Kerberos SASL server cannot find kerberos key** - -**WARNING: No release note provided for this incompatible change.** +Please see hdfs-default.xml documentation corresponding to ""dfs.namenode.stale.datanode.interval" for more details on how to configure this feature. When this feature is not configured, this metrics would return zero. --- -* [HADOOP-8999](https://issues.apache.org/jira/browse/HADOOP-8999) | *Major* | **SASL negotiation is flawed** +* [HADOOP-8922](https://issues.apache.org/jira/browse/HADOOP-8922) | *Trivial* | **Provide alternate JSONP output for JMXJsonServlet to allow javascript in browser dashboard** -The RPC SASL negotiation now always ends with final response. If the SASL mechanism does not have a final response (GSSAPI, PLAIN), then an empty success response is sent to the client. The client will now always expect a final response to definitively know if negotiation is complete/successful. +Add a JSONP alternative outpout for /jmx HTTP interface to provide a Javascript polling ability in browsers. --- @@ -72,109 +70,100 @@ Speed up Crc32 by improving the cache hit-ratio of hadoop.util.PureJavaCrc32 --- -* [HADOOP-8922](https://issues.apache.org/jira/browse/HADOOP-8922) | *Trivial* | **Provide alternate JSONP output for JMXJsonServlet to allow javascript in browser dashboard** +* [MAPREDUCE-4637](https://issues.apache.org/jira/browse/MAPREDUCE-4637) | *Major* | **Killing an unassigned task attempt causes the job to fail** -Add a JSONP alternative outpout for /jmx HTTP interface to provide a Javascript polling ability in browsers. +Handle TaskAttempt diagnostic updates while in the NEW and UNASSIGNED states. --- -* [HADOOP-8712](https://issues.apache.org/jira/browse/HADOOP-8712) | *Minor* | **Change default hadoop.security.group.mapping** +* [HDFS-4122](https://issues.apache.org/jira/browse/HDFS-4122) | *Major* | **Cleanup HDFS logs and reduce the size of logged messages** -The default group mapping policy has been changed to JniBasedUnixGroupsNetgroupMappingWithFallback. This should maintain the same semantics as the prior default for most users. +The change from this jira changes the content of some of the log messages. No log message are removed. Only the content of the log messages is changed to reduce the size. If you have a tool that depends on the exact content of the log, please look at the patch and make appropriate updates to the tool. --- -* [HDFS-4451](https://issues.apache.org/jira/browse/HDFS-4451) | *Major* | **hdfs balancer command returns exit code 1 on success instead of 0** +* [HDFS-1331](https://issues.apache.org/jira/browse/HDFS-1331) | *Minor* | **dfs -test should work like /bin/test** -This is an incompatible change from release 2.0.2-alpha and prior releases. Balancer tool exited with exit code 1 on success. It is changed to exit with exit code 0 on success. Non 0 exit code indicates failure. +"test" will not print a warning for non-existent paths when testing for existence --- -* [HDFS-4403](https://issues.apache.org/jira/browse/HDFS-4403) | *Minor* | **DFSClient can infer checksum type when not provided by reading first byte** +* [HDFS-4080](https://issues.apache.org/jira/browse/HDFS-4080) | *Major* | **Add a separate logger for block state change logs to enable turning off those logs** -The HDFS implementation of getFileChecksum() can now operate correctly against earlier-version datanodes which do not include the checksum type information in their checksum response. The checksum type is automatically inferred by issuing a read of the first byte of each block. +Add a separate logger "BlockStateChange" for block state change logs. --- -* [HDFS-4369](https://issues.apache.org/jira/browse/HDFS-4369) | *Blocker* | **GetBlockKeysResponseProto does not handle null response** +* [HADOOP-8999](https://issues.apache.org/jira/browse/HADOOP-8999) | *Major* | **SASL negotiation is flawed** -Protobuf message GetBlockKeysResponseProto member keys is made optional from required so that null values can be passed over the wire. This is an incompatible wire protocol change and does not affect the API backward compatibility. +The RPC SASL negotiation now always ends with final response. If the SASL mechanism does not have a final response (GSSAPI, PLAIN), then an empty success response is sent to the client. The client will now always expect a final response to definitively know if negotiation is complete/successful. --- -* [HDFS-4367](https://issues.apache.org/jira/browse/HDFS-4367) | *Blocker* | **GetDataEncryptionKeyResponseProto does not handle null response** +* [MAPREDUCE-4049](https://issues.apache.org/jira/browse/MAPREDUCE-4049) | *Major* | **plugin for generic shuffle service** -Member dataEncryptionKey of the protobuf message GetDataEncryptionKeyResponseProto is made optional instead of required. This is incompatible change is not likely to affect the existing users (that are using HDFS FileSystem and other public APIs). +Allow ReduceTask loading a third party plugin for shuffle (and merge) instead of the default shuffle. --- -* [HDFS-4364](https://issues.apache.org/jira/browse/HDFS-4364) | *Blocker* | **GetLinkTargetResponseProto does not handle null path** +* [MAPREDUCE-2454](https://issues.apache.org/jira/browse/MAPREDUCE-2454) | *Minor* | **Allow external sorter plugin for MR** -Protobuf message GetLinkTargetResponseProto member targetPath is made optional from required so that null values can be passed over the wire. This is an incompatible wire protocol change and does not affect the API backward compatibility. +MAPREDUCE-4807 Allow external implementations of the sort phase in a Map task --- -* [HDFS-4362](https://issues.apache.org/jira/browse/HDFS-4362) | *Critical* | **GetDelegationTokenResponseProto does not handle null token** +* [HADOOP-9147](https://issues.apache.org/jira/browse/HADOOP-9147) | *Trivial* | **Add missing fields to FIleStatus.toString** -**WARNING: No release note provided for this incompatible change.** +Update FileStatus.toString to include missing fields --- -* [HDFS-4350](https://issues.apache.org/jira/browse/HDFS-4350) | *Major* | **Make enabling of stale marking on read and write paths independent** - -This patch makes an incompatible configuration change, as described below: -In releases 1.1.0 and other point releases 1.1.x, the configuration parameter "dfs.namenode.check.stale.datanode" could be used to turn on checking for the stale nodes. This configuration is no longer supported in release 1.2.0 onwards and is renamed as "dfs.namenode.avoid.read.stale.datanode". +* [HDFS-4362](https://issues.apache.org/jira/browse/HDFS-4362) | *Critical* | **GetDelegationTokenResponseProto does not handle null token** -How feature works and configuring this feature: -As described in HDFS-3703 release notes, datanode stale period can be configured using parameter "dfs.namenode.stale.datanode.interval" in seconds (default value is 30 seconds). NameNode can be configured to use this staleness information for reads using configuration "dfs.namenode.avoid.read.stale.datanode". When this parameter is set to true, namenode picks a stale datanode as the last target to read from when returning block locations for reads. Using staleness information for writes is as described in the releases notes of HDFS-3912. +**WARNING: No release note provided for this change.** --- -* [HDFS-4122](https://issues.apache.org/jira/browse/HDFS-4122) | *Major* | **Cleanup HDFS logs and reduce the size of logged messages** +* [HADOOP-9119](https://issues.apache.org/jira/browse/HADOOP-9119) | *Minor* | **Add test to FileSystemContractBaseTest to verify integrity of overwritten files** -The change from this jira changes the content of some of the log messages. No log message are removed. Only the content of the log messages is changed to reduce the size. If you have a tool that depends on the exact content of the log, please look at the patch and make appropriate updates to the tool. +Patches adds more tests to verify overwritten and more complex operations -write-delete-overwrite. By using differently sized datasets and different data inside, these tests verify that the overwrite really did take place. While HDFS meets all these requirements directly, eventually consistent object stores may not -hence these tests. --- -* [HDFS-4080](https://issues.apache.org/jira/browse/HDFS-4080) | *Major* | **Add a separate logger for block state change logs to enable turning off those logs** +* [HADOOP-9118](https://issues.apache.org/jira/browse/HADOOP-9118) | *Trivial* | **FileSystemContractBaseTest test data for read/write isn't rigorous enough** -Add a separate logger "BlockStateChange" for block state change logs. +Resolved as part of HADOOP-9119 -it's test data generator creates more bits in every test byte --- -* [HDFS-4059](https://issues.apache.org/jira/browse/HDFS-4059) | *Minor* | **Add number of stale DataNodes to metrics** - -This jira adds a new metric with name "StaleDataNodes" under metrics context "dfs" of type Gauge. This tracks the number of DataNodes marked as stale. A DataNode is marked stale when the heartbeat message from the DataNode is not received within the configured time ""dfs.namenode.stale.datanode.interval". - +* [HDFS-4367](https://issues.apache.org/jira/browse/HDFS-4367) | *Blocker* | **GetDataEncryptionKeyResponseProto does not handle null response** -Please see hdfs-default.xml documentation corresponding to ""dfs.namenode.stale.datanode.interval" for more details on how to configure this feature. When this feature is not configured, this metrics would return zero. +Member dataEncryptionKey of the protobuf message GetDataEncryptionKeyResponseProto is made optional instead of required. This is incompatible change is not likely to affect the existing users (that are using HDFS FileSystem and other public APIs). --- -* [HDFS-3703](https://issues.apache.org/jira/browse/HDFS-3703) | *Major* | **Decrease the datanode failure detection time** - -This jira adds a new DataNode state called "stale" at the NameNode. DataNodes are marked as stale if it does not send heartbeat message to NameNode within the timeout configured using the configuration parameter "dfs.namenode.stale.datanode.interval" in seconds (default value is 30 seconds). NameNode picks a stale datanode as the last target to read from when returning block locations for reads. +* [HDFS-4364](https://issues.apache.org/jira/browse/HDFS-4364) | *Blocker* | **GetLinkTargetResponseProto does not handle null path** -This feature is by default turned \* off \*. To turn on the feature, set the HDFS configuration "dfs.namenode.check.stale.datanode" to true. +Protobuf message GetLinkTargetResponseProto member targetPath is made optional from required so that null values can be passed over the wire. This is an incompatible wire protocol change and does not affect the API backward compatibility. --- -* [HDFS-1331](https://issues.apache.org/jira/browse/HDFS-1331) | *Minor* | **dfs -test should work like /bin/test** +* [HDFS-4369](https://issues.apache.org/jira/browse/HDFS-4369) | *Blocker* | **GetBlockKeysResponseProto does not handle null response** -"test" will not print a warning for non-existent paths when testing for existence +Protobuf message GetBlockKeysResponseProto member keys is made optional from required so that null values can be passed over the wire. This is an incompatible wire protocol change and does not affect the API backward compatibility. --- @@ -186,37 +175,48 @@ Protobuf message GetDelegationTokenRequestProto field renewer is made requried f --- -* [MAPREDUCE-4637](https://issues.apache.org/jira/browse/MAPREDUCE-4637) | *Major* | **Killing an unassigned task attempt causes the job to fail** +* [HADOOP-8712](https://issues.apache.org/jira/browse/HADOOP-8712) | *Minor* | **Change default hadoop.security.group.mapping** -Handle TaskAttempt diagnostic updates while in the NEW and UNASSIGNED states. +The default group mapping policy has been changed to JniBasedUnixGroupsNetgroupMappingWithFallback. This should maintain the same semantics as the prior default for most users. --- -* [MAPREDUCE-4123](https://issues.apache.org/jira/browse/MAPREDUCE-4123) | *Critical* | **./mapred groups gives NoClassDefFoundError** +* [HADOOP-9106](https://issues.apache.org/jira/browse/HADOOP-9106) | *Major* | **Allow configuration of IPC connect timeout** -**WARNING: No release note provided for this incompatible change.** +This jira introduces a new configuration parameter "ipc.client.connect.timeout". This configuration defines the Hadoop RPC connection timeout in milliseconds for a client to connect to a server. For details see the description associated with this configuration in core-default.xml. --- -* [MAPREDUCE-4049](https://issues.apache.org/jira/browse/MAPREDUCE-4049) | *Major* | **plugin for generic shuffle service** +* [HDFS-4403](https://issues.apache.org/jira/browse/HDFS-4403) | *Minor* | **DFSClient can infer checksum type when not provided by reading first byte** -Allow ReduceTask loading a third party plugin for shuffle (and merge) instead of the default shuffle. +The HDFS implementation of getFileChecksum() can now operate correctly against earlier-version datanodes which do not include the checksum type information in their checksum response. The checksum type is automatically inferred by issuing a read of the first byte of each block. --- -* [MAPREDUCE-3678](https://issues.apache.org/jira/browse/MAPREDUCE-3678) | *Major* | **The Map tasks logs should have the value of input split it processed** +* [HDFS-4451](https://issues.apache.org/jira/browse/HDFS-4451) | *Major* | **hdfs balancer command returns exit code 1 on success instead of 0** -A map-task's syslogs now carries basic info on the InputSplit it processed. +This is an incompatible change from release 2.0.2-alpha and prior releases. Balancer tool exited with exit code 1 on success. It is changed to exit with exit code 0 on success. Non 0 exit code indicates failure. --- -* [MAPREDUCE-2454](https://issues.apache.org/jira/browse/MAPREDUCE-2454) | *Minor* | **Allow external sorter plugin for MR** +* [HDFS-4350](https://issues.apache.org/jira/browse/HDFS-4350) | *Major* | **Make enabling of stale marking on read and write paths independent** -MAPREDUCE-4807 Allow external implementations of the sort phase in a Map task +This patch makes an incompatible configuration change, as described below: +In releases 1.1.0 and other point releases 1.1.x, the configuration parameter "dfs.namenode.check.stale.datanode" could be used to turn on checking for the stale nodes. This configuration is no longer supported in release 1.2.0 onwards and is renamed as "dfs.namenode.avoid.read.stale.datanode". + +How feature works and configuring this feature: +As described in HDFS-3703 release notes, datanode stale period can be configured using parameter "dfs.namenode.stale.datanode.interval" in seconds (default value is 30 seconds). NameNode can be configured to use this staleness information for reads using configuration "dfs.namenode.avoid.read.stale.datanode". When this parameter is set to true, namenode picks a stale datanode as the last target to read from when returning block locations for reads. Using staleness information for writes is as described in the releases notes of HDFS-3912. + + +--- + +* [HADOOP-9070](https://issues.apache.org/jira/browse/HADOOP-9070) | *Blocker* | **Kerberos SASL server cannot find kerberos key** + +**WARNING: No release note provided for this change.**
http://git-wip-us.apache.org/repos/asf/hadoop/blob/19041008/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.4-alpha/CHANGES.2.0.4-alpha.md ---------------------------------------------------------------------- diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.4-alpha/CHANGES.2.0.4-alpha.md b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.4-alpha/CHANGES.2.0.4-alpha.md index 0f1db1e..b4e6a82 100644 --- a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.4-alpha/CHANGES.2.0.4-alpha.md +++ b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.4-alpha/CHANGES.2.0.4-alpha.md @@ -20,85 +20,57 @@ ## Release 2.0.4-alpha - 2013-04-25 -### INCOMPATIBLE CHANGES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### IMPORTANT ISSUES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### NEW FEATURES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | ### IMPROVEMENTS: | JIRA | Summary | Priority | Component | Reporter | Contributor | |:---- |:---- | :--- |:---- |:---- |:---- | -| [HADOOP-9379](https://issues.apache.org/jira/browse/HADOOP-9379) | capture the ulimit info after printing the log to the console | Trivial | . | Arpit Gupta | Arpit Gupta | | [HADOOP-9374](https://issues.apache.org/jira/browse/HADOOP-9374) | Add tokens from -tokenCacheFile into UGI | Major | security | Daryn Sharp | Daryn Sharp | | [YARN-443](https://issues.apache.org/jira/browse/YARN-443) | allow OS scheduling priority of NM to be different than the containers it launches | Major | nodemanager | Thomas Graves | Thomas Graves | +| [HADOOP-9379](https://issues.apache.org/jira/browse/HADOOP-9379) | capture the ulimit info after printing the log to the console | Trivial | . | Arpit Gupta | Arpit Gupta | ### BUG FIXES: | JIRA | Summary | Priority | Component | Reporter | Contributor | |:---- |:---- | :--- |:---- |:---- |:---- | -| [HADOOP-9471](https://issues.apache.org/jira/browse/HADOOP-9471) | hadoop-client wrongfully excludes jetty-util JAR, breaking webhdfs | Major | build | Alejandro Abdelnur | Alejandro Abdelnur | -| [HADOOP-9467](https://issues.apache.org/jira/browse/HADOOP-9467) | Metrics2 record filtering (.record.filter.include/exclude) does not filter by name | Major | metrics | Chris Nauroth | Chris Nauroth | -| [HADOOP-9444](https://issues.apache.org/jira/browse/HADOOP-9444) | $var shell substitution in properties are not expanded in hadoop-policy.xml | Blocker | conf | Konstantin Boudnik | Roman Shaposhnik | +| [MAPREDUCE-3685](https://issues.apache.org/jira/browse/MAPREDUCE-3685) | There are some bugs in implementation of MergeManager | Critical | mrv2 | anty.rao | anty | +| [YARN-429](https://issues.apache.org/jira/browse/YARN-429) | capacity-scheduler config missing from yarn-test artifact | Blocker | resourcemanager | Siddharth Seth | Siddharth Seth | +| [MAPREDUCE-5023](https://issues.apache.org/jira/browse/MAPREDUCE-5023) | History Server Web Services missing Job Counters | Critical | jobhistoryserver, webapps | Kendall Thrapp | Ravi Prakash | +| [HDFS-4571](https://issues.apache.org/jira/browse/HDFS-4571) | WebHDFS should not set the service hostname on the server side | Major | webhdfs | Alejandro Abdelnur | Alejandro Abdelnur | +| [HDFS-3344](https://issues.apache.org/jira/browse/HDFS-3344) | Unreliable corrupt blocks counting in TestProcessCorruptBlocks | Major | namenode | Tsz Wo Nicholas Sze | Kihwal Lee | | [HADOOP-9406](https://issues.apache.org/jira/browse/HADOOP-9406) | hadoop-client leaks dependency on JDK tools jar | Major | build | Alejandro Abdelnur | Alejandro Abdelnur | -| [HADOOP-9405](https://issues.apache.org/jira/browse/HADOOP-9405) | TestGridmixSummary#testExecutionSummarizer is broken | Minor | test, tools | Andrew Wang | Andrew Wang | -| [HADOOP-9399](https://issues.apache.org/jira/browse/HADOOP-9399) | protoc maven plugin doesn't work on mvn 3.0.2 | Minor | build | Todd Lipcon | Konstantin Boudnik | | [HADOOP-9301](https://issues.apache.org/jira/browse/HADOOP-9301) | hadoop client servlet/jsp/jetty/tomcat JARs creating conflicts in Oozie & HttpFS | Blocker | build | Roman Shaposhnik | Alejandro Abdelnur | | [HADOOP-9299](https://issues.apache.org/jira/browse/HADOOP-9299) | kerberos name resolution is kicking in even when kerberos is not configured | Blocker | security | Roman Shaposhnik | Daryn Sharp | -| [HDFS-4649](https://issues.apache.org/jira/browse/HDFS-4649) | Webhdfs cannot list large directories | Blocker | namenode, security, webhdfs | Daryn Sharp | Daryn Sharp | -| [HDFS-4646](https://issues.apache.org/jira/browse/HDFS-4646) | createNNProxyWithClientProtocol ignores configured timeout value | Minor | namenode | Jagane Sundar | Jagane Sundar | -| [HDFS-4581](https://issues.apache.org/jira/browse/HDFS-4581) | DataNode#checkDiskError should not be called on network errors | Major | datanode | Rohit Kochar | Rohit Kochar | -| [HDFS-4576](https://issues.apache.org/jira/browse/HDFS-4576) | Webhdfs authentication issues | Major | webhdfs | Daryn Sharp | Daryn Sharp | -| [HDFS-4571](https://issues.apache.org/jira/browse/HDFS-4571) | WebHDFS should not set the service hostname on the server side | Major | webhdfs | Alejandro Abdelnur | Alejandro Abdelnur | -| [HDFS-3344](https://issues.apache.org/jira/browse/HDFS-3344) | Unreliable corrupt blocks counting in TestProcessCorruptBlocks | Major | namenode | Tsz Wo Nicholas Sze | Kihwal Lee | -| [MAPREDUCE-5117](https://issues.apache.org/jira/browse/MAPREDUCE-5117) | With security enabled HS delegation token renewer fails | Blocker | security | Roman Shaposhnik | Siddharth Seth | -| [MAPREDUCE-5094](https://issues.apache.org/jira/browse/MAPREDUCE-5094) | Disable mem monitoring by default in MiniMRYarnCluster | Major | . | Siddharth Seth | Siddharth Seth | -| [MAPREDUCE-5088](https://issues.apache.org/jira/browse/MAPREDUCE-5088) | MR Client gets an renewer token exception while Oozie is submitting a job | Blocker | . | Roman Shaposhnik | Daryn Sharp | -| [MAPREDUCE-5083](https://issues.apache.org/jira/browse/MAPREDUCE-5083) | MiniMRCluster should use a random component when creating an actual cluster | Major | mrv2 | Siddharth Seth | Siddharth Seth | | [MAPREDUCE-5053](https://issues.apache.org/jira/browse/MAPREDUCE-5053) | java.lang.InternalError from decompression codec cause reducer to fail | Major | . | Robert Parker | Robert Parker | -| [MAPREDUCE-5023](https://issues.apache.org/jira/browse/MAPREDUCE-5023) | History Server Web Services missing Job Counters | Critical | jobhistoryserver, webapps | Kendall Thrapp | Ravi Prakash | +| [HADOOP-9399](https://issues.apache.org/jira/browse/HADOOP-9399) | protoc maven plugin doesn't work on mvn 3.0.2 | Minor | build | Todd Lipcon | Konstantin Boudnik | +| [YARN-470](https://issues.apache.org/jira/browse/YARN-470) | Support a way to disable resource monitoring on the NodeManager | Major | nodemanager | Hitesh Shah | Siddharth Seth | | [MAPREDUCE-5006](https://issues.apache.org/jira/browse/MAPREDUCE-5006) | streaming tests failing | Major | contrib/streaming | Alejandro Abdelnur | Sandy Ryza | +| [HDFS-4581](https://issues.apache.org/jira/browse/HDFS-4581) | DataNode#checkDiskError should not be called on network errors | Major | datanode | Rohit Kochar | Rohit Kochar | | [MAPREDUCE-4549](https://issues.apache.org/jira/browse/MAPREDUCE-4549) | Distributed cache conflicts breaks backwards compatability | Blocker | mrv2 | Robert Joseph Evans | Robert Joseph Evans | -| [MAPREDUCE-3685](https://issues.apache.org/jira/browse/MAPREDUCE-3685) | There are some bugs in implementation of MergeManager | Critical | mrv2 | anty.rao | anty | -| [YARN-470](https://issues.apache.org/jira/browse/YARN-470) | Support a way to disable resource monitoring on the NodeManager | Major | nodemanager | Hitesh Shah | Siddharth Seth | +| [HADOOP-9444](https://issues.apache.org/jira/browse/HADOOP-9444) | $var shell substitution in properties are not expanded in hadoop-policy.xml | Blocker | conf | Konstantin Boudnik | Roman Shaposhnik | +| [HADOOP-9405](https://issues.apache.org/jira/browse/HADOOP-9405) | TestGridmixSummary#testExecutionSummarizer is broken | Minor | test, tools | Andrew Wang | Andrew Wang | | [YARN-449](https://issues.apache.org/jira/browse/YARN-449) | HBase test failures when running against Hadoop 2 | Blocker | . | Siddharth Seth | | -| [YARN-429](https://issues.apache.org/jira/browse/YARN-429) | capacity-scheduler config missing from yarn-test artifact | Blocker | resourcemanager | Siddharth Seth | Siddharth Seth | - - -### TESTS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | +| [HDFS-4649](https://issues.apache.org/jira/browse/HDFS-4649) | Webhdfs cannot list large directories | Blocker | namenode, security, webhdfs | Daryn Sharp | Daryn Sharp | +| [MAPREDUCE-5117](https://issues.apache.org/jira/browse/MAPREDUCE-5117) | With security enabled HS delegation token renewer fails | Blocker | security | Roman Shaposhnik | Siddharth Seth | +| [MAPREDUCE-5088](https://issues.apache.org/jira/browse/MAPREDUCE-5088) | MR Client gets an renewer token exception while Oozie is submitting a job | Blocker | . | Roman Shaposhnik | Daryn Sharp | +| [MAPREDUCE-5083](https://issues.apache.org/jira/browse/MAPREDUCE-5083) | MiniMRCluster should use a random component when creating an actual cluster | Major | mrv2 | Siddharth Seth | Siddharth Seth | +| [HDFS-4646](https://issues.apache.org/jira/browse/HDFS-4646) | createNNProxyWithClientProtocol ignores configured timeout value | Minor | namenode | Jagane Sundar | Jagane Sundar | +| [HADOOP-9467](https://issues.apache.org/jira/browse/HADOOP-9467) | Metrics2 record filtering (.record.filter.include/exclude) does not filter by name | Major | metrics | Chris Nauroth | Chris Nauroth | +| [HADOOP-9471](https://issues.apache.org/jira/browse/HADOOP-9471) | hadoop-client wrongfully excludes jetty-util JAR, breaking webhdfs | Major | build | Alejandro Abdelnur | Alejandro Abdelnur | +| [MAPREDUCE-5094](https://issues.apache.org/jira/browse/MAPREDUCE-5094) | Disable mem monitoring by default in MiniMRYarnCluster | Major | . | Siddharth Seth | Siddharth Seth | +| [HDFS-4576](https://issues.apache.org/jira/browse/HDFS-4576) | Webhdfs authentication issues | Major | webhdfs | Daryn Sharp | Daryn Sharp | ### SUB-TASKS: | JIRA | Summary | Priority | Component | Reporter | Contributor | |:---- |:---- | :--- |:---- |:---- |:---- | -| [HDFS-4577](https://issues.apache.org/jira/browse/HDFS-4577) | Webhdfs operations should declare if authentication is required | Major | webhdfs | Daryn Sharp | Daryn Sharp | -| [HDFS-4567](https://issues.apache.org/jira/browse/HDFS-4567) | Webhdfs does not need a token for token operations | Major | webhdfs | Daryn Sharp | Daryn Sharp | -| [HDFS-4566](https://issues.apache.org/jira/browse/HDFS-4566) | Webdhfs token cancelation should use authentication | Major | webhdfs | Daryn Sharp | Daryn Sharp | | [HDFS-4560](https://issues.apache.org/jira/browse/HDFS-4560) | Webhdfs cannot use tokens obtained by another user | Major | webhdfs | Daryn Sharp | Daryn Sharp | +| [HDFS-4566](https://issues.apache.org/jira/browse/HDFS-4566) | Webdhfs token cancelation should use authentication | Major | webhdfs | Daryn Sharp | Daryn Sharp | +| [HDFS-4567](https://issues.apache.org/jira/browse/HDFS-4567) | Webhdfs does not need a token for token operations | Major | webhdfs | Daryn Sharp | Daryn Sharp | +| [HDFS-4577](https://issues.apache.org/jira/browse/HDFS-4577) | Webhdfs operations should declare if authentication is required | Major | webhdfs | Daryn Sharp | Daryn Sharp | | [HDFS-4548](https://issues.apache.org/jira/browse/HDFS-4548) | Webhdfs doesn't renegotiate SPNEGO token | Blocker | . | Daryn Sharp | Daryn Sharp | -### OTHER: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - http://git-wip-us.apache.org/repos/asf/hadoop/blob/19041008/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.5-alpha/CHANGES.2.0.5-alpha.md ---------------------------------------------------------------------- diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.5-alpha/CHANGES.2.0.5-alpha.md b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.5-alpha/CHANGES.2.0.5-alpha.md index 2aab255..0ca6e8a 100644 --- a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.5-alpha/CHANGES.2.0.5-alpha.md +++ b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.5-alpha/CHANGES.2.0.5-alpha.md @@ -20,56 +20,16 @@ ## Release 2.0.5-alpha - 2013-06-06 -### INCOMPATIBLE CHANGES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### IMPORTANT ISSUES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### NEW FEATURES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### IMPROVEMENTS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | ### BUG FIXES: | JIRA | Summary | Priority | Component | Reporter | Contributor | |:---- |:---- | :--- |:---- |:---- |:---- | -| [HADOOP-9614](https://issues.apache.org/jira/browse/HADOOP-9614) | smart-test-patch.sh hangs for new version of patch (2.7.1) | Major | . | Ravi Prakash | Ravi Prakash | -| [HADOOP-9407](https://issues.apache.org/jira/browse/HADOOP-9407) | commons-daemon 1.0.3 dependency has bad group id causing build issues | Major | build | Sangjin Lee | Sangjin Lee | -| [HADOOP-8419](https://issues.apache.org/jira/browse/HADOOP-8419) | GzipCodec NPE upon reset with IBM JDK | Major | io | Luke Lu | Yu Li | | [HDFS-4482](https://issues.apache.org/jira/browse/HDFS-4482) | ReplicationMonitor thread can exit with NPE due to the race between delete and replication of same file. | Blocker | namenode | Uma Maheswara Rao G | Uma Maheswara Rao G | +| [HADOOP-8419](https://issues.apache.org/jira/browse/HADOOP-8419) | GzipCodec NPE upon reset with IBM JDK | Major | io | Luke Lu | Yu Li | | [MAPREDUCE-5240](https://issues.apache.org/jira/browse/MAPREDUCE-5240) | inside of FileOutputCommitter the initialized Credentials cache appears to be empty | Blocker | mrv2 | Roman Shaposhnik | Vinod Kumar Vavilapalli | - - -### TESTS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### SUB-TASKS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### OTHER: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | +| [HADOOP-9407](https://issues.apache.org/jira/browse/HADOOP-9407) | commons-daemon 1.0.3 dependency has bad group id causing build issues | Major | build | Sangjin Lee | Sangjin Lee | +| [HADOOP-9614](https://issues.apache.org/jira/browse/HADOOP-9614) | smart-test-patch.sh hangs for new version of patch (2.7.1) | Major | . | Ravi Prakash | Ravi Prakash | http://git-wip-us.apache.org/repos/asf/hadoop/blob/19041008/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.6-alpha/CHANGES.2.0.6-alpha.md ---------------------------------------------------------------------- diff --git a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.6-alpha/CHANGES.2.0.6-alpha.md b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.6-alpha/CHANGES.2.0.6-alpha.md index 2383d4a..c27d9a4 100644 --- a/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.6-alpha/CHANGES.2.0.6-alpha.md +++ b/hadoop-common-project/hadoop-common/src/site/markdown/release/2.0.6-alpha/CHANGES.2.0.6-alpha.md @@ -20,28 +20,6 @@ ## Release 2.0.6-alpha - 2013-08-22 -### INCOMPATIBLE CHANGES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### IMPORTANT ISSUES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### NEW FEATURES: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### IMPROVEMENTS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | ### BUG FIXES: @@ -51,21 +29,3 @@ | [YARN-854](https://issues.apache.org/jira/browse/YARN-854) | App submission fails on secure deploy | Blocker | . | Ramya Sunil | Omkar Vinit Joshi | -### TESTS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### SUB-TASKS: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - -### OTHER: - -| JIRA | Summary | Priority | Component | Reporter | Contributor | -|:---- |:---- | :--- |:---- |:---- |:---- | - - --------------------------------------------------------------------- To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-commits-h...@hadoop.apache.org
