accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Wall <mjw...@gmail.com>
Subject Re: Accumulo upgrade rollback...
Date Tue, 06 Jun 2017 12:42:17 GMT
Hi Bob,

Unfortunately, rolling back an upgraded system is not an automated task.
Moving from 1.5.4 to 1.6.6 as you saw !METADATA changed to
accumulo.metadata and accumulo.root.  The upgrade also changes the data
version of the rfiles, so any new files written from mutations or
compactions will not be readable by prior versions.  Good for you that you
saved off the /accumulo directory in HDFS.

What you are going to need to do is reinitialize Accumulo, create the
tables with whatever splits and configs you need, then bulk import the
rfiles from your /accumulo_backup directory in the new tables.  That will
make the metadata and zookeeper happy.  You can follow the directions for a
Zookeeper failure at
http://accumulo.apache.org/1.8/accumulo_user_manual.html#zookeeper_failure.

Interested in what you are seeing that made you want to rollback.  If you
are testing, you may want to try upgrading to the latest 1.8, which is
currently 1.8.1.

Let us know how it goes.

Mike



On Tue, Jun 6, 2017 at 2:25 AM Robert Rosekrans <
robert.rosekrans@inovexcorp.com> wrote:

>
> Accumulo team,
>
> Our team is upgrading from Accumulo 1.5.4 to 1.6.6 then to 1.7.3.  We are
> testing the upgrade in our integration environment. Before we started the
> upgrade, we copied our HDFS /accumulo directory to /accumulo_backup. My
> hope was that I could just swap out the directories to rollback. However
> when I did, the metadata table didn't load. I looked at the tables and the
> metadata table was listed as "metadata" versus "!METADATA" indicating it
> was using the new format of the tables.  My guess is that zookeeper is
> maintaining the previous upgraded table names.
>
> My question is what is the easiest way to rollback the data.
>
> Thanks
> Bob
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message