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-1591) Upgrading Accumulo with different zookeeper secret causes issues
Date Mon, 22 Jul 2013 15:02:49 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715264#comment-13715264
] 

Keith Turner commented on ACCUMULO-1591:
----------------------------------------

Here is a more detailed scenario that describes the problem

 # User installs 1.4.1
 # User edits accumulo-site.xml and sets the secret to X
 # User shuts down 1.4.1 
 # User installs 1.4.2
 # Secret is not set in accumulo-site.xml and therefore reverts to default
 # User starts 1.4.2
 # 1.4.2 starts writes some zookeeper nodes using the default secret
 # 1.4.2 is unable to read nodes written using the secret X
 # 1.4.2 instance will not start up completely
 # User kills 1.4.2 instance
 # User edits accumulo-site.xml and sets the secret to X
 # 1.4.2 still does not start properly because it can not read the nodes written with the
default secret
 # User has to go into zookeeper and fix things

                
> Upgrading Accumulo with different zookeeper secret causes issues
> ----------------------------------------------------------------
>
>                 Key: ACCUMULO-1591
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1591
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> A user ran into an issue where they upgraded Accumulo from 1.4.x to 1.4.y.  During the
process they changed the zookeeper password.  This resulted in different nodes in zookeeper
with different auths and which prevent Accumulo from working properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message