This is an automated email from the ASF dual-hosted git repository. git-site-role 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 24fa165a1 Automatic Site Publish by Buildbot 24fa165a1 is described below commit 24fa165a12cfdd0caea3a191021f82ffd1dda42a Author: buildbot <us...@infra.apache.org> AuthorDate: Tue Oct 8 11:01:40 2024 +0000 Automatic Site Publish by Buildbot --- output/blog/2024/10/07/accumulo4-preview.html | 217 +++++++++++++++++++++ output/feed.xml | 158 +++++++-------- .../blog/202409_accumulo4/AccumuloDeployment1.png | Bin 0 -> 30785 bytes .../blog/202409_accumulo4/AccumuloDeployment2.png | Bin 0 -> 36242 bytes .../blog/202409_accumulo4/AccumuloDeployment3.png | Bin 0 -> 61210 bytes .../blog/202409_accumulo4/AccumuloDeployment4.png | Bin 0 -> 55056 bytes .../blog/202409_accumulo4/AccumuloDeployment5.png | Bin 0 -> 48132 bytes output/index.html | 14 +- output/news/index.html | 7 + output/search_data.json | 8 + 10 files changed, 321 insertions(+), 83 deletions(-) diff --git a/output/blog/2024/10/07/accumulo4-preview.html b/output/blog/2024/10/07/accumulo4-preview.html new file mode 100644 index 000000000..05e91dd7a --- /dev/null +++ b/output/blog/2024/10/07/accumulo4-preview.html @@ -0,0 +1,217 @@ +<!DOCTYPE html> +<html lang="en"> +<head> +<!-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<meta charset="utf-8"> +<meta http-equiv="X-UA-Compatible" content="IE=edge"> +<meta name="viewport" content="width=device-width, initial-scale=1"> + +<link rel="stylesheet" type="text/css" href="/css/bootstrap/5.3.3/dist/css/bootstrap.css"> +<link rel="stylesheet" type="text/css" href="/css/fontawesome/fontawesome-free-6.6.0-web/css/all.css"> +<link rel="stylesheet" type="text/css" href="/css/datatables/bs5/dt-2.0.8/datatables.css"> +<link rel="stylesheet" type="text/css" href="/css/accumulo.css"> + +<title>Accumulo 4.0 Feature Preview</title> + +<script type="text/javascript" src="/js/jquery/3.7.1/jquery.js"></script> +<script type="text/javascript" src="/js/bootstrap/5.3.3/dist/js/bootstrap.bundle.js"></script> +<script type="text/javascript" src="/js/datatables/bs5/dt-2.0.8/datatables.js"></script> +<script type="text/javascript" src="https://www.apachecon.com/event-images/snippet.js"></script> +<script type="text/javascript" src="/js/accumulo.js"></script> +</head> +<body style="padding-top: 100px"> + + <nav class="navbar navbar-expand-lg navbar-light fixed-top bg-light"> + <div class="container"> + <a class="navbar-brand" href="/"> + <img alt="Apache Accumulo" id="nav-logo" src="/images/accumulo-logo.png" width="200"> + </a> + <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbar-items"> + <span class="navbar-toggler-icon"></span> + </button> + <div class="collapse navbar-collapse" id="navbar-items"> + <ul class="navbar-nav me-auto"> + <li class="nav-item"><a class="nav-link" href="/downloads">Download</a></li> + <li class="nav-item"><a class="nav-link" href="/tour">Tour</a></li> + <li class="nav-item dropdown"> + <a class="nav-link dropdown-toggle" href="#" role="button" data-bs-toggle="dropdown">Releases</a> + <ul class="dropdown-menu"> + <li><a class="dropdown-item" href="/release/accumulo-3.0.0/">3.0.0 (Latest non-LTM)</a></li> + <li><a class="dropdown-item" href="/release/accumulo-2.1.3/">2.1.3 (Latest LTM)</a></li> + <li><a class="dropdown-item" href="/release/accumulo-1.10.4/">1.10.4 (Legacy LTM)</a></li> + <li><a class="dropdown-item" href="/release/">Archive</a></li> + </ul> + </li> + <li class="nav-item dropdown"> + <a class="nav-link dropdown-toggle" href="#" role="button" data-bs-toggle="dropdown">Documentation</a> + <ul class="dropdown-menu"> + <li><a class="dropdown-item" href="/docs/2.x">User Manual (2.x)</a></li> + <li><a class="dropdown-item" href="/docs/2.x/apidocs">Javadocs (2.x)</a></li> + <li><a class="dropdown-item" href="/api">Public API</a></li> + <li><a class="dropdown-item" href="/quickstart-1.x">Quickstart (1.x)</a></li> + <li><a class="dropdown-item" href="/accumulo2-maven-plugin">Accumulo Maven Plugin</a></li> + <li><a class="dropdown-item" href="/1.10/accumulo_user_manual.html">User Manual (1.10)</a></li> + <li><a class="dropdown-item" href="/1.10/apidocs">Javadocs (1.10)</a></li> + <li><a class="dropdown-item" href="/external-docs">External Docs</a></li> + <li><a class="dropdown-item" href="/docs-archive/">Archive</a></li> + </ul> + </li> + <li class="nav-item dropdown"> + <a class="nav-link dropdown-toggle" href="#" role="button" data-bs-toggle="dropdown">Community</a> + <ul class="dropdown-menu"> + <li><a class="dropdown-item" href="/contact-us">Contact Us</a></li> + <li><a class="dropdown-item" href="/how-to-contribute">How To Contribute</a></li> + <li><a class="dropdown-item" href="/people">People</a></li> + <li><a class="dropdown-item" href="/related-projects">Related Projects</a></li> + </ul> + </li> + <li class="nav-item"><a class="nav-link" href="/search">Search</a></li> + </ul> + <ul class="navbar-nav ms-auto"> + <li class="nav-item dropdown"> + <a class="nav-link dropdown-toggle" href="#" role="button" data-bs-toggle="dropdown"> + <img alt="Apache Software Foundation" src="https://www.apache.org/foundation/press/kit/feather.svg" width="15"/> + </a> + <ul class="dropdown-menu dropdown-menu-end"> + <li><a class="dropdown-item" href="https://www.apache.org">Apache Homepage <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/licenses/">License <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship">Sponsorship <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/security">Security <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/foundation/thanks">Thanks <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of Conduct <span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/foundation/policies/privacy.html">Privacy Policy<span class="fa-solid fa-up-right-from-square"></span></a></li> + <li><a class="dropdown-item" href="https://www.apache.org/events/current-event.html">Current Event <span class="fa-solid fa-up-right-from-square"></span></a></li> + </ul> + </li> + </ul> + </div> + </div> +</nav> + + + <div class="container"> + <div class="row"> + <div class="col-md-12"> + + <div id="non-canonical" style="display: none; background-color: #F0E68C; padding-left: 1em;"> + Visit the official site at: <a href="https://accumulo.apache.org">https://accumulo.apache.org</a> + </div> + <div id="content"> + + <h1 class="title">Accumulo 4.0 Feature Preview</h1> + + <p> +<b>Author: </b> Dave Marion<br> +<b>Date: </b> 07 Oct 2024<br> + +</p> + +<h2 id="background">Background</h2> + +<p>In version 2.1, we introduced two new optional and experimental features, <a href="https://accumulo.apache.org/blog/2021/07/08/external-compactions.html">External Compactions</a> and <a href="https://github.com/apache/accumulo/pull/2665">ScanServers</a>. The External Compactions feature included two new server processes, the CompactionCoordinator and the Compactor. Using these new processes and their related configurations allows the user to perform major compactions on Tablets extern [...] + +<p>The ScanServers feature included one new server process, the ScanServer, which allows users to execute scans against a Tablet external to the TabletServer. Because the ScanServer does not have access to the in-memory mutations within the TabletServer, we introduced a consistency level setting on the Scanner and BatchScanner where scans with the “immediate” consistency setting (default) would be sent to the TabletServer only and scans with the “eventual” consistency setting would be se [...] + +<h2 id="new-for-40">New For 4.0</h2> + +<p>The features in version 4.0 are intended to make running Accumulo in a cloud environment more cost-efficient by building on the optional and experimental features added in version 2.1. Prior to version 4.0, running an Accumulo instance required enough compute resources to host enough TabletServers to support the ingest, query, and Tablet maintenance (compact, split, merge, etc.) workload as Accumulo was originally designed to keep all Tablets immediately accessible all the time. Versi [...] + +<h3 id="on-demand-tablets">On-Demand Tablets</h3> + +<p>On an upgrade to Accumulo 4.0, the upgrade code will assign all Tablets (except for the root and metadata tables) with an availability setting of ONDEMAND. What this means is that the Tablet is not assigned and hosted by a TabletServer by default. If an operation is performed that requires a Tablet to be hosted by a TabletServer, then the operation will wait for the Tablet to be assigned and hosted. This setting can be changed and checked using the Shell commands <code class="language [...] + +<p>User operations that would require a Tablet to be hosted are live ingest and immediate consistency scans. Users can still interact with data in unhosted tablets via bulk import and eventual consistency scans, and users can still perform tablet maintenance operations on unhosted tablets. The root and metadata tables have an availability value of HOSTED, which cannot be changed by the user. If your application only performs eventual scans and bulk imports, then only one TabletServer is [...] + +<p>Because Tablets are now optionally hosted in a TabletServer, the implementation of all the Tablet maintenance functions had to be moved out of the TabletServer and re-implemented. Split, Merge, and other metadata-only operations were re-implemented as Fate operations in the Manager.</p> + +<h3 id="external-compactions-only">External Compactions Only</h3> + +<p>If a Tablet is not hosted, and the user is bulk importing to it, this could trigger the need for a major compaction. Hosting the Tablet just for the purpose of compacting it will cause churn on the cluster as the balancer may move Tablets around. This led to the decision to move all major compactions to the External Compactions feature. In 4.0, the CompactionCoordinator component was merged into the Manager process, so manually running the CompactionCoordinator process is no longer re [...] + +<h3 id="resource-groups">Resource Groups</h3> + +<p>In version 4.0 a new group property can be supplied to the Compactor, ScanServer, and TabletServer processes (this replaces the “queue” property mentioned previously for Compactors). If not specified, the default group is used. These properties allow the user to create groups of processes with the same name that can be used to host Tablets, execute major compactions, and perform eventual scans. For example, application A may have requirements that dictate the need for immediate access [...] + +<h3 id="increased-visibility">Increased Visibility</h3> + +<p>Speaking of scaling, in version 4.0 we are emitting more metrics that can be used to determine when and how a resource needs to be scaled. The resource group and application name tags can be used to identify the group and type of resource that needs to be scaled. The metric name and value can be used to determine how the resource needs to be scaled. For example, if the value for metric <code class="language-plaintext highlighter-rouge">accumulo.compactor.queue.jobs.queued</code> is in [...] + +<h2 id="possible-deployment-scenarios">Possible Deployment Scenarios</h2> + +<p>With the new features described above, many possible deployment scenarios are possible. We highlight a few of them below.</p> + +<h3 id="scenario-1">Scenario 1</h3> + +<p>The diagram below depicts the simplest deployment where all tables operate within the default group of resources. There are no ScanServers, so only immediate scans are available. Tablets for all tables are assigned, hosted, and balanced within the same set of TabletServers. Major compactions for all tablets are executed within the same set of Compactors.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment1.png" alt="Scenario1" /></p> + +<h3 id="scenario-2">Scenario 2</h3> + +<p>The diagram below depicts a slightly more complicated deployment where ScanServers are also being used to support eventual scans against Tablets.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment2.png" alt="Scenario2" /></p> + +<h3 id="scenario-3">Scenario 3</h3> + +<p>The diagram below depicts a deployment where multiple compactor groups are configured in the default resource group. The compaction configuration enables the user, for example, to send compactions to different groups based on the sum of the input file sizes. In this example we have two additional Compactor groups, default-small and default-large, that can be configured for some user tables. The Compactor group in the default resource group would be used for all other tables. See the [...] + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment3.png" alt="Scenario3" /></p> + +<h3 id="scenario-4">Scenario 4</h3> + +<p>The diagram below depicts a scenario where a second resource group, app1, has been created to service Tablets for Tables associated with a particular application. The application can perform eventual and immediate consistent scans, and performs live ingest into the Tables, so it needs both ScanServers and TabletServers. The user would configure their application to perform eventual scans using the instructions in the ScanServer blog post, configure major compactions to run in the app1 [...] + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment4.png" alt="Scenario4" /></p> + +<h3 id="scenario-5">Scenario 5</h3> + +<p>The diagram below is a slight modification to the prior scenario that shows the same app1 resource group, but without TabletServers. In this situation the associated application is only performing bulk imports and eventual scans on table data.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment5.png" alt="Scenario5" /></p> + +<h2 id="current-state-and-path-forward">Current State and Path Forward</h2> + +<p>Version 4.0.0-SNAPSHOT has been merged into the main branch. We have added over 100 new integration tests and all of the old and new tests are passing. We are planning on performing testing at increasing scales to determine what other architectural changes are needed. For example, we have discussed the possibility of needing to run multiple active Manager processes as the Manager is now responsible for performing more functions (CompactionCoordinator, more Fate operations, etc.).</p> + + + +<p><strong>View all posts in the <a href="/news">news archive</a></strong></p> + + </div> + + +<footer> + + <p><a href="https://www.apache.org/foundation/contributing"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support the ASF" id="asf-logo" height="100" /></a></p> + + <p>Copyright © 2011-2024 <a href="https://www.apache.org">The Apache Software Foundation</a>. +Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>.</p> + + <p>Apache®, the names of Apache projects and their logos, and the multicolor feather +logo are registered trademarks or trademarks of The Apache Software Foundation +in the United States and/or other countries.</p> + +</footer> + + + </div> + </div> + </div> +</body> +</html> diff --git a/output/feed.xml b/output/feed.xml index 08ef4ee96..67ef7ac89 100644 --- a/output/feed.xml +++ b/output/feed.xml @@ -6,11 +6,91 @@ </description> <link>https://accumulo.apache.org/</link> <atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/> - <pubDate>Fri, 27 Sep 2024 19:24:44 +0000</pubDate> - <lastBuildDate>Fri, 27 Sep 2024 19:24:44 +0000</lastBuildDate> + <pubDate>Tue, 08 Oct 2024 11:01:33 +0000</pubDate> + <lastBuildDate>Tue, 08 Oct 2024 11:01:33 +0000</lastBuildDate> <generator>Jekyll v4.3.4</generator> + <item> + <title>Accumulo 4.0 Feature Preview</title> + <description><h2 id="background">Background</h2> + +<p>In version 2.1, we introduced two new optional and experimental features, <a href="https://accumulo.apache.org/blog/2021/07/08/external-compactions.html">External Compactions</a> and <a href="https://github.com/apache/accumulo/pull/2665">ScanServers</a>. The External Compactions feature included two new server processes, the CompactionCoordinator and the Compactor. Using these new processes and their related configurations allows the u [...] + +<p>The ScanServers feature included one new server process, the ScanServer, which allows users to execute scans against a Tablet external to the TabletServer. Because the ScanServer does not have access to the in-memory mutations within the TabletServer, we introduced a consistency level setting on the Scanner and BatchScanner where scans with the “immediate” consistency setting (default) would be sent to the TabletServer only and scans with the “eventual” consistency setting would [...] + +<h2 id="new-for-40">New For 4.0</h2> + +<p>The features in version 4.0 are intended to make running Accumulo in a cloud environment more cost-efficient by building on the optional and experimental features added in version 2.1. Prior to version 4.0, running an Accumulo instance required enough compute resources to host enough TabletServers to support the ingest, query, and Tablet maintenance (compact, split, merge, etc.) workload as Accumulo was originally designed to keep all Tablets immediately accessible all the time. [...] + +<h3 id="on-demand-tablets">On-Demand Tablets</h3> + +<p>On an upgrade to Accumulo 4.0, the upgrade code will assign all Tablets (except for the root and metadata tables) with an availability setting of ONDEMAND. What this means is that the Tablet is not assigned and hosted by a TabletServer by default. If an operation is performed that requires a Tablet to be hosted by a TabletServer, then the operation will wait for the Tablet to be assigned and hosted. This setting can be changed and checked using the Shell commands <code class= [...] + +<p>User operations that would require a Tablet to be hosted are live ingest and immediate consistency scans. Users can still interact with data in unhosted tablets via bulk import and eventual consistency scans, and users can still perform tablet maintenance operations on unhosted tablets. The root and metadata tables have an availability value of HOSTED, which cannot be changed by the user. If your application only performs eventual scans and bulk imports, then only one TabletServ [...] + +<p>Because Tablets are now optionally hosted in a TabletServer, the implementation of all the Tablet maintenance functions had to be moved out of the TabletServer and re-implemented. Split, Merge, and other metadata-only operations were re-implemented as Fate operations in the Manager.</p> + +<h3 id="external-compactions-only">External Compactions Only</h3> + +<p>If a Tablet is not hosted, and the user is bulk importing to it, this could trigger the need for a major compaction. Hosting the Tablet just for the purpose of compacting it will cause churn on the cluster as the balancer may move Tablets around. This led to the decision to move all major compactions to the External Compactions feature. In 4.0, the CompactionCoordinator component was merged into the Manager process, so manually running the CompactionCoordinator process is no lon [...] + +<h3 id="resource-groups">Resource Groups</h3> + +<p>In version 4.0 a new group property can be supplied to the Compactor, ScanServer, and TabletServer processes (this replaces the “queue” property mentioned previously for Compactors). If not specified, the default group is used. These properties allow the user to create groups of processes with the same name that can be used to host Tablets, execute major compactions, and perform eventual scans. For example, application A may have requirements that dictate the need for immediate [...] + +<h3 id="increased-visibility">Increased Visibility</h3> + +<p>Speaking of scaling, in version 4.0 we are emitting more metrics that can be used to determine when and how a resource needs to be scaled. The resource group and application name tags can be used to identify the group and type of resource that needs to be scaled. The metric name and value can be used to determine how the resource needs to be scaled. For example, if the value for metric <code class="language-plaintext highlighter-rouge">accumulo.compactor.queue.jo [...] + +<h2 id="possible-deployment-scenarios">Possible Deployment Scenarios</h2> + +<p>With the new features described above, many possible deployment scenarios are possible. We highlight a few of them below.</p> + +<h3 id="scenario-1">Scenario 1</h3> + +<p>The diagram below depicts the simplest deployment where all tables operate within the default group of resources. There are no ScanServers, so only immediate scans are available. Tablets for all tables are assigned, hosted, and balanced within the same set of TabletServers. Major compactions for all tablets are executed within the same set of Compactors.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment1.png" alt="Scenario1" /></p> + +<h3 id="scenario-2">Scenario 2</h3> + +<p>The diagram below depicts a slightly more complicated deployment where ScanServers are also being used to support eventual scans against Tablets.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment2.png" alt="Scenario2" /></p> + +<h3 id="scenario-3">Scenario 3</h3> + +<p>The diagram below depicts a deployment where multiple compactor groups are configured in the default resource group. The compaction configuration enables the user, for example, to send compactions to different groups based on the sum of the input file sizes. In this example we have two additional Compactor groups, default-small and default-large, that can be configured for some user tables. The Compactor group in the default resource group would be used for all other tables. Se [...] + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment3.png" alt="Scenario3" /></p> + +<h3 id="scenario-4">Scenario 4</h3> + +<p>The diagram below depicts a scenario where a second resource group, app1, has been created to service Tablets for Tables associated with a particular application. The application can perform eventual and immediate consistent scans, and performs live ingest into the Tables, so it needs both ScanServers and TabletServers. The user would configure their application to perform eventual scans using the instructions in the ScanServer blog post, configure major compactions to run in th [...] + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment4.png" alt="Scenario4" /></p> + +<h3 id="scenario-5">Scenario 5</h3> + +<p>The diagram below is a slight modification to the prior scenario that shows the same app1 resource group, but without TabletServers. In this situation the associated application is only performing bulk imports and eventual scans on table data.</p> + +<p><img src="/images/blog/202409_accumulo4/AccumuloDeployment5.png" alt="Scenario5" /></p> + +<h2 id="current-state-and-path-forward">Current State and Path Forward</h2> + +<p>Version 4.0.0-SNAPSHOT has been merged into the main branch. We have added over 100 new integration tests and all of the old and new tests are passing. We are planning on performing testing at increasing scales to determine what other architectural changes are needed. For example, we have discussed the possibility of needing to run multiple active Manager processes as the Manager is now responsible for performing more functions (CompactionCoordinator, more Fate operations, etc.) [...] + +</description> + <pubDate>Mon, 07 Oct 2024 00:00:00 +0000</pubDate> + <link>https://accumulo.apache.org/blog/2024/10/07/accumulo4-preview.html</link> + <guid isPermaLink="true">https://accumulo.apache.org/blog/2024/10/07/accumulo4-preview.html</guid> + + + <category>blog</category> + + </item> + <item> <title>Apache Accumulo 2.1.3</title> <description><h2 id="about">About</h2> @@ -1872,79 +1952,5 @@ general.opentelemetry.enabled=true </item> - <item> - <title>Apache Accumulo 1.10.2</title> - <description><h2 id="about">About</h2> - -<p>Apache Accumulo 1.10.2 is a bug fix release of the 1.10 LTM release line.</p> - -<p>These release notes are highlights of the changes since 1.10.1. The full -detailed changes can be seen in the git history. If anything important is -missing from this list, please <a href="/contact-us">contact</a> us to have it included.</p> - -<p>Users of 1.10.1 or earlier are encouraged to upgrade to 1.10.2, as this is a -continuation of the 1.10 LTM release line with bug fixes and improvements, and -it supersedes any prior 1.x version. Users are also encouraged to consider -migrating to a 2.x version when one that is suitable for their needs becomes -available.</p> - -<h2 id="known-issues">Known Issues</h2> - -<p>Apache Commons VFS was upgraded in <a href="https://github.com/apache/accumulo/issues/1295">#1295</a> and some users have reported -issues similar to <a href="https://issues.apache.org/jira/projects/VFS/issues/VFS-683">VFS-683</a>. Possible solutions are discussed in <a href="https://github.com/apache/accumulo/issues/2775">#2775</a>.</p> - -<h2 id="major-improvements">Major Improvements</h2> - -<p>This release bundles <a href="https://reload4j.qos.ch/">reload4j</a> (<a href="https://github.com/apache/accumulo/issues/2458">#2458</a>) in -the convenience binary and uses that instead of log4j 1.2. This is to make it -easier for users to avoid the many CVEs that apply to log4j 1.2, which is no -longer being maintained. Accumulo 2.x versions will have already switched to -use the latest log4j 2. However, doing so required making some breaking API -changes and other substantial changes, so that can’t be done for Accumulo 1.10. -Using reload4j instead, was deemed to be a viable interim solution until -Accumulo 2.x.</p> - -<h3 id="other-improvements">Other Improvements</h3> - -<ul> - <li><a href="https://github.com/apache/accumulo/issues/1808">#1808</a> Re-throw exceptions in threads instead of merely logging them</li> - <li><a href="https://github.com/apache/accumulo/issues/1863">#1863</a> Avoid unnecessory redundant log sorting</li> - <li><a href="https://github.com/apache/accumulo/issues/1917">#1917</a> Ensure RFileWriterBuilder API validates filenames</li> - <li><a href="https://github.com/apache/accumulo/issues/2006">#2006</a> Detect system config changes in HostRegexTableLoadBalancer without restarting master</li> - <li><a href="https://github.com/apache/accumulo/issues/2464">#2464</a> Apply timeout to socket.connect()</li> -</ul> - -<h3 id="other-bug-fixes">Other Bug Fixes</h3> - -<ul> - <li><a href="https://github.com/apache/accumulo/issues/1775">#1775</a> Ensure monitor reports a dead tserver when it is killed</li> - <li><a href="https://github.com/apache/accumulo/issues/1858">#1858</a> Fix a bug in the monitor graphs due to use of int instead of long</li> - <li><a href="https://github.com/apache/accumulo/issues/2370">#2370</a> Fix bug in getsplits command in the shell</li> -</ul> - -<h2 id="note-about-jdk-15">Note About JDK 15</h2> - -<p>See the note in the 1.10.1 release notes about the use of JDK 15 or later, as -the information pertaining to the use of the CMS garbage collector remains -applicable to this version.</p> - -<h2 id="useful-links">Useful Links</h2> - -<ul> - <li><a href="https://lists.apache.org/thread/bq424vnov27nwnkb471oxg5nd7m6xwn9">Release VOTE email thread</a></li> - <li><a href="https://github.com/apache/accumulo/compare/rel/1.10.1...apache:rel/1.10.2">All Changes since 1.10.1</a></li> - <li><a href="https://github.com/apache/accumulo/milestone/9">All tickets related to this release</a></li> -</ul> - -</description> - <pubDate>Sun, 13 Feb 2022 00:00:00 +0000</pubDate> - <link>https://accumulo.apache.org/release/accumulo-1.10.2/</link> - <guid isPermaLink="true">https://accumulo.apache.org/release/accumulo-1.10.2/</guid> - - - <category>release</category> - - </item> - </channel> </rss> diff --git a/output/images/blog/202409_accumulo4/AccumuloDeployment1.png b/output/images/blog/202409_accumulo4/AccumuloDeployment1.png new file mode 100644 index 000000000..9af24857c Binary files /dev/null and b/output/images/blog/202409_accumulo4/AccumuloDeployment1.png differ diff --git a/output/images/blog/202409_accumulo4/AccumuloDeployment2.png b/output/images/blog/202409_accumulo4/AccumuloDeployment2.png new file mode 100644 index 000000000..183ff8b16 Binary files /dev/null and b/output/images/blog/202409_accumulo4/AccumuloDeployment2.png differ diff --git a/output/images/blog/202409_accumulo4/AccumuloDeployment3.png b/output/images/blog/202409_accumulo4/AccumuloDeployment3.png new file mode 100644 index 000000000..1e6eeb93b Binary files /dev/null and b/output/images/blog/202409_accumulo4/AccumuloDeployment3.png differ diff --git a/output/images/blog/202409_accumulo4/AccumuloDeployment4.png b/output/images/blog/202409_accumulo4/AccumuloDeployment4.png new file mode 100644 index 000000000..fd4595aa8 Binary files /dev/null and b/output/images/blog/202409_accumulo4/AccumuloDeployment4.png differ diff --git a/output/images/blog/202409_accumulo4/AccumuloDeployment5.png b/output/images/blog/202409_accumulo4/AccumuloDeployment5.png new file mode 100644 index 000000000..751cac58d Binary files /dev/null and b/output/images/blog/202409_accumulo4/AccumuloDeployment5.png differ diff --git a/output/index.html b/output/index.html index e6787303d..1ae5c49c2 100644 --- a/output/index.html +++ b/output/index.html @@ -152,6 +152,13 @@ <p style="font-size: 24px; margin-bottom: 0px;">Latest News</p> + <div class="row latest-news-item"> + <div class="col-sm-12" style="margin-bottom: 5px"> + <span style="font-size: 12px; margin-right: 5px;">Oct 2024</span> + <a href="/blog/2024/10/07/accumulo4-preview.html">Accumulo 4.0 Feature Preview</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;">Aug 2024</span> @@ -180,13 +187,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;">Aug 2023</span> - <a href="/release/accumulo-2.1.2/">Apache Accumulo 2.1.2</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/output/news/index.html b/output/news/index.html index 8e49c700e..71143fd52 100644 --- a/output/news/index.html +++ b/output/news/index.html @@ -122,6 +122,13 @@ + <div class="row" style="margin-top: 15px"> + <div class="col-md-1">Oct 07</div> + <div class="col-md-10"><a href="/blog/2024/10/07/accumulo4-preview.html">Accumulo 4.0 Feature Preview</a></div> + </div> + + + <div class="row" style="margin-top: 15px"> <div class="col-md-1">Aug 12</div> <div class="col-md-10"><a href="/release/accumulo-2.1.3/">Apache Accumulo 2.1.3</a></div> diff --git a/output/search_data.json b/output/search_data.json index 76f2526ca..57e33dd0f 100644 --- a/output/search_data.json +++ b/output/search_data.json @@ -330,6 +330,14 @@ }, + "blog-2024-10-07-accumulo4-preview-html": { + "title": "Accumulo 4.0 Feature Preview", + "content": "BackgroundIn version 2.1, we introduced two new optional and experimental features, External Compactions and ScanServers. The External Compactions feature included two new server processes, the CompactionCoordinator and the Compactor. Using these new processes and their related configurations allows the user to perform major compactions on Tablets external to the TabletServer process. The configuration in 2.1 allows the user to define different “queues” for the External [...] + "url": " /blog/2024/10/07/accumulo4-preview.html", + "categories": "blog" + } + , + "release-accumulo-2-1-3": { "title": "Apache Accumulo 2.1.3", "content": "AboutApache Accumulo 2.1.3 is a patch release of the 2.1 LTM line. It contains bugfixes and minor enhancements. This version supersedes 2.1.2. Users upgrading to2.1 should upgrade directly to this version instead of 2.1.2.Notable ChangesThe full set of changes are too numerous to be useful here. Below are some highlights of the mostsignificant bug fixes and features added in 2.1.3. For the full set of changes, please see thecommit history or issue tracker milestone link [...]