accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r940405 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.6.2.html
Date Mon, 16 Feb 2015 22:14:02 GMT
Author: buildbot
Date: Mon Feb 16 22:14:02 2015
New Revision: 940405

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/release_notes/1.6.2.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 16 22:14:02 2015
@@ -1 +1 @@
-1660216
+1660226

Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.2.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.6.2.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.2.html Mon Feb 16 22:14:02 2015
@@ -252,6 +252,28 @@ data stored in Accumulo using the broken
 </pre></div>
 
 
+<h3 id="reduce-miniaccumulocluster-failures-due-to-random-port-allocations">Reduce
MiniAccumuloCluster failures due to random port allocations</h3>
+<p><code>MiniAccumuloCluster</code> 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 <a href="https://issues.apache.org/jira/browse/ACCUMULO-3233">ACCUMULO-3233</a>
+and the related issues should eliminate sporadic failures users of <code>MiniAccumuloCluster</code>
might have observed.</p>
+<h3 id="tracer-doesnt-handle-trace-table-state-transition">Tracer doesn't handle trace
table state transition</h3>
+<p>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. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3351">ACCUMULO-3351</a>
ensures that the Tracer process
+will resume writing Spans to the trace table when it transitions to online after being offline.</p>
+<h3 id="tablet-not-major-compacting">Tablet not major compacting</h3>
+<p>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. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3462">ACCUMULO-3462</a>
identified as fix
+server-side which would prevent this from happening in the future.</p>
+<h3 id="yarn-job-submission-fails-with-hadoop-260">YARN job submission fails with Hadoop-2.6.0</h3>
+<p>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 <code>accumulo</code>
and <code>tool.sh</code> 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. <a href="https://issues.apache.org/jira/browse/ACCUMULO-3230">ACCUMULO-3230</a>
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.</p>
 <h2 id="performance-improvements">Performance Improvements</h2>
 <p>Apache Accumulo 1.6.2 includes a number of performance-related fixes over previous
versions.</p>
 <h3 id="improvement-1">Improvement 1</h3>



Mime
View raw message