accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2148) Verify upgrade 1.5 to 1.6 works
Date Sat, 05 Apr 2014 00:01:23 GMT

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

Josh Elser commented on ACCUMULO-2148:
--------------------------------------

bq. I could maybe explain that the 1.4 to 1.5 upgrade process asynchronously handled migrating
1.4 write ahead logs and that 1.6 can no longer make retries?

I think that would be a good idea. Perhaps a disclaimer that those successfully running 1.5
upgraded from 1.4 don't need to perform the verification of no local WALs, too.

bq. I did mean "table metadata". We write into multiple tables as a part of the upgrade, not
just into the reserved metadata table. (the new reserved root, for example)

Oh I see. What about  ".. in both ZooKeeper and the Accumulo system tables."  instead? That
would match nomenclature better I believe.

> Verify upgrade 1.5 to 1.6 works
> -------------------------------
>
>                 Key: ACCUMULO-2148
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2148
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-2148.1.patch.txt, ACCUMULO-2148.2.patch.txt
>
>
> Need to verify that 1.6.0 release candidate can upgrade from 1.5.0



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message