accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r951746 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.7.0.html
Date Mon, 18 May 2015 15:35:25 GMT
Author: buildbot
Date: Mon May 18 15:35:25 2015
New Revision: 951746

Staging update by buildbot for accumulo

    websites/staging/accumulo/trunk/content/   (props changed)

Propchange: websites/staging/accumulo/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Mon May 18 15:35:25 2015
@@ -1 +1 @@

Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.0.html
--- websites/staging/accumulo/trunk/content/release_notes/1.7.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.0.html Mon May 18 15:35:25 2015
@@ -213,6 +213,7 @@ Latest 1.5 release: <strong>1.5.2</stron
     <p>Apache Accumulo 1.7.0 is a release that needs to be described</p>
 <h1 id="draft-draft-draft-draft-draft-draft">DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT</h1>
+<h1 id="notable-improvements">Notable Improvements</h1>
 <h3 id="client-authentication-with-kerberos">Client Authentication with Kerberos</h3>
 <p>Kerberos is far and away the de-facto means provide strong authentication across
 and other related components. Kerberos uses requires a centralized key distribution center
@@ -234,6 +235,21 @@ and authorization module.</p>
 authentication can be found in the <a href="">Kerberos
chapter</a> of the Accumulo
 User Manual.</p>
 <h3 id="data-center-replication">Data-Center Replication</h3>
+<p>In previous releases, Accumulo only operated withing the constraints of a single
+Because single instances of Accumulo often consist of many nodes and Accumulo's design scales
+efficiently across many nodes, it is typical that one Accumulo is run per physical installation
+or data-center. <a href="">ACCUMULO-378</a>
introduces support in Accumulo to automatically
+copy data from one Accumulo instance to another.</p>
+<p>This data-center replication feature is directly applicable for users wishing to
+a disaster recovery strategy. Data can be automatically sent from a primary instance to one
+or more other Accumulo instances. Conversely to normal Accumulo operation in which ingest
+query are strongly consistent, replication is a lazy, eventually consistent operation. This
+is desirable for replication as it prevent additional latency for ingest operations on the
+primary instance. Additionally, outages between the primary instance and replicas can sustain
+prolonged outages without any administrative overhead.</p>
+<p>The Accumulo User Manual contains a <a href="">new
chapter on replication</a> which covers
+in better detail the design and implementation of the feature, how users can configure replication
+and special cases to consider when choosing to integrate the feature into a user application.</p>
 <h3 id="user-initiated-compaction-strategies">User Initiated Compaction Strategies</h3>
 <p>Per table compaction strategies were added in 1.6.0.  In 1.7.0 the ability to
 specify a compaction strategy for a user initiated compaction was added in

View raw message