accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwa...@apache.org
Subject [accumulo-website] branch asf-site updated: Jekyll build from master:8830c20
Date Wed, 13 Dec 2017 16:47:17 GMT
This is an automated email from the ASF dual-hosted git repository.

mwalch pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 466ad78  Jekyll build from master:8830c20
466ad78 is described below

commit 466ad7843ff8897fc8cc26be177f5efc79bf9aee
Author: Mike Walch <mwalch@apache.org>
AuthorDate: Wed Dec 13 11:42:31 2017 -0500

    Jekyll build from master:8830c20
    
    Created post announcing Accumulo tour (#53)
---
 .../2017/12/12/take-the-accumulo-tour.html         |  83 +++-----
 feed.xml                                           | 210 ++++-----------------
 index.html                                         |  14 +-
 news/index.html                                    |   7 +
 tour/index.html                                    |   2 +-
 5 files changed, 76 insertions(+), 240 deletions(-)

diff --git a/tour/index.html b/blog/2017/12/12/take-the-accumulo-tour.html
similarity index 79%
copy from tour/index.html
copy to blog/2017/12/12/take-the-accumulo-tour.html
index 81c3190..2696dc4 100644
--- a/tour/index.html
+++ b/blog/2017/12/12/take-the-accumulo-tour.html
@@ -25,7 +25,7 @@
 <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/jq-2.2.3/dt-1.10.12/datatables.min.css">
 <link href="/css/accumulo.css" rel="stylesheet" type="text/css">
 
-<title>Accumulo Tour</title>
+<title>Take the Accumulo Tour!</title>
 
 <script src="https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js"></script>
 <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa"
crossorigin="anonymous"></script>
@@ -146,63 +146,36 @@
         </div>
         <div id="content">
           
-          <article class="post">
-
-  <header class="post-header">
-    <h1 class="post-title">Accumulo Tour</h1>
-  </header>
-
-  <div class="post-content">
-    
-<p>Welcome to the Accumulo tour! The tour offers a hands on introduction to the Accumulo
Java API, broken down into
-independent steps and exercises. The exercises give you a chance to apply what you have learned
by writing code on your
-own. The answers to an exercise are typically provided in the next step.  The tour starts
with a 
-<a href="/tour/getting-started/">Getting Started</a> page that will help you
get set up.</p>
-
-<p>When on a tour page, the left and right keys on the keyboard can be used to navigate.
If you have any questions
-or suggestions while going through the tour, please send an email to our <a href="/mailing_list/">mailing
list</a>
-or <a href="https://issues.apache.org/jira/projects/ACCUMULO">create an issue</a>.</p>
-
-<ol>
-  <li>
-    <p><a href="/tour/getting-started/">Getting Started</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/basic-read-write/">Writing and Reading</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/data-model/">Data Model</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/data-model-code/">Data Model Code</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/authorizations/">Authorizations</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/authorizations-code/">Authorizations Code</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/ranges-splits/">Ranges and Splits</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/batch-scanner/">Batch Scanner</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/batch-scanner-code/">Batch Scanner Code</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/conditional-writer/">Conditional Writer</a></p>
-  </li>
-  <li>
-    <p><a href="/tour/conditional-writer-code/">Conditional Writer Code</a></p>
-  </li>
-</ol>
+          <h1 class="title">Take the Accumulo Tour!</h1>
+          
+          <p>
+
+<b>Date: </b>&nbsp;&nbsp;12 Dec 2017<br>
+
+</p>
+
+<p>Apache Accumulo now has a <a href="/tour/">hands-on tour</a> that introduces
users to key Accumulo concepts
+by completing a series of programming exercises. Don’t worry! Solutions are provided if
+you get stuck.</p>
+
+<p>The tour has a <a href="/tour/getting-started/">getting started</a>
page that helps you set up your development environment and
+clone a repository with template code. After you are set up, the tour has exercises that
cover the
+following Accumulo concepts:</p>
+
+<ul>
+  <li><a href="/tour/basic-read-write/">Writing and Reading from Accumulo</a></li>
+  <li><a href="/tour/data-model/">Data Model</a></li>
+  <li><a href="/tour/authorizations/">Authorizations</a></li>
+  <li><a href="/tour/ranges-splits/">Ranges &amp; Splits</a></li>
+  <li><a href="/tour/batch-scanner/">Batch Scanner</a></li>
+  <li><a href="/tour/conditional-writer/">Conditional Writer</a></li>
+</ul>
+
+<p>More exercises (such as one on Accumulo Iterators) will be added in the future so
check for updates.</p>
 
 
-  </div>
 
-</article>
+<p><strong>View all posts in the <a href="/news">news archive</a></strong></p>
 
         </div>
 
diff --git a/feed.xml b/feed.xml
index d13695d..71fb826 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,12 +6,43 @@
 </description>
     <link>https://accumulo.apache.org/</link>
     <atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Tue, 12 Dec 2017 15:56:06 -0500</pubDate>
-    <lastBuildDate>Tue, 12 Dec 2017 15:56:06 -0500</lastBuildDate>
+    <pubDate>Wed, 13 Dec 2017 11:42:17 -0500</pubDate>
+    <lastBuildDate>Wed, 13 Dec 2017 11:42:17 -0500</lastBuildDate>
     <generator>Jekyll v3.5.2</generator>
     
     
       <item>
+        <title>Take the Accumulo Tour!</title>
+        <description>&lt;p&gt;Apache Accumulo now has a &lt;a href=&quot;/tour/&quot;&gt;hands-on
tour&lt;/a&gt; that introduces users to key Accumulo concepts
+by completing a series of programming exercises. Don’t worry! Solutions are provided if
+you get stuck.&lt;/p&gt;
+
+&lt;p&gt;The tour has a &lt;a href=&quot;/tour/getting-started/&quot;&gt;getting
started&lt;/a&gt; page that helps you set up your development environment and
+clone a repository with template code. After you are set up, the tour has exercises that
cover the
+following Accumulo concepts:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/basic-read-write/&quot;&gt;Writing
and Reading from Accumulo&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/data-model/&quot;&gt;Data Model&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/authorizations/&quot;&gt;Authorizations&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/ranges-splits/&quot;&gt;Ranges
&amp;amp; Splits&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/batch-scanner/&quot;&gt;Batch
Scanner&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;/tour/conditional-writer/&quot;&gt;Conditional
Writer&lt;/a&gt;&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;p&gt;More exercises (such as one on Accumulo Iterators) will be added in the
future so check for updates.&lt;/p&gt;
+
+</description>
+        <pubDate>Tue, 12 Dec 2017 00:00:00 -0500</pubDate>
+        <link>https://accumulo.apache.org/blog/2017/12/12/take-the-accumulo-tour.html</link>
+        <guid isPermaLink="true">https://accumulo.apache.org/blog/2017/12/12/take-the-accumulo-tour.html</guid>
+        
+        
+        <category>blog</category>
+        
+      </item>
+    
+      <item>
         <title>Accumulo Summit is on October 16th!</title>
         <description>&lt;p&gt;&lt;a href=&quot;http://accumulosummit.com/&quot;&gt;&lt;img
src=&quot;/images/accumulo-summit-2017-logo-horizontal.png&quot; alt=&quot;Accumulo
Summit&quot; width=&quot;400px&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
 
@@ -1350,180 +1381,5 @@ Commands:
         
       </item>
     
-      <item>
-        <title>Durability Performance Implications</title>
-        <description>&lt;h2 id=&quot;overview&quot;&gt;Overview&lt;/h2&gt;
-
-&lt;p&gt;Accumulo stores recently written data in a sorted in memory map.  Before
data is
-added to this map, it’s written to an unsorted write ahead log(WAL).  In the
-case when a tablet server dies, the recently written data is recovered from the
-WAL.&lt;/p&gt;
-
-&lt;p&gt;When data is written to Accumulo the following happens :&lt;/p&gt;
-
-&lt;ul&gt;
-  &lt;li&gt;Client sends a batch of mutations to a tablet server&lt;/li&gt;
-  &lt;li&gt;Tablet server does the following :
-    &lt;ul&gt;
-      &lt;li&gt;Writes mutation to tablet servers’ WAL&lt;/li&gt;
-      &lt;li&gt;Sync or flush tablet servers’ WAL&lt;/li&gt;
-      &lt;li&gt;Adds mutations to sorted in memory map of each tablet.&lt;/li&gt;
-      &lt;li&gt;Reports success back to client.&lt;/li&gt;
-    &lt;/ul&gt;
-  &lt;/li&gt;
-&lt;/ul&gt;
-
-&lt;p&gt;The sync/flush step above moves data written to the WAL from memory to disk.
-Write ahead logs are stored in HDFS. HDFS supports two ways of forcing data to
-disk for an open file : &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
and &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;.&lt;/p&gt;
-
-&lt;h2 id=&quot;hdfs-syncflush-details&quot;&gt;HDFS Sync/Flush Details&lt;/h2&gt;
-
-&lt;p&gt;When &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
is called on a WAL, it does not guarantee data is on disk.  It
-only guarantees that data is in OS buffers on each datanode and on its way to disk.
-As a result calls to &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
are very fast.  If a WAL is replicated to 3 data
-nodes then data may be lost if all three machines reboot or die.  If the datanode
-process dies, then data loss will not happen because the data was in OS buffers
-waiting to be written to disk.  The machines have to reboot or die for data loss to
-occur.&lt;/p&gt;
-
-&lt;p&gt;In order to avoid data loss in the event of reboot, &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
can be called.  This
-will ensure data is written to disk on all datanodes before returning.  When
-using &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
for the WAL, if Accumulo reports success to a user it means the
-data is on disk.  However &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
is much slower than &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
and the way it’s
-implemented exacerbates the problem.  For example &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
make take 1ms and
-&lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
may take 50ms.  This difference will impact writes to Accumulo and can
-be mitigated in some situations with larger buffers in Accumulo.&lt;/p&gt;
-
-&lt;p&gt;HDFS keeps checksum data internally by default.  Datanodes store checksum
data
-in a separate file in the local filesystem.  This means when &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
is called
-on a WAL, two files must be synced on each datanode.  Syncing two files doubles
-the time. To make matters even worse, when the two files are synced the local
-filesystem metadata is also synced.  Depending on the local filesystem and its
-configuration, syncing the metadata may or may not take time.  In the worst
-case, we need to wait for four sync operations at the local filesystem level on
-each datanode. One thing I am not sure about, is if these sync operations occur
-in parallel on the replicas on different datanodes.  If anyone can answer this
-question, please let us know on the &lt;a href=&quot;/mailing_list&quot;&gt;dev
list&lt;/a&gt;. The following pointers show
-where sync occurs in the datanode code.&lt;/p&gt;
-
-&lt;ul&gt;
-  &lt;li&gt;&lt;a href=&quot;https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockReceiver.java#L358&quot;&gt;BlockReceiver.flushOrSync()&lt;/a&gt;
calls &lt;a href=&quot;https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/fsdataset/ReplicaOutputStreams.java#L78&quot;&gt;ReplicaOutputStreams.syncDataOut()&lt;/a&gt;
a [...]
-  &lt;li&gt;The methods in ReplicaOutputStreams call &lt;a href=&quot;https://docs.oracle.com/javase/8/docs/api/java/nio/channels/FileChannel.html#force-boolean-&quot;&gt;FileChannel.force(true)&lt;/a&gt;
which
-synchronously flushes data and filesystem metadata.&lt;/li&gt;
-&lt;/ul&gt;
-
-&lt;p&gt;If files were preallocated (this would avoid syncing local filesystem metadata)
-and checksums were stored in-line, then 1 sync could be done instead of 4.&lt;/p&gt;
-
-&lt;h2 id=&quot;configuring-wal-flushsync-in-accumulo-16&quot;&gt;Configuring
WAL flush/sync in Accumulo 1.6&lt;/h2&gt;
-
-&lt;p&gt;Accumulo 1.6.0 only supported &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
and this caused &lt;a href=&quot;/release/accumulo-1.6.0#slower-writes-than-previous-accumulo-versions&quot;&gt;performance
-problems&lt;/a&gt;.  In order to offer better performance, the option to
-configure &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
was &lt;a href=&quot;/release/accumulo-1.6.1#write-ahead-log-sync-implementation&quot;&gt;added
in 1.6.1&lt;/a&gt;.  The
-&lt;a href=&quot;/1.6/accumulo_user_manual#_tserver_wal_sync_method&quot;&gt;tserver.wal.sync.method&lt;/a&gt;
configuration option was added to support
-this feature.  This was a tablet server wide option that applied to everything
-written to any table.&lt;/p&gt;
-
-&lt;h2 id=&quot;group-commit&quot;&gt;Group Commit&lt;/h2&gt;
-
-&lt;p&gt;Each Accumulo tablet server has a single WAL.  When multiple clients send
-mutations to a tablet server at around the same time, the tablet sever may group
-all of this into a single WAL operation.  It will do this instead of writing and
-syncing or flushing each client’s mutations to the WAL separately.  Doing this
-increase throughput and lowers average latency for clients.&lt;/p&gt;
-
-&lt;h2 id=&quot;configuring-wal-flushsync-in-accumulo-17&quot;&gt;Configuring
WAL flush/sync in Accumulo 1.7+&lt;/h2&gt;
-
-&lt;p&gt;Accumulo 1.7.0 introduced &lt;a href=&quot;/1.7/accumulo_user_manual#_table_durability&quot;&gt;table.durability&lt;/a&gt;,
a new per table property
-for configuring durability.  It also stopped using the &lt;code class=&quot;highlighter-rouge&quot;&gt;tserver.wal.sync.method&lt;/code&gt;
-property.  The &lt;code class=&quot;highlighter-rouge&quot;&gt;table.durability&lt;/code&gt;
property has the following four legal values.
-This property defaults to the most durable option which is &lt;code class=&quot;highlighter-rouge&quot;&gt;sync&lt;/code&gt;.&lt;/p&gt;
-
-&lt;ul&gt;
-  &lt;li&gt;&lt;strong&gt;none&lt;/strong&gt; : Do not write to WAL&lt;/li&gt;
-  &lt;li&gt;&lt;strong&gt;log&lt;/strong&gt;  : Write to WAL, but
do not sync&lt;/li&gt;
-  &lt;li&gt;&lt;strong&gt;flush&lt;/strong&gt; : Write to WAL and
call &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;&lt;/li&gt;
-  &lt;li&gt;&lt;strong&gt;sync&lt;/strong&gt; : Write to WAL and
call &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;&lt;/li&gt;
-&lt;/ul&gt;
-
-&lt;p&gt;If multiple writes arrive at around the same time with different durability
-settings, then the group commit code will choose the most durable.  This can
-cause one tables settings to slow down writes to another table.  Basically, one
-table that is set to &lt;code class=&quot;highlighter-rouge&quot;&gt;sync&lt;/code&gt;
can impact the entire system.&lt;/p&gt;
-
-&lt;p&gt;In Accumulo 1.6, it was easy to make all writes use &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;
because there was
-only one tserver setting.  Getting everything to use &lt;code class=&quot;highlighter-rouge&quot;&gt;flush&lt;/code&gt;
in 1.7 and later
-can be a little tricky because by default the Accumulo metadata table is set to
-use &lt;code class=&quot;highlighter-rouge&quot;&gt;sync&lt;/code&gt;.
 The following shell commands show this. The first command sets
-&lt;code class=&quot;highlighter-rouge&quot;&gt;table.durability=flush&lt;/code&gt;
as a system wide default for all tables.  However, the
-metadata table is still set to &lt;code class=&quot;highlighter-rouge&quot;&gt;sync&lt;/code&gt;,
because it has a per table override for
-that setting.  This override is set when Accumulo is initialized.  To get this
-table to use &lt;code class=&quot;highlighter-rouge&quot;&gt;flush&lt;/code&gt;,
the per table override must be deleted.  After deleting
-those properties, the metadata tables will inherit the system wide setting.&lt;/p&gt;
-
-&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;root@uno&amp;gt;
config -s table.durability=flush
-root@uno&amp;gt; createtable foo
-root@uno foo&amp;gt; config -t foo -f table.durability
------------+---------------------+----------------------------------------------
-SCOPE      | NAME                | VALUE
------------+---------------------+----------------------------------------------
-default    | table.durability .. | sync
-system     |    @override ...... | flush
------------+---------------------+----------------------------------------------
-root@uno&amp;gt; config -t accumulo.metadata -f table.durability
------------+---------------------+----------------------------------------------
-SCOPE      | NAME                | VALUE
------------+---------------------+----------------------------------------------
-default    | table.durability .. | sync
-system     |    @override ...... | flush
-table      |    @override ...... | sync
------------+---------------------+----------------------------------------------
-root@uno&amp;gt; config -t accumulo.metadata -d table.durability
-root@uno&amp;gt; config -t accumulo.metadata -f table.durability
------------+---------------------+----------------------------------------------
-SCOPE      | NAME                | VALUE
------------+---------------------+----------------------------------------------
-default    | table.durability .. | sync
-system     |    @override ...... | flush
------------+---------------------+----------------------------------------------
-&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-
-&lt;p&gt;In short, executing the following commands will make all writes use &lt;code
class=&quot;highlighter-rouge&quot;&gt;flush&lt;/code&gt;
-(assuming no other tables or namespaces have been specifically set to &lt;code class=&quot;highlighter-rouge&quot;&gt;sync&lt;/code&gt;).&lt;/p&gt;
-
-&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;config
-s table.durability=flush
-config -t accumulo.metadata -d table.durability
-config -t accumulo.root -d table.durability
-&lt;/code&gt;&lt;/pre&gt;
-&lt;/div&gt;
-
-&lt;p&gt;Even with these settings adjusted, minor compactions could still force &lt;code
class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
-to be called in 1.7.0 and 1.7.1.  This was fixed in 1.7.2 and 1.8.0.  See the
-&lt;a href=&quot;/release/accumulo-1.7.2#minor-performance-improvements&quot;&gt;1.7.2
release notes&lt;/a&gt; and &lt;a href=&quot;https://issues.apache.org/jira/browse/ACCUMULO-4112&quot;&gt;ACCUMULO-4112&lt;/a&gt;
for more details.&lt;/p&gt;
-
-&lt;p&gt;In addition to the per table durability setting, a per batch writer durability
-setting was also added in 1.7.0.  See
-&lt;a href=&quot;/1.8/apidocs/org/apache/accumulo/core/client/BatchWriterConfig.html#setDurability(org.apache.accumulo.core.client.Durability)&quot;&gt;BatchWriterConfig.setDurability(…)&lt;/a&gt;.
 This means any client could
-potentially cause a &lt;code class=&quot;highlighter-rouge&quot;&gt;hsync&lt;/code&gt;
operation to occur, even if the system is
-configured to use &lt;code class=&quot;highlighter-rouge&quot;&gt;hflush&lt;/code&gt;.&lt;/p&gt;
-
-&lt;h2 id=&quot;improving-the-situation&quot;&gt;Improving the situation&lt;/h2&gt;
-
-&lt;p&gt;The more granular durability settings introduced in 1.7.0 can cause some
-unexpected problems.  &lt;a href=&quot;https://issues.apache.org/jira/browse/ACCUMULO-4146&quot;&gt;ACCUMULO-4146&lt;/a&gt;
suggests one possible way to solve these
-problems with Per-durability write ahead logs.&lt;/p&gt;
-
-</description>
-        <pubDate>Wed, 02 Nov 2016 13:00:00 -0400</pubDate>
-        <link>https://accumulo.apache.org/blog/2016/11/02/durability-performance.html</link>
-        <guid isPermaLink="true">https://accumulo.apache.org/blog/2016/11/02/durability-performance.html</guid>
-        
-        
-        <category>blog</category>
-        
-      </item>
-    
   </channel>
 </rss>
diff --git a/index.html b/index.html
index a6403e8..89eef50 100644
--- a/index.html
+++ b/index.html
@@ -186,6 +186,13 @@
         
         <div class="row latest-news-item">
           <div class="col-sm-12" style="margin-bottom: 5px">
+           <span style="font-size: 12px; margin-right: 5px;">Dec 2017</span>
+           <a href="/blog/2017/12/12/take-the-accumulo-tour.html">Take the Accumulo
Tour!</a>
+          </div>
+        </div>
+        
+        <div class="row latest-news-item">
+          <div class="col-sm-12" style="margin-bottom: 5px">
            <span style="font-size: 12px; margin-right: 5px;">Jul 2017</span>
            <a href="/blog/2017/07/27/accumulo-summmit-on-october-16.html">Accumulo
Summit is on October 16th!</a>
           </div>
@@ -212,13 +219,6 @@
           </div>
         </div>
         
-        <div class="row latest-news-item">
-          <div class="col-sm-12" style="margin-bottom: 5px">
-           <span style="font-size: 12px; margin-right: 5px;">Mar 2017</span>
-           <a href="/blog/2017/03/21/happy-anniversary-accumulo.html">Happy Anniversary
Accumulo</a>
-          </div>
-        </div>
-        
         <div id="news-archive-link">
          <p>View all posts in the <a href="/news">news archive</a></p>
         </div>
diff --git a/news/index.html b/news/index.html
index b2430ae..447aaa7 100644
--- a/news/index.html
+++ b/news/index.html
@@ -156,6 +156,13 @@
   
   
   <div class="row" style="margin-top: 15px">
+    <div class="col-md-1">Dec 12</div>
+    <div class="col-md-10"><a href="/blog/2017/12/12/take-the-accumulo-tour.html">Take
the Accumulo Tour!</a></div>
+  </div>
+
+  
+  
+  <div class="row" style="margin-top: 15px">
     <div class="col-md-1">Jul 27</div>
     <div class="col-md-10"><a href="/blog/2017/07/27/accumulo-summmit-on-october-16.html">Accumulo
Summit is on October 16th!</a></div>
   </div>
diff --git a/tour/index.html b/tour/index.html
index 81c3190..e0cd0d3 100644
--- a/tour/index.html
+++ b/tour/index.html
@@ -160,7 +160,7 @@ own. The answers to an exercise are typically provided in the next step.
 The to
 <a href="/tour/getting-started/">Getting Started</a> page that will help you
get set up.</p>
 
 <p>When on a tour page, the left and right keys on the keyboard can be used to navigate.
If you have any questions
-or suggestions while going through the tour, please send an email to our <a href="/mailing_list/">mailing
list</a>
+or suggestions while going through the tour, please send an email to our <a href="/contact-us/#mailing-lists">mailing
list</a>
 or <a href="https://issues.apache.org/jira/projects/ACCUMULO">create an issue</a>.</p>
 
 <ol>

-- 
To stop receiving notification emails like this one, please contact
['"commits@accumulo.apache.org" <commits@accumulo.apache.org>'].

Mime
View raw message