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 829c36b5 Automatic Site Publish by Buildbot
829c36b5 is described below

commit 829c36b5a27ae179e1f356db4172663d616fd324
Author: buildbot <us...@infra.apache.org>
AuthorDate: Mon Aug 7 12:33:38 2023 +0000

    Automatic Site Publish by Buildbot
---
 output/docs/2.x/troubleshooting/advanced.html | 11 ++++++++---
 output/feed.xml                               |  4 ++--
 output/search_data.json                       |  2 +-
 3 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/output/docs/2.x/troubleshooting/advanced.html 
b/output/docs/2.x/troubleshooting/advanced.html
index 434741f3..c1d48c32 100644
--- a/output/docs/2.x/troubleshooting/advanced.html
+++ b/output/docs/2.x/troubleshooting/advanced.html
@@ -775,18 +775,23 @@ overridden by using the <code class="language-plaintext 
highlighter-rouge">--loc
 <p><strong>I am trying to start the manager after upgrading but the upgrade is 
aborting with the following message:</strong>
   <code class="language-plaintext 
highlighter-rouge">org.apache.accumulo.core.client.AccumuloException: Aborting 
upgrade because there are outstanding FATE transactions from a previous 
Accumulo version.</code></p>
 
-<p>You can use the shell to delete completed FATE transactions using the 
following:</p>
+<p>For versions 2.1 and later, you can use the admin fate command to delete 
completed FATE transactions using the following:</p>
 
 <ul>
   <li>Start tservers</li>
   <li>Start shell</li>
-  <li>Run <code class="language-plaintext highlighter-rouge">fate print</code> 
to list all</li>
-  <li>If completed, just delete with <code class="language-plaintext 
highlighter-rouge">fate delete</code></li>
+  <li>Run <code class="language-plaintext highlighter-rouge">accumulo admin 
fate --print</code> to list all transactions</li>
+  <li>If the transactions have completed, just delete with them with <code 
class="language-plaintext highlighter-rouge">accumulo admin fate --delete TXID 
[TXID...]</code></li>
   <li>Start managers once there are no more fate operations</li>
 </ul>
 
 <p>If any of the operations are not complete, you should rollback the upgrade 
and troubleshoot completing them with your prior version.</p>
 
+<p>Prior to 2.1, the same steps apply, but the fate command is accessed with 
the Accumulo shell instead of the admin command.  The shell commands are as 
follows:</p>
+
+<p>use <code class="language-plaintext highlighter-rouge">fate print</code> to 
list transactions
+use <code class="language-plaintext highlighter-rouge">fate delete</code> to 
delete completed transactions</p>
+
 <h2 id="file-naming-conventions">File Naming Conventions</h2>
 
 <p><strong>Why are files named like they are? Why do some start with <code 
class="language-plaintext highlighter-rouge">C</code> and others with <code 
class="language-plaintext highlighter-rouge">F</code>?</strong></p>
diff --git a/output/feed.xml b/output/feed.xml
index 1c1a15a2..23601010 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>https://accumulo.apache.org/</link>
     <atom:link href="https://accumulo.apache.org/feed.xml"; rel="self" 
type="application/rss+xml"/>
-    <pubDate>Thu, 27 Jul 2023 19:50:06 +0000</pubDate>
-    <lastBuildDate>Thu, 27 Jul 2023 19:50:06 +0000</lastBuildDate>
+    <pubDate>Mon, 07 Aug 2023 12:33:32 +0000</pubDate>
+    <lastBuildDate>Mon, 07 Aug 2023 12:33:32 +0000</lastBuildDate>
     <generator>Jekyll v4.3.2</generator>
     
     
diff --git a/output/search_data.json b/output/search_data.json
index b3583390..e2c88ec4 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -268,7 +268,7 @@
   
     "docs-2-x-troubleshooting-advanced": {
       "title": "Advanced Troubleshooting",
-      "content": "Tablet server locksMy tablet server lost its lock.  Why?The 
primary reason a tablet server loses its lock is that it has been pushed into 
swap.A large java program (like the tablet server) may have a large portionof 
its memory image unused.  The operating system will favor pushingthis 
allocated, but unused memory into swap so that the memory can bere-used as a 
disk buffer.  When the java virtual machine decides toaccess this memory, the 
OS will begin flushing disk buffe [...]
+      "content": "Tablet server locksMy tablet server lost its lock.  Why?The 
primary reason a tablet server loses its lock is that it has been pushed into 
swap.A large java program (like the tablet server) may have a large portionof 
its memory image unused.  The operating system will favor pushingthis 
allocated, but unused memory into swap so that the memory can bere-used as a 
disk buffer.  When the java virtual machine decides toaccess this memory, the 
OS will begin flushing disk buffe [...]
       "url": " /docs/2.x/troubleshooting/advanced",
       "categories": "troubleshooting"
     },

Reply via email to