Author: elserj
Date: Mon Feb 16 22:13:56 2015
New Revision: 1660226
URL: http://svn.apache.org/r1660226
Log:
First pass of notable bugs done
Modified:
accumulo/site/trunk/content/release_notes/1.6.2.mdtext
Modified: accumulo/site/trunk/content/release_notes/1.6.2.mdtext
URL:
http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.6.2.mdtext?rev=1660226&r1=1660225&r2=1660226&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.6.2.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.6.2.mdtext Mon Feb 16 22:13:56
2015
@@ -89,6 +89,35 @@ data stored in Accumulo using the broken
// ...
}
+### Reduce MiniAccumuloCluster failures due to random port allocations
+
+`MiniAccumuloCluster` has had issues where it fails to properly start due to
the way it attempts to choose
+a random, unbound port on the local machine to start the ZooKeeper and
Accumulo processes. Improvements have
+been made, including retry logic, to withstand a few failed port choices. The
changes made by [ACCUMULO-3233][12]
+and the related issues should eliminate sporadic failures users of
`MiniAccumuloCluster` might have observed.
+
+### Tracer doesn't handle trace table state transition
+
+The Tracer is an optional Accumulo server process that serializes Spans,
elements of a distributed trace,
+to the trace table for later inspection and correlation with other Spans. By
default, the Tracer writes
+to a "trace" table. In earlier versions of Accumulo, if this table was put
offline, the Tracer would fail
+to write new Spans to the table when it came back online. [ACCUMULO-3351][13]
ensures that the Tracer process
+will resume writing Spans to the trace table when it transitions to online
after being offline.
+
+### Tablet not major compacting
+
+It was noticed that a system performing many bulk imports, there was a tablet
with hundreds of files which
+was not major compacting nor was scheduled to be major compacted.
[ACCUMULO-3462][14] identified as fix
+server-side which would prevent this from happening in the future.
+
+### YARN job submission fails with Hadoop-2.6.0
+
+Hadoop 2.6.0 introduced a new component, the TimelineServer, which is a
centralized metrics service designed
+for other Hadoop components to leverage. MapReduce jobs submitted via
`accumulo` and `tool.sh` failed to
+run the job because it attempted to contact the TimelineServer and Accumulo
was missing a dependency on
+the classpath to communicate with the TimelineServer. [ACCUMULO-3230][15]
updates the classpath in the example
+configuration files to include the necessary dependencies for the
TimelineServer to ensure that YARN job
+submission operates as previously.
## Performance Improvements
@@ -150,4 +179,8 @@ and, in HDFS High-Availability instances
[8]: https://issues.apache.org/jira/browse/ACCUMULO-3301
[9]: https://issues.apache.org/jira/browse/ACCUMULO-3217
[10]: https://issues.apache.org/jira/browse/ACCUMULO-3372
-[11]: https://issues.apache.org/jira/browse/ACCUMULO-3385
\ No newline at end of file
+[11]: https://issues.apache.org/jira/browse/ACCUMULO-3385
+[12]: https://issues.apache.org/jira/browse/ACCUMULO-3233
+[13]: https://issues.apache.org/jira/browse/ACCUMULO-3351
+[14]: https://issues.apache.org/jira/browse/ACCUMULO-3462
+[15]: https://issues.apache.org/jira/browse/ACCUMULO-3230
\ No newline at end of file
