accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3002) Handle instance.volumes in upgrade
Date Wed, 07 Jan 2015 17:40:35 GMT

    [ 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)

Mime
View raw message