accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2918) TServers expect zookeeper to have parent nodes created
Date Tue, 17 Jun 2014 23:43:14 GMT


ASF subversion and git services commented on ACCUMULO-2918:

Commit 672801c154362a1aa870ae52439e5f9b81f42c04 in accumulo's branch refs/heads/master from
[;h=672801c ]

ACCUMULO-2918 Pay the penalty of embedding ZK hierarchy manipulation to avoid creating an
upgrade path.

In a fresh 1.7.0 instance, this isn't an issue because {{accumulo init}} will create the necessary
parent nodes in ZooKeeper. However, for upgrades from 1.6 or 1.7 installs that were created
before the replication code was merged, the tserver will error out because the parent ZK nodes
do not exist (and ZK will not automatically create them).

While it's not ideal to embed this logic in the server processes, it's the better alternative
to create an upgrade path, because one does not yet exist.

> TServers expect zookeeper to have parent nodes created
> ------------------------------------------------------
>                 Key: ACCUMULO-2918
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: replication
>         Environment: starting up 1.7.0 after replication was commited
>            Reporter: Eric Newton
>            Assignee: Josh Elser
>             Fix For: 1.7.0
> replication needs some upgrade code to make some nodes in zookeeper
> Here's the error message:
> {noformat}
> KeeperErrorCode = NoNode for /accumulo/2f3173c3-c02f-4e3a-b01c-7f721d4a9f00/replication/tservers/host:9997
> {noformat}

This message was sent by Atlassian JIRA

View raw message