[activemq-website] branch main updated: [AMQ-7502] Update website references to LevelDB

[jb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jbonofre pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git


The following commit(s) were added to refs/heads/main by this push:
     new c5d4f88  [AMQ-7502] Update website references to LevelDB
     new 8d69b30  Merge pull request #51 from ehossack-aws/amq-7502/leveldb-refs
c5d4f88 is described below

commit c5d4f885b00739e3633794c44c1f5f2ae46bdabc
Author: Étienne H <eh...@amazon.com>
AuthorDate: Fri May 28 16:39:18 2021 -0700

    [AMQ-7502] Update website references to LevelDB
    
    * Remove high-level references/links to LevelDB
    * Clarify archival nature of pages (prevent dead links)
    * Quantify lifetime of LevelDB in page references
---
 src/features.md          | 2 --
 src/leveldb-store.md     | 6 ++++--
 src/persistence.md       | 7 ++++++-
 src/pure-master-slave.md | 6 ++++++
 src/sitemap.md           | 1 -
 5 files changed, 16 insertions(+), 6 deletions(-)

diff --git a/src/features.md b/src/features.md
index af548a7..82fddbc 100644
--- a/src/features.md
+++ b/src/features.md
@@ -109,10 +109,8 @@ Apache ActiveMQ is packed with features; to get an idea you might want to look a
         *   [Sybase](sybase)
     *   [KahaDB](kahadb)
     *   [Kaha Persistence](kaha-persistence)
-    *   [LevelDB Store](leveldb-store)
     *   [Periodically checking disk limits](periodically-checking-disk-limits)
     *   [Pluggable storage lockers](pluggable-storage-lockers)
-    *   [Replicated LevelDB Store](replicated-Persistenceleveldb-store)
 *   [Scaling the Depth of a Queue](scaling-the-depth-of-a-queue)
 *   [Security](security)
     *   [Audit Logging](audit-logging)
diff --git a/src/leveldb-store.md b/src/leveldb-store.md
index e3557d6..81cb61c 100644
--- a/src/leveldb-store.md
+++ b/src/leveldb-store.md
@@ -7,11 +7,13 @@ type: activemq5
 
 > **Warning**
 > 
-> The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is [KahaDB](kahadb)
+> The LevelDB store has been removed from production.
+> This page only serves as an archival page for previous releases.
+> Use [KahaDB](kahadb) instead.
 
 > **Version Compatibility**
 > 
-> Available in ActiveMQ 5.8.0 and newer
+> Available in ActiveMQ 5.8.0 but became unsupported as of 5.14.2, and was removed in 5.17.0
 
 The LevelDB Store is a file based persistence database that is local to the message broker that is using it. It has been optimized to provide even faster persistence than KahaDB. It's similar to KahahDB but instead of using a custom B-Tree implementation to index the write ahead logs, it uses [LevelDB](https://code.google.com/p/leveldb/) based indexes which have several nice properties due to the 'append only' files access patterns :
 
diff --git a/src/persistence.md b/src/persistence.md
index 358d498..6a84e6d 100644
--- a/src/persistence.md
+++ b/src/persistence.md
@@ -7,11 +7,16 @@ type: activemq5
 
 [Features](features) > [Persistence](persistence)
 
+ActiveMQ V5.14.2 / V5.17.0
+-------------
+
+ActiveMQ 5.14.2 was the first release after the deprecation announcement of LevelDB. The implementation was removed in 5.17.0.
+We once again recommend you use [KahaDB](kahadb).
 
 ActiveMQ V5.9
 -------------
 
-In ActiveMQ 5.9, the [Replicated LevelDB Store](replicated-leveldb-store) is introduced. It handles using [Apache ZooKeeper](http://zookeeper.apache.org/) to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates to the master. This might become the preferred [Master Slave](masterslave) configuration going forward.
+In ActiveMQ 5.9, the [Replicated LevelDB Store](replicated-leveldb-store) was introduced. It handles using [Apache ZooKeeper](http://zookeeper.apache.org/) to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates to the master. It may have become the preferred [Master Slave](masterslave) configuration going forward.
 
 ActiveMQ V5.8
 -------------
diff --git a/src/pure-master-slave.md b/src/pure-master-slave.md
index 3e6fc08..cd2d32a 100644
--- a/src/pure-master-slave.md
+++ b/src/pure-master-slave.md
@@ -7,6 +7,12 @@ type: activemq5
 
 [Features](features) > [Clustering](clustering) > [MasterSlave](masterslave) > [Pure Master Slave](pure-master-slave)
 
+> **Warning**
+> 
+> The LevelDB store has been removed from production.
+> This page only serves as an archival page for previous releases.
+> Use [shared storage master/slave](masterslave) instead.
+
 
 ### Pure Master Slave
 
diff --git a/src/sitemap.md b/src/sitemap.md
index cd6153f..6e9dce0 100644
--- a/src/sitemap.md
+++ b/src/sitemap.md
@@ -328,7 +328,6 @@ Features
     *   [MasterSlave]()
         *   [JDBC Master Slave](jdbc-master-slave)
         *   [KahaDB Replication (Experimental)](kahadb-replication-experimental)
-        *   [Pure Master Slave](pure-master-slave)
         *   [Shared File System Master Slave](shared-file-system-master-slave)
     *   [Networks of Brokers](networks-of-brokers)
     *   [Replicated Message Store](replicated-message-store)