Return-Path: X-Original-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A0A6F936A for ; Mon, 12 Dec 2011 22:14:18 +0000 (UTC) Received: (qmail 83135 invoked by uid 500); 12 Dec 2011 22:14:18 -0000 Delivered-To: apmail-incubator-accumulo-user-archive@incubator.apache.org Received: (qmail 83111 invoked by uid 500); 12 Dec 2011 22:14:18 -0000 Mailing-List: contact accumulo-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: accumulo-user@incubator.apache.org Delivered-To: mailing list accumulo-user@incubator.apache.org Received: (qmail 83103 invoked by uid 99); 12 Dec 2011 22:14:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 22:14:18 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of scubafuchs@gmail.com designates 209.85.210.47 as permitted sender) Received: from [209.85.210.47] (HELO mail-pz0-f47.google.com) (209.85.210.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 22:14:10 +0000 Received: by dake40 with SMTP id e40so4884529dak.6 for ; Mon, 12 Dec 2011 14:13:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=mCcon0zeKBIf6ooM2X1Cgw+27gWbS3DLAouy52rHxMw=; b=eOvNeJtDugVZG0XG4grYZcmNK1xbzQB/3gqf+dILAqnDTqXZ47FY1tcGxPEZITcR+Y nZ4QjCdLlPstFEd0A19IG71qsyAU2LQv4R+Nt4pPgTN+Jq2DoKGoYIb7HzYKrzsJY6gJ mASTUek5t921DtcOsxiDB0VaACUJ0WU/R1Q8w= MIME-Version: 1.0 Received: by 10.68.189.97 with SMTP id gh1mr37255349pbc.37.1323728029434; Mon, 12 Dec 2011 14:13:49 -0800 (PST) Sender: scubafuchs@gmail.com Received: by 10.68.6.8 with HTTP; Mon, 12 Dec 2011 14:13:49 -0800 (PST) In-Reply-To: References: Date: Mon, 12 Dec 2011 17:13:49 -0500 X-Google-Sender-Auth: SlHWFB8M2kiIYNWAq8X7OTW8tb8 Message-ID: Subject: Re: Upgrade from 1.3.5 to 1.4? From: Adam Fuchs To: accumulo-user@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c820f942c104b3ec725f X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1c820f942c104b3ec725f Content-Type: text/plain; charset=ISO-8859-1 Hi Trevor, The Accumulo 1.3.x to Accumulo 1.4.x upgrade is as simple as shutting down the 1.3 instance, copying the 1.3 configuration into a 1.4 distribution, and then starting the 1.4 instance. We've tested this upgrade mechanism a fair bit, but we will probably do some more testing before releasing 1.4. One caveat is that you cannot safely go back to 1.3 after you've run with 1.4 code on the same instance. Cheers, Adam On Mon, Dec 12, 2011 at 4:30 PM, Trevor Adams wrote: > Hey, > > I was just wondering what the procedure is for upgrading from 1.3 to 1.4. > I know there is JIRA for creating a script to do the upgrade but if someone > wanted to give it a whirl with a large set of data? > > Is it as simple as setting the dfs.local.dir to the one used by 1.3 and > start 1.4? (I doubt it but hey, why not) > > > -Trevor > --e89a8ff1c820f942c104b3ec725f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Trevor,

The Accumulo 1.3.x to Accumulo 1.4.x upgrade = is as simple as shutting down the 1.3 instance, copying the 1.3 configurati= on into a 1.4 distribution, and then starting the 1.4 instance. We've t= ested this upgrade mechanism a fair bit, but we will probably do some more = testing before releasing 1.4. One caveat is that you cannot safely go back = to 1.3 after you've run with 1.4 code on the same instance.

Cheers,
Adam



On Mon= , Dec 12, 2011 at 4:30 PM, Trevor Adams <trevoradams@gmail.com> wrote:
=
Hey,

I was just wondering what the procedure is for upgrading from 1= .3 to 1.4. I know there is JIRA for creating a script to do the upgrade but= if someone wanted to give it a whirl with a large set of data?

Is it as simple as setting the dfs.local.dir to the one used by 1.3 and sta= rt 1.4? (I doubt it but hey, why not)


-Trevor

--e89a8ff1c820f942c104b3ec725f--