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 1467C10F9E for ; Fri, 19 Dec 2014 20:59:14 +0000 (UTC) Received: (qmail 67094 invoked by uid 500); 19 Dec 2014 20:59:14 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 67055 invoked by uid 500); 19 Dec 2014 20:59:14 -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 66926 invoked by uid 99); 19 Dec 2014 20:59:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 20:59:13 +0000 Date: Fri, 19 Dec 2014 20:59:13 +0000 (UTC) From: "Josh Elser (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=14254012#comment-14254012 ] Josh Elser commented on ACCUMULO-3002: -------------------------------------- Is that to be interpreted that you can't reproduce the issue, [~kturner]? Are you still looking into this for 1.6.2, and, if so, do you know of something that needs to be done? > 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 > Priority: Blocker > Fix For: 1.6.2, 1.7.0 > > > 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)