From commits-return-22294-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Thu Nov 1 19:43:20 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DC07F180652 for ; Thu, 1 Nov 2018 19:43:19 +0100 (CET) Received: (qmail 60636 invoked by uid 500); 1 Nov 2018 18:43:18 -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 60627 invoked by uid 99); 1 Nov 2018 18:43:18 -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; Thu, 01 Nov 2018 18:43:18 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 414DC87032; Thu, 1 Nov 2018 18:43:18 +0000 (UTC) Date: Thu, 01 Nov 2018 18:43:18 +0000 To: "commits@accumulo.apache.org" Subject: [accumulo-website] branch asf-site updated: Jekyll build from master:99166db MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <154109779819.32359.2562111185178280139@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: 49e831695e0677ae51736cae243862f1e8653b37 X-Git-Newrev: 10135ddba84865e3ba1a5ef27dcf7f86d31c3874 X-Git-Rev: 10135ddba84865e3ba1a5ef27dcf7f86d31c3874 X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated 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 10135dd Jekyll build from master:99166db 10135dd is described below commit 10135ddba84865e3ba1a5ef27dcf7f86d31c3874 Author: Mike Walch AuthorDate: Thu Nov 1 14:42:40 2018 -0400 Jekyll build from master:99166db Created documentation for upgrading to 2.0 (#126) * Updated lexicoder docs in features --- docs/2.x/administration/upgrading.html | 99 +++++++++++++++++++++++++++++++++- docs/2.x/getting-started/features.html | 14 ++--- feed.xml | 4 +- search_data.json | 4 +- 4 files changed, 107 insertions(+), 14 deletions(-) diff --git a/docs/2.x/administration/upgrading.html b/docs/2.x/administration/upgrading.html index e21665e..0debcbb 100644 --- a/docs/2.x/administration/upgrading.html +++ b/docs/2.x/administration/upgrading.html @@ -422,7 +422,104 @@ -

Upgrading from 1.7 to 1.8

+

Upgrading from 1.8/9 to 2.0

+ +

Follow the steps below to upgrade your Accumulo instance and client to 2.0.

+ +

Upgrade Accumulo instance

+ +

IMPORTANT! Before upgrading to Accumulo 2.0, you will need to upgrade to Java 8 and Hadoop 3.x.

+ +

Upgrading to Accumulo 2.0 is done by stopping Accumulo 1.8/9 and starting Accumulo 2.0.

+ +

Before stopping Accumulo 1.8/9, install Accumulo 2.0 and configure it by following the 2.0 install instructions.

+ +

There are several changes to scripts and configuration in 2.0 so be careful when using configuration or automated setup designed for 1.8/9. +Below are some changes in 2.0 that you should be aware of:

+
    +
  • accumulo.properties has replaced accumulo-site.xml. You can either convert accumulo-site.xml by hand +from XML to properties or use the following Accumulo command. +
    accumulo convert-config -x old/accumulo-site.xml -p new/accumulo.properties
    +
    +
  • +
  • accumulo-client.properties has replaced client.conf. The client properties +in the new file are different so take care when customizing.
  • +
  • accumulo-cluster script has replaced the start-all.sh & stop-all.sh scripts. +
      +
    • Default host files (i.e masters, monitor, gc) are no longer in conf/ directory of tarball but can be created using accumulo-cluster create-config
    • +
    • Tablet server hosts must be listed in a tservers file instead of a slaves file. To minimize confusion, Accumulo will not start if the old slaves file is present.
    • +
    +
  • +
  • accumulo-service script can be used to start/stop Accumulo services (i.e master, tablet server, monitor) on a single node. +
      +
    • Can be used even if Accumulo was started using accumulo-cluster script.
    • +
    +
  • +
  • accumulo-env.sh constructs environment variables (such as JAVA_OPTS and CLASSPATH) used when running Accumulo processes +
      +
    • This file was used in Accumulo 1.x but has changed signficantly for 2.0
    • +
    • Environment variables (such as $cmd, $bin, $conf) are set before accumulo-env.sh is loaded and can be used to customize environment.
    • +
    • The JAVA_OPTS variable is constructed in accumulo-env.sh to pass command-line arguments to the java command that the starts Accumulo processes +(i.e. java $JAVA_OPTS main.class.for.$cmd).
    • +
    • The CLASSPATH variable sets the Java classpath used when running Accumulo processes. It can be modified to upgrade dependencies or use vendor-specific +distributions of Hadoop.
    • +
    +
  • +
  • Logging is configured in accumulo-env.sh for Accumulo processes. The following log4j configuration files in the conf/ directory will be used if +accumulo-env.sh is not modified. These files can be modified to turn on/off logging for Accumulo processes: +
      +
    • log4j-service.properties for all Accumulo services (except monitor)
    • +
    • logj4-monitor.properties for Accumulo monitor
    • +
    • log4j.properties for Accumulo clients and commands
    • +
    +
  • +
  • Run the command accumulo shell to access the shell using configuration in conf/accumulo-client.properties
  • +
+ +

When your Accumulo 2.0 installation is properly configured, stop Accumulo 1.8/9 and start Accumulo 2.0:

+ +
./accumulo-1.9.2/bin/stop-all.sh
+./accumulo-2.0.0/bin/accumulo-cluster start
+
+

It is recommended that users test this upgrade on development or test clusters before attempting it on production clusters.

+ +

Upgrade Accumulo clients

+ +

There several client API changes in 2.0. In most cases, new API was introduced and the old API was only deprecated. While it is recommended +that users start using the new API, the old API will continue to be supported through 2.x.

+ +

Below is a list of client API changes that users are required to make for 2.0:

+ +
    +
  • Update your pom.xml use Accumulo 2.0. Also, update any Hadoop & ZooKeeper dependencies in your pom.xml to match the versions runing on your cluster. +
    <dependency>
    +  <groupId>org.apache.accumulo</groupId>
    +  <artifactId>accumulo-core</artifactId>
    +  <version>2.0.0</version>
    +</dependency>
    +
    +
  • +
  • ClientConfiguration objects can no longer be ceated using new ClientConfiguration(). +
      +
    • Use ClientConfiguration.create() instead
    • +
    +
  • +
  • Some API deprecated in 1.x releases was dropped
  • +
  • Aggregators have been removed
  • +
+ +

Below is a list of recommended client API changes:

+ +