Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A35FE200D53 for ; Tue, 5 Dec 2017 17:32:30 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A1B52160C1B; Tue, 5 Dec 2017 16:32:30 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ECE64160BF1 for ; Tue, 5 Dec 2017 17:32:28 +0100 (CET) Received: (qmail 78423 invoked by uid 500); 5 Dec 2017 16:32:28 -0000 Mailing-List: contact commits-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list commits@accumulo.apache.org Received: (qmail 78414 invoked by uid 99); 5 Dec 2017 16:32:28 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2017 16:32:28 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 8D38B82091; Tue, 5 Dec 2017 16:32:27 +0000 (UTC) Date: Tue, 05 Dec 2017 16:32:27 +0000 To: "commits@accumulo.apache.org" Subject: [accumulo-website] branch asf-site updated: Jekyll build from master:3ed7aa9 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <151249154749.13421.15205397191249095079@gitbox.apache.org> From: mwalch@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: accumulo-website X-Git-Refname: refs/heads/asf-site X-Git-Reftype: branch X-Git-Oldrev: 2560f3d4f5598e769769fa33abd29ea21b076722 X-Git-Newrev: 82e86a392b701d9fc52e35877430b9d4fca03da0 X-Git-Rev: 82e86a392b701d9fc52e35877430b9d4fca03da0 X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated archived-at: Tue, 05 Dec 2017 16:32:30 -0000 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 82e86a3 Jekyll build from master:3ed7aa9 82e86a3 is described below commit 82e86a392b701d9fc52e35877430b9d4fca03da0 Author: Mike Walch AuthorDate: Tue Dec 5 11:32:08 2017 -0500 Jekyll build from master:3ed7aa9 Fixed page # on new upgrading page --- docs/2.0/administration/caching.html | 2 + .../administration/configuration-management.html | 2 + .../administration/configuration-properties.html | 2 + docs/2.0/administration/fate.html | 2 + docs/2.0/administration/in-depth-install.html | 2 + docs/2.0/administration/kerberos.html | 2 + docs/2.0/administration/monitoring-metrics.html | 2 + docs/2.0/administration/multivolume.html | 2 + docs/2.0/administration/replication.html | 2 + docs/2.0/administration/ssl.html | 2 + docs/2.0/administration/tracing.html | 2 + .../{monitoring-metrics.html => upgrading.html} | 173 ++++++++++++--------- docs/2.0/development/development_tools.html | 2 + docs/2.0/development/high_speed_ingest.html | 2 + docs/2.0/development/iterators.html | 2 + docs/2.0/development/mapreduce.html | 2 + docs/2.0/development/proxy.html | 2 + docs/2.0/development/sampling.html | 2 + docs/2.0/development/security.html | 2 + docs/2.0/development/summaries.html | 2 + docs/2.0/getting-started/clients.html | 2 + docs/2.0/getting-started/design.html | 2 + docs/2.0/getting-started/quick-install.html | 2 + docs/2.0/getting-started/shell.html | 2 + docs/2.0/getting-started/table_configuration.html | 2 + docs/2.0/getting-started/table_design.html | 2 + docs/2.0/troubleshooting/advanced.html | 2 + docs/2.0/troubleshooting/basic.html | 2 + .../troubleshooting/system-metadata-tables.html | 2 + docs/2.0/troubleshooting/tools.html | 2 + feed.xml | 4 +- 31 files changed, 157 insertions(+), 78 deletions(-) diff --git a/docs/2.0/administration/caching.html b/docs/2.0/administration/caching.html index 4787aed..c5c8fef 100644 --- a/docs/2.0/administration/caching.html +++ b/docs/2.0/administration/caching.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/configuration-management.html b/docs/2.0/administration/configuration-management.html index ff1e8ee..b1c67c4 100644 --- a/docs/2.0/administration/configuration-management.html +++ b/docs/2.0/administration/configuration-management.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/configuration-properties.html b/docs/2.0/administration/configuration-properties.html index 58cb1f9..245096f 100644 --- a/docs/2.0/administration/configuration-properties.html +++ b/docs/2.0/administration/configuration-properties.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/fate.html b/docs/2.0/administration/fate.html index fb4a61b..3ae4d66 100644 --- a/docs/2.0/administration/fate.html +++ b/docs/2.0/administration/fate.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/in-depth-install.html b/docs/2.0/administration/in-depth-install.html index 38626f2..e29c4e7 100644 --- a/docs/2.0/administration/in-depth-install.html +++ b/docs/2.0/administration/in-depth-install.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/kerberos.html b/docs/2.0/administration/kerberos.html index 78eb6ca..b50861b 100644 --- a/docs/2.0/administration/kerberos.html +++ b/docs/2.0/administration/kerberos.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/monitoring-metrics.html b/docs/2.0/administration/monitoring-metrics.html index 00a3ca9..bd98f97 100644 --- a/docs/2.0/administration/monitoring-metrics.html +++ b/docs/2.0/administration/monitoring-metrics.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/multivolume.html b/docs/2.0/administration/multivolume.html index 6a2d038..527e9fe 100644 --- a/docs/2.0/administration/multivolume.html +++ b/docs/2.0/administration/multivolume.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/replication.html b/docs/2.0/administration/replication.html index bf052a7..4ad10cf 100644 --- a/docs/2.0/administration/replication.html +++ b/docs/2.0/administration/replication.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/ssl.html b/docs/2.0/administration/ssl.html index f9eb777..edf8574 100644 --- a/docs/2.0/administration/ssl.html +++ b/docs/2.0/administration/ssl.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/tracing.html b/docs/2.0/administration/tracing.html index 62f3482..1f799e4 100644 --- a/docs/2.0/administration/tracing.html +++ b/docs/2.0/administration/tracing.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/administration/monitoring-metrics.html b/docs/2.0/administration/upgrading.html similarity index 63% copy from docs/2.0/administration/monitoring-metrics.html copy to docs/2.0/administration/upgrading.html index 00a3ca9..7514836 100644 --- a/docs/2.0/administration/monitoring-metrics.html +++ b/docs/2.0/administration/upgrading.html @@ -25,7 +25,7 @@ -Accumulo Documentation - Monitoring & Metrics +Accumulo Documentation - Upgrading Accumulo @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ @@ -320,118 +322,137 @@
-

Accumulo 2.0 documentation  >>  Administration  >>  Monitoring & Metrics

+

Accumulo 2.0 documentation  >>  Administration  >>  Upgrading Accumulo

-

Monitoring & Metrics

-
Edit this page
+

Upgrading Accumulo

+
Edit this page
-

Monitoring

+

Upgrading from 1.7 to 1.8

-

Accumulo Monitor

+

Upgrades from 1.7 to 1.8 are possible with little effort as no changes were made at the data layer and RPC changes were made in a backwards-compatible way. The recommended way is to stop Accumulo 1.7, perform the Accumulo upgrade to 1.8, and then start 1.8. Like previous versions, after 1.8 is started on a 1.7 instance, a one-time upgrade will happen by the Master which will prevent a downgrade back to 1.7. Upgrades are still one way. Upgrades from versions prior to 1.7 to 1.8 should [...] -

The Accumulo Monitor provides an interface for monitoring the status and health of -Accumulo components. The Accumulo Monitor provides a web UI for accessing this information at -http://_monitorhost_:9995/.

+

Existing configuration files from 1.7 should be compared against the examples provided in 1.8. The 1.7 configuration files should all function with 1.8 code, but you will likely want to include changes found in the 1.8.0 release notes and these release notes for 1.8.1.

-

Things highlighted in yellow may be in need of attention. -If anything is highlighted in red on the monitor page, it is something that definitely needs attention.

+

For upgrades from prior to 1.7, follow the upgrade instructions to 1.7 first.

-

The Overview page contains some summary information about the Accumulo instance, including the version, instance name, and instance ID. -There is a table labeled Accumulo Master with current status, a table listing the active Zookeeper servers, and graphs displaying various metrics over time. -These include ingest and scan performance and other useful measurements.

+

Upgrading from 1.7.x to 1.7.y

-

The Master Server, Tablet Servers, and Tables pages display metrics grouped in different ways (e.g. by tablet server or by table). -Metrics typically include number of entries (key/value pairs), ingest and query rates. -The number of running scans, major and minor compactions are in the form number_running (number_queued). -Another important metric is hold time, which is the amount of time a tablet has been waiting but unable to flush its memory in a minor compaction.

+

The recommended way to upgrade from a prior 1.7.x release is to stop Accumulo, upgrade to 1.7.y and then start 1.7.y.

-

The Server Activity page graphically displays tablet server status, with each server represented as a circle or square. -Different metrics may be assigned to the nodes’ color and speed of oscillation. -The Overall Avg metric is only used on the Server Activity page, and represents the average of all the other metrics (after normalization). -Similarly, the Overall Max metric picks the metric with the maximum normalized value.

+

When upgrading, there is a known issue if the upgrade fails due to outstanding FATE operations, see ACCUMULO-4496 The work around if this situation is encountered:

-

The Garbage Collector page displays a list of garbage collection cycles, the number of files found of each type (including deletion candidates in use and files actually deleted), and the length of the deletion cycle. -The Traces page displays data for recent traces performed (see the following section for information on tracing). -The Recent Logs page displays warning and error logs forwarded to the monitor from all Accumulo processes. -Also, the XML and JSON links provide metrics in XML and JSON formats, respectively.

+
    +
  • Start tservers
    • +
  • Start shell
    • +
  • Run fate print to list all
    • +
  • If completed, just delete with fate delete
    • +
  • Start masters once there are no more fate operations
    • +
-

The Accumulo monitor does a best-effort to not display any sensitive information to users; however, -the monitor is intended to be a tool used with care. It is not a production-grade webservice. It is -a good idea to whitelist access to the monitor via an authentication proxy or firewall. It -is strongly recommended that the Monitor is not exposed to any publicly-accessible networks.

+

If any of the FATE operations are not complete, you should rollback the upgrade and troubleshoot completing them with your prior version. When performing an upgrade between major versions, the upgrade is one-way, therefore it is important that you do not have any outstanding FATE operations before starting the upgrade.

-

SSL

+

Upgrading from 1.6 to 1.7

-

SSL may be enabled for the monitor page by setting the following properties in the accumulo-site.xml file:

+

Upgrades from 1.6 to 1.7 are possible with little effort as no changes were made at the data layer and RPC changes were made in a backwards-compatible way. The recommended way is to stop Accumulo 1.6, perform the Accumulo upgrade to 1.7, and then start 1.7. Like previous versions, after 1.7.0 is started on a 1.6 instance, a one-time upgrade will happen by the Master which will prevent a downgrade back to 1.6. Upgrades are still one way. Upgrades from versions prior to 1.6 to 1.7 shoul [...] -

monitor.ssl.keyStore
-monitor.ssl.keyStorePassword
-monitor.ssl.trustStore
-monitor.ssl.trustStorePassword
-
-
+

After upgrading to 1.7.0, users will notice the addition of a replication table in the accumulo namespace. This table is created and put offline to avoid any additional maintenance if the data-center replication feature is not in use.

-

If the Accumulo conf directory has been configured (in particular the accumulo-env.sh file must be set up), the -accumulo-util gen-monitor-cert command can be used to create the keystore and truststore files with random passwords. The command -will print out the properties that need to be added to the accumulo-site.xml file. The stores can also be generated manually with the -Java keytool command, whose usage can be seen in the accumulo-util script.

+

Existing configuration files from 1.6 should be compared against the examples provided in 1.7. The 1.6 configuration files should all function with 1.7 code, but you will likely want to include a new file (hadoop-metrics2-accumulo.properties) to enable the new metrics subsystem. Read the section on Hadoop Metrics2 in the Administration chapter of the Accumulo User Manual.

-

If desired, the SSL ciphers allowed for connections can be controlled via the following properties in accumulo-site.xml:

+

For each of the other new features, new configuration properties exist to support the feature. Refer to the added sections in the User Manual for the feature for information on how to properly configure and use the new functionality.

-
monitor.ssl.include.ciphers
-monitor.ssl.exclude.ciphers
-
-
+

Upgrading from 1.5 to 1.6

+ +

This happens automatically the first time Accumulo 1.6 is started.

+ +

If your instance previously upgraded from 1.4 to 1.5, you must verify that your +1.5 instance has no outstanding local write ahead logs. You can do this by ensuring +either:

-

If SSL is enabled, the monitor URL can only be accessed via https. -This also allows you to access the Accumulo shell through the monitor page. -The left navigation bar will have a new link to Shell. -An Accumulo user name and password must be entered for access to the shell.

+
    +
  • All of your tables are online and the Monitor shows all tablets hosted
    • +
  • The directory for write ahead logs (logger.dir.walog) from 1.4 has no files remaining + on any tablet server / logger hosts
    • +
-

Metrics

+

To upgrade from 1.5 to 1.6 you must:

-

Accumulo can expose metrics through a legacy metrics library and using the Hadoop Metrics2 library.

+
    +
  • Verify that there are no outstanding FATE operations +
      +
    • Under 1.5 you can list what’s in FATE by running +$ACCUMULO_HOME/bin/accumulo org.apache.accumulo.server.fate.Admin print
      • +
    • Note that operations in any state will prevent an upgrade. It is safe +to delete operations with status SUCCESSFUL. For others, you should restart +your 1.5 cluster and allow them to finish.
      • +
    +
    • +
  • Stop the 1.5 instance.
    • +
  • Configure 1.6 to use the hdfs directory and zookeepers that 1.5 was using.
    • +
  • Copy other 1.5 configuration options as needed.
    • +
  • Start Accumulo 1.6.
    • +
-

Legacy Metrics

+

The upgrade process must make changes to Accumulo’s internal state in both ZooKeeper and + the table metadata. This process may take some time if Tablet Servers have to go through + recovery. During this time, the Monitor will claim that the Master is down and some + services may send the Monitor log messages about failure to communicate with each other. + These messages are safe to ignore. If you need detail on the upgrade’s progress you should + view the local logs on the Tablet Servers and active Master.

-

Accumulo has a legacy metrics library that can be exposes metrics using JMX endpoints or file-based logging. These metrics can -be enabled by setting general.legacy.metrics to true in accumulo-site.xml and placing the accumulo-metrics.xml -configuration file on the classpath (which is typically done by placing the file in the conf/ directory). A template for -accumulo-metrics.xml can be found in conf/templates of the Accumulo tarball.

+

Upgrading from 1.4 to 1.6

+ +

To upgrade from 1.4 to 1.6 you must perform a manual initial step.

+ +

Prior to upgrading you must:

+ +
    +
  • Verify that there are no outstanding FATE operations +
      +
    • Under 1.4 you can list what’s in FATE by running $ACCUMULO_HOME/bin/accumulo org.apache.accumulo.server.fate.Admin print
      • +
    • Note that operations in any state will prevent an upgrade. It is safe to delete operations with status SUCCESSFUL. For others, + you should restart your 1.4 cluster and allow them to finish.
      • +
    +
    • +
  • Stop the 1.4 instance.
    • +
  • Configure 1.6 to use the hdfs directory, walog directories, and zookeepers that 1.4 was using.
    • +
  • Copy other 1.4 configuration options as needed.
    • +
+ +

Prior to starting the 1.6 instance you will need to run the LocalWALRecovery tool on each node that previously ran an instance of the Logger role.

+ +
$ACCUMULO_HOME/bin/accumulo org.apache.accumulo.tserver.log.LocalWALRecovery
+
+
-

Hadoop Metrics2

+

The recovery tool will rewrite the 1.4 write ahead logs into a format that 1.6 can read. After this step has completed on all nodes, start the 1.6 cluster to continue the upgrade.

-

Hadoop Metrics2 is a library which allows for routing of metrics generated by registered MetricsSources to -configured MetricsSinks. Examples of sinks that are implemented by Hadoop include file-based logging, Graphite and Ganglia. -All metric sources are exposed via JMX when using Metrics2.

+

The upgrade process must make changes to Accumulo’s internal state in both ZooKeeper and the table metadata. This process may take some time if Tablet Servers have to go through recovery. During this time, the Monitor will claim that the Master is down and some services may send the Monitor log messages about failure to communicate with each other. While the upgrade is in progress, the Garbage Collector may complain about invalid paths. The Master may also complain about failure to cr [...] -

Metrics2 is configured by examining the classpath for a file that matches hadoop-metrics2*.properties. The Accumulo tarball -contains an example hadoop-metrics2-accumulo.properties file in conf/templates which can be copied to conf/ to place -on classpath. This file is used to enable file, Graphite or Ganglia sinks (some minimal configuration required for Graphite -and Ganglia). Because the Hadoop configuration is also on the Accumulo classpath, be sure that you do not have multiple -Metrics2 configuration files. It is recommended to consolidate metrics in a single properties file in a central location to -remove ambiguity. The contents of hadoop-metrics2-accumulo.properties can be added to a central hadoop-metrics2.properties -in $HADOOP_CONF_DIR.

+

Note that the LocalWALRecovery tool does not delete the local files. Once you confirm that 1.6 is successfully running, you should delete these files on the local filesystem.

-

As a note for configuring the file sink, the provided path should be absolute. A relative path or file name will be created relative -to the directory in which the Accumulo process was started. External tools, such as logrotate, can be used to prevent these files -from growing without bound.

+

Upgrading from 1.4 to 1.5

-

Each server process should have log messages from the Metrics2 library about the sinks that were created. Be sure to check -the Accumulo processes log files when debugging missing metrics output.

+

This happens automatically the first time Accumulo 1.5 is started.

-

For additional information on configuring Metrics2, visit the Javadoc page for Metrics2.

+
    +
  • Stop the 1.4 instance.
    • +
  • Configure 1.5 to use the hdfs directory, walog directories, and zookeepers +that 1.4 was using.
    • +
  • Copy other 1.4 configuration options as needed.
    • +
  • Start Accumulo 1.5.
    • +
Find documentation for all releases in the archive
-
Edit this page
+
Edit this page
diff --git a/docs/2.0/development/development_tools.html b/docs/2.0/development/development_tools.html index c8d9e7b..83fc4d8 100644 --- a/docs/2.0/development/development_tools.html +++ b/docs/2.0/development/development_tools.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/high_speed_ingest.html b/docs/2.0/development/high_speed_ingest.html index 38cb105..91c2085 100644 --- a/docs/2.0/development/high_speed_ingest.html +++ b/docs/2.0/development/high_speed_ingest.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/iterators.html b/docs/2.0/development/iterators.html index 1e4b814..31e8ece 100644 --- a/docs/2.0/development/iterators.html +++ b/docs/2.0/development/iterators.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/mapreduce.html b/docs/2.0/development/mapreduce.html index 11b12d9..b167ed0 100644 --- a/docs/2.0/development/mapreduce.html +++ b/docs/2.0/development/mapreduce.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/proxy.html b/docs/2.0/development/proxy.html index d6c9ec7..cf0413c 100644 --- a/docs/2.0/development/proxy.html +++ b/docs/2.0/development/proxy.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/sampling.html b/docs/2.0/development/sampling.html index 39ee793..074b178 100644 --- a/docs/2.0/development/sampling.html +++ b/docs/2.0/development/sampling.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/security.html b/docs/2.0/development/security.html index c793536..c6fca38 100644 --- a/docs/2.0/development/security.html +++ b/docs/2.0/development/security.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/development/summaries.html b/docs/2.0/development/summaries.html index 40610d0..8a7cc8a 100644 --- a/docs/2.0/development/summaries.html +++ b/docs/2.0/development/summaries.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/clients.html b/docs/2.0/getting-started/clients.html index 48d80b9..589517a 100644 --- a/docs/2.0/getting-started/clients.html +++ b/docs/2.0/getting-started/clients.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/design.html b/docs/2.0/getting-started/design.html index 8046234..e9f0054 100644 --- a/docs/2.0/getting-started/design.html +++ b/docs/2.0/getting-started/design.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/quick-install.html b/docs/2.0/getting-started/quick-install.html index 93ff85a..881f663 100644 --- a/docs/2.0/getting-started/quick-install.html +++ b/docs/2.0/getting-started/quick-install.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/shell.html b/docs/2.0/getting-started/shell.html index 775977b..d60aaa8 100644 --- a/docs/2.0/getting-started/shell.html +++ b/docs/2.0/getting-started/shell.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/table_configuration.html b/docs/2.0/getting-started/table_configuration.html index 93a64bb..8708458 100644 --- a/docs/2.0/getting-started/table_configuration.html +++ b/docs/2.0/getting-started/table_configuration.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/getting-started/table_design.html b/docs/2.0/getting-started/table_design.html index c245684..9fe67a9 100644 --- a/docs/2.0/getting-started/table_design.html +++ b/docs/2.0/getting-started/table_design.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/troubleshooting/advanced.html b/docs/2.0/troubleshooting/advanced.html index 4ffde01..3d8fd53 100644 --- a/docs/2.0/troubleshooting/advanced.html +++ b/docs/2.0/troubleshooting/advanced.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/troubleshooting/basic.html b/docs/2.0/troubleshooting/basic.html index 750d429..1d5183c 100644 --- a/docs/2.0/troubleshooting/basic.html +++ b/docs/2.0/troubleshooting/basic.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/troubleshooting/system-metadata-tables.html b/docs/2.0/troubleshooting/system-metadata-tables.html index 73e8c5c..4b7f457 100644 --- a/docs/2.0/troubleshooting/system-metadata-tables.html +++ b/docs/2.0/troubleshooting/system-metadata-tables.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/docs/2.0/troubleshooting/tools.html b/docs/2.0/troubleshooting/tools.html index 57e57ec..2f71ac4 100644 --- a/docs/2.0/troubleshooting/tools.html +++ b/docs/2.0/troubleshooting/tools.html @@ -268,6 +268,8 @@
Caching
+
Upgrading Accumulo
+ diff --git a/feed.xml b/feed.xml index b137e4b..cea0e21 100644 --- a/feed.xml +++ b/feed.xml @@ -6,8 +6,8 @@ https://accumulo.apache.org/ - Mon, 04 Dec 2017 15:16:13 -0500 - Mon, 04 Dec 2017 15:16:13 -0500 + Tue, 05 Dec 2017 11:31:56 -0500 + Tue, 05 Dec 2017 11:31:56 -0500 Jekyll v3.5.2 -- To stop receiving notification emails like this one, please contact ['"commits@accumulo.apache.org" '].