accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1575035 - in /accumulo/site/trunk/content: downloads/index.mdtext release_notes/1.5.1.mdtext release_notes/release_notes.mdtext
Date Thu, 06 Mar 2014 20:37:32 GMT
Author: elserj
Date: Thu Mar  6 20:37:31 2014
New Revision: 1575035

URL: http://svn.apache.org/r1575035
Log:
ACCUMULO-2394 Add some more changes to the release notes for 1.5.1

Added:
    accumulo/site/trunk/content/release_notes/1.5.1.mdtext
      - copied, changed from r1575030, accumulo/site/trunk/content/release_notes/release_notes.mdtext
Removed:
    accumulo/site/trunk/content/release_notes/release_notes.mdtext
Modified:
    accumulo/site/trunk/content/downloads/index.mdtext

Modified: accumulo/site/trunk/content/downloads/index.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/downloads/index.mdtext?rev=1575035&r1=1575034&r2=1575035&view=diff
==============================================================================
--- accumulo/site/trunk/content/downloads/index.mdtext (original)
+++ accumulo/site/trunk/content/downloads/index.mdtext Thu Mar  6 20:37:31 2014
@@ -17,7 +17,7 @@ Notice:    Licensed to the Apache Softwa
            under the License.
 
 ## 1.5.1 (latest)
-The most recent Apache Accumulo™ release is version 1.5.1.  See the [CHANGES][21].
 
+The most recent Apache Accumulo™ release is version 1.5.1.  See the [release notes][33]
and [CHANGES][21].  
 Be sure to verify your downloads by these [procedures][1] using these [KEYS][2].  
 For convenience, [MD5][22] and [SHA1][23] hashes are also available.
 
@@ -89,4 +89,5 @@ Be sure to verify your downloads by thes
 [29]: http://www.apache.org/dist/accumulo/1.5.1/accumulo-1.5.1-native.deb.asc
 [30]: http://www.apache.org/dist/accumulo/1.5.1/accumulo-1.5.1-test.deb.asc
 [31]: http://www.apache.org/dist/accumulo/1.5.1/accumulo-1.5.1-src.tar.gz.asc
-[32]: /1.5/examples
\ No newline at end of file
+[32]: /1.5/examples
+[33]: /release_notes/1.5.1.html

Copied: accumulo/site/trunk/content/release_notes/1.5.1.mdtext (from r1575030, accumulo/site/trunk/content/release_notes/release_notes.mdtext)
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.5.1.mdtext?p2=accumulo/site/trunk/content/release_notes/1.5.1.mdtext&p1=accumulo/site/trunk/content/release_notes/release_notes.mdtext&r1=1575030&r2=1575035&rev=1575035&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/release_notes.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.5.1.mdtext Thu Mar  6 20:37:31 2014
@@ -16,51 +16,128 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-## Accumulo 1.5.1 Release Notes (Work in progress)
 
+Apache Accumulo 1.5.1 is a maintenance release on the 1.5 version branch.
+This release is contains changes from over 200 issues, comprised of bug fixes
+(client side and server side), new test cases, updated Hadoop support, and more.
+As this is a maintenance release, Apache Accumulo 1.5.1 has no client API 
+incompatibilities over Apache Accumulo 1.5.0 and requires no manual upgrade 
+process. Users of 1.5.0 are strongly encouraged to update as soon as possible 
+to benefit from the improvements.
 
-### Notable Improvements
 
-Accumulo client code creates background threads that users can not stop.  This
-causes problems when using Accumulo with Tomcat or JBoss.  [ACCUMULO-2128][3]
-introduced the static utility org.apache.accumulo.core.util.CleanUp to clean
-these threads up.
+## Notable Improvements
 
-If IPv6 is enabled on nodes but not in use on the network, then Accumulo may
-have issues communicating with itself.  [ACCUMULO-2262][4] adds java
-configuration to startup scripts to prefer IPv4.
+While new features are typically not added in a bug-fix release as 1.5.1, the
+community does create a variety of improvements that are API compatible. Contained
+here are some of the more notable improvements.
 
-[ACCUMULO-1933][7] allows lower case memory units in Accumulo configuration.
+### PermGen Leak from Client API
 
-[ACCUMULO-2360][14] allows users to configure the maximum frame size an
-Accumulo server will read.  This prevents non Accumulo client from connecting
-and causing memory exhaustion.
+Accumulo's client code creates background threads that users presently cannot 
+stop through the API. This is quick to cause problems when invoking the Accumulo
+API in application containers such as Apache Tomcat or JBoss and repeatedly 
+redeploying an application. [ACCUMULO-2128][3] introduces a static utility, 
+org.apache.accumulo.core.util.CleanUp, that users can invoke as part of a 
+teardown hook in their container that will stop these threads and avoid 
+the eventual OutOfMemoryError "PermGen space".
 
-The following documentation updates were made : [ACCUMULO-2127][17],
-[ACCUMULO-1956][18], and [ACCUMULO-1428][19].
+### Prefer IPv4 when starting Accumulo processes
 
-### Notable Bug Fixes
+While Hadoop [does not support IPv6 networks][28], attempting to run on a 
+system that does not have IPv6 completely disabled can cause strange failures.
+[ACCUMULO-2262][4] invokes the JVM-provided configuration parameter at process
+startup to prefer IPv4 over IPv6.
 
- * [ACCUMULO-1800][5] fixed deletes made via the Proxy.
- * [ACCUMULO-1994][6] fixed ranges in the Proxy.
- * [ACCUMULO-2234][8] fixed offline map reduce over non default HDFS location
- * [ACCUMULO-1615][15] fixed service accumulo-tserver stop
- * [ACCUMULO-1876][16] fixed issues with ivy
+### Memory units in configuration
 
-Some important internal bugs were fixed in Accumulo that should be considered
-when deciding to upgrade. These bugs are : [ACCUMULO-2057][9],
-[ACCUMULO-2261][10], [ACCUMULO-2037][11], [ACCUMULO-1821][12],
-[ACCUMULO-1572][13], [ACCUMULO-2078][20], [ACCUMULO-1985][21],
-[ACCUMULO-1999][22],[ACCUMULO-2065][23], and [ACCUMULO-1630][24]. 
+In previous versions, units of memory had to be provided as upper-case (e.g. '2G', not '2g').
+Additionally, a non-intuitive error was printed when a lower-case unit was provided.
+[ACCUMULO-1933][7] allows lower-case memory units in all Accumulo configurations.
 
+### Thrift maximum frame size
 
-### Known Issues
+Apache Thrift is used as the internal RPC service. [ACCUMULO-2360][14] allows 
+users to configure the maximum frame size an Accumulo server will read. This 
+prevents non Accumulo client from connecting and causing memory exhaustion.
 
-When using Accumulo 1.5 and Hadoop 2, Accumulo will call hsync() on hdfs.
-Calling hsync improves durability by ensuring data is on disk, however calling
-it frequently slows writes. A work around is to increase
-tserver.mutation.queue.max.  See [ACCUMULO-1905 comment][1], [ACCUMULO-1950][2], and
-the new tserver.mutation.queue.max documentation for more information.
+
+## Notable Bug Fixes
+
+As with any Apache Accumulo release, we have numerous bug fixes that have been fixed. Most
+are very subtle and won't affect the common user; however, some notable bugs were resolved

+as a part of 1.5.1 that are rather common.
+
+### Failure of ZooKeeper server in quorum kills connected Accumulo services
+
+Apache ZooKeeper provides a number of wonderful features that Accumulo uses to accomplish
+a variety of tasks, most notably a distributed locking service. Typically, multiple ZooKeeper
+servers are run to provide resilience against a certain number of node failures. [ACCUMULO-1572][13]
+resolves an issue where Accumulo processes would kill themselves when the ZooKeeper server
they
+were communicating with died instead of failing over to another ZooKeeper server in the quorum.
+
+### Monitor table state isn't updated
+
+The Accumulo Monitor contains a column for the state of each table in the Accumulo instance.
+The previous resolution was to restart the Monitor process when it got in this state.
+[ACCUMULO-1920][25] resolves an issue where the Monitor would not see updates from ZooKeeper.
+
+### Two locations for the same extent
+
+The !METADATA table is the brains behind the data storage for each table, tracking information
+like which files comprise a Tablet, and which TabletServers are hosting which Tablets. [ACCUMULO-2057][9]
+fixes an issue where the !METADATA table contained multiple locations (hosting server) for
+a single Tablet.
+
+### Deadlock on !METADATA tablet unload
+
+Tablets are unloaded, typically, when a shutdown request is issued. [ACCUMULO-1143][27] resolves
+a potential deadlock issue when a merging-minor compaction is issued to flush in-memory data
+to disk before unloading a Tablet.
+
+### Other notable fixes
+
+ * [ACCUMULO-1800][5] Fixed deletes made via the Proxy.
+ * [ACCUMULO-1994][6] Fixed ranges in the Proxy.
+ * [ACCUMULO-2234][8] Fixed offline map reduce over non default HDFS location.
+ * [ACCUMULO-1615][15] Fixed `service accumulo-tserver stop`.
+ * [ACCUMULO-1876][16] Fixed issues depending on Accumulo using Apache Ivy.
+ * [ACCUMULO-2261][10] Duplicate locations for a Tablet.
+ * [ACCUMULO-2037][11] Tablets assigned to previous location.
+ * [ACCUMULO-1821][12] Avoid recovery on recovering Tablets.
+ * [ACCUMULO-2078][20] Incorrectly computed ACCUMULO_LOG_HOST in example configurations.
+ * [ACCUMULO-1985][21] Configuration to bind Monitor on all network interfaces.
+ * [ACCUMULO-1999][22] Allow '0' to signify random port for the Master.
+ * [ACCUMULO-1630][24] Fixed GC to interpret any IP/hostname.
+
+
+## Known Issues
+
+When using Accumulo 1.5 and Hadoop 2, Accumulo will call hsync() on HDFS.
+Calling hsync improves durability by ensuring data is on disk (where other older 
+Hadoop versions might lose data in the face of power failure); however, calling
+hsync frequently does noticably slow writes. A simple work around is to increase 
+the value of the tserver.mutation.queue.max configuration parameter via accumulo-site.xml.
+
+A value of "4M" is a better recommendation, and memory consumption will increase by
+the number of concurrent writers to that TabletServer. For example, a value of 4M with
+50 concurrent writers would equate to approximately 200M of Java heap being used for
+mutation queues.
+
+For more information, see [ACCUMULO-1950][2] and [this comment][1].
+
+## Documentation
+
+The following documentation updates were made: 
+
+ * [ACCUMULO-1956][18]
+ * [ACCUMULO-1428][19]
+ * [ACCUMULO-1687][29]
+ * [ACCUMULO-2141][30]
+ * [ACCUMULO-1946][31]
+ * [ACCUMULO-2223][32]
+ * [ACCUMULO-2226][33]
+ * [ACCUMULO-1470][34]
 
 
 [1]: https://issues.apache.org/jira/browse/ACCUMULO-1905?focusedCommentId=13915208&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13915208
@@ -86,4 +163,13 @@ the new tserver.mutation.queue.max docum
 [21]: https://issues.apache.org/jira/browse/ACCUMULO-1985
 [22]: https://issues.apache.org/jira/browse/ACCUMULO-1999
 [23]: https://issues.apache.org/jira/browse/ACCUMULO-2065
-[24]: https://issues.apache.org/jira/browse/ACCUMULO-1630
\ No newline at end of file
+[24]: https://issues.apache.org/jira/browse/ACCUMULO-1630
+[25]: https://issues.apache.org/jira/browse/ACCUMULO-1920
+[27]: https://issues.apache.org/jira/browse/ACCUMULO-1143
+[28]: http://wiki.apache.org/hadoop/HadoopIPv6
+[29]: https://issues.apache.org/jira/browse/ACCUMULO-1687
+[30]: https://issues.apache.org/jira/browse/ACCUMULO-2141
+[31]: https://issues.apache.org/jira/browse/ACCUMULO-1946
+[32]: https://issues.apache.org/jira/browse/ACCUMULO-2223
+[33]: https://issues.apache.org/jira/browse/ACCUMULO-2226
+[34]: https://issues.apache.org/jira/browse/ACCUMULO-1470



Mime
View raw message