[Archivesspace_Users_Group] Issue with 2.1.0 upgrade

Galligan, Patrick PGalligan at rockarch.org
Mon Aug 7 09:52:14 EDT 2017


I don’t know if it was our server running slow or something, but I just tested our first initial upgrade to 2.1.0 from 2.0, and the indexing took almost a full week. In the past it used to take 36-48 hours and we could be done over the weekend.

I think I’d like to test everything again before conclusively saying that’s how long it takes, but it seemed like a drastic increase in time.

-Patrick Galligan

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Christine Di Bella <christine.dibella at lyrasis.org>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, August 4, 2017 at 5:26 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with 2.1.0 upgrade

Hi Dale,

Just to let you know, the ArchivesSpace team is looking into this and a few other reports about performance or difficulty indexing when upgrading to 2.1.0. We hope to have more information soon, though so far these are somewhat isolated incidents. We’re definitely interested to hear if others are having similar experiences when upgrading to 2.1.0.

We do know that the initial indexing period takes longer with 2.1.0, and we know of at least one institution that need to do a small amount of data cleanup because some bad data that was ignored in previous versions was preventing indexing from completing.


Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
cdibella13 (Skype)


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Poulter, Dale
Sent: Tuesday, August 1, 2017 8:37 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Issue with 2.1.0 upgrade

Good evening,

We upgraded from 2.0.1 to 2.1.0 earlier today.  The upgrade appeared to go well with no errors generated during the database setup stage.  However,  it still seems to be generating many calls to the database.  Is this expected behavior? When we upgraded to 2.0.1 the we had similar behavior but that only lasted for an hour or less.

Thank you for your help!


Dale Poulter
Coordinator, Search and Core Services
Library Digital Services
Vanderbilt University
419 21st Avenue South, Room 812
Nashville, TN  37203-2427
(615)207-9705 (cell)
dale.poulter at vanderbilt.edu<mailto:dale.poulter at vanderbilt.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170807/d50910f2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23340 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170807/d50910f2/attachment.png>

More information about the Archivesspace_Users_Group mailing list