zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ZOOKEEPER-5) Upgrade Feature in Zookeeper server.
Date Thu, 16 Oct 2008 23:48:44 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Patrick Hunt updated ZOOKEEPER-5:

    Status: Open  (was: Patch Available)

In general I'm +1 on this patch with the following changes:

1) update Upgrade.main to catch any exception (throwable?) and log it before exiting. This
will ensure we have the issue captured in the log.
2) log the creation of directories, coping of files... renaming, etc...
3) log the various stages of the "runUpgrade" method, ie aftereach step log success of step.

I can't tell you how many times I've run into cases where an upgrade fails and having this
type if information (being able to determine with finer granularity what is happening for
the customer) would be useful.

I would also suggest that you change Upgrade.java to UpgradeMain.java to be consistent w/
the rest of the main utils in zk core.

> Upgrade Feature in Zookeeper server.
> ------------------------------------
>                 Key: ZOOKEEPER-5
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-5
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>             Fix For: 3.0.0
>         Attachments: log.100000001, log.100001bf0, snapshot.100000000, snapshot.100001bec,
ZOOKEEPER-5.patch, ZOOKEEPER-5.patch, ZOOKEEPER-5.patch, ZOOKEEPER-5.patch, ZOOKEEPER-5.patch
> We need an upgrade feature in zookeeper where we can upgrade the old databases to a new

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message