You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2013/07/22 15:20:48 UTC

[jira] [Commented] (ACCUMULO-1591) Upgrading Accumulo with different zookeeper secret causes issues

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

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

One possible way to avoid this problem is to make Accumulo server processes all try to read a certain zookeeper node and halt if they can not.  So if node X can not be read, then do not write anything to zookeeper. 

[~vines], will this solution work w/ Curator?  

Depending on the solution we come up with for this problem, it may be worth porting to 1.4 and 1.5.
                
> 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