Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2545EC23A for ; Wed, 7 Jan 2015 17:40:35 +0000 (UTC) Received: (qmail 45186 invoked by uid 500); 7 Jan 2015 17:40:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 45075 invoked by uid 500); 7 Jan 2015 17:40:35 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 44970 invoked by uid 99); 7 Jan 2015 17:40:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 17:40:35 +0000 Date: Wed, 7 Jan 2015 17:40:35 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3002) Handle instance.volumes in upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267930#comment-14267930 ] Keith Turner commented on ACCUMULO-3002: ---------------------------------------- bq. Is that to be interpreted that you can't reproduce the issue I can't reproduce exactly what happened and I can't remember exactly why the 1.6.0 release notes said not to set {{instance.volumes}} prior to upgrade. I think when I was deep in the weeds working on this stuff I noticed some really annoying case if {{instance.volumes}} is set during upgrade. However I can not remember the specifics. I think it would be good to not upgrade if set. > Handle instance.volumes in upgrade > ---------------------------------- > > Key: ACCUMULO-3002 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3002 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.6.0 > Reporter: Keith Turner > Assignee: Keith Turner > Priority: Blocker > Fix For: 1.6.2, 1.7.0 > > Attachments: ACCUMULO-3002-1.patch > > > A user configured instance.volumes before upgrading and ran into problems. The 1.6.0 release notes mention not to do this. However thats not really enough. Need to fix this issues or make the upgrade abort if instance.volumes is configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)