accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1591) Upgrading Accumulo with different zookeeper secret causes issues
Date Mon, 22 Jul 2013 14:52:49 GMT

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

John Vines commented on ACCUMULO-1591:
--------------------------------------

Curator basically provides a wrapper which simplifies a lot of calls with auto retries, etc.
as well as a bunch of recipes for common actions, such as distirbuted locks, distributed atomic
values, and caching, among others. So anything that will work with vanilla ZK will work with
Curator. I can't think of a better solution, but TBH I'm having issues understanding the problem
at hand. Wouldn't it make more sense to just make the update do all updates as a single transaction?
                
> 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