Time
S
Nick
Message
00:15 dataverse-user joined #dataverse
02:33 poikilotherm joined #dataverse
06:10 PatrickV joined #dataverse
06:32 Virgile joined #dataverse
08:32 PatrickV joined #dataverse
08:42 pvranckx joined #dataverse
09:33 pvranckx
Could someone help me with an upgrade ?
11:27 pvranckx joined #dataverse
11:48 donsizemore joined #dataverse
12:19 Virgile joined #dataverse
12:43 pvranckx joined #dataverse
12:49 donsizemore
@pvranckx welcome back - what's going on with your upgrade?
12:57 pvranckx
Our server runs the initial version of dataverse 4.14. I'm trying to test the upgrade path to 5.
12:57 pvranckx
I set up a new server with the same version and restored a backup of the production data.
12:58 pvranckx
When I upgrade to 4.15 and 4.15.1, I get a lot of warnings regarding the database.
12:58 pvranckx
The same from 4.15.1 to 4.16
12:58 donsizemore
any warning ending with "already exists" may likely be safely ignored. other warnings... tell me what they are?
13:00 pvranckx
OK. Most of the errors are ...already exists... expected this one:
13:00 pvranckx
PER01000: Got SQLException executing statement "INSERT INTO SEQUENCE(SEQ_NAME, SEQ_COUNT) values ('SEQ_GEN', 0)": org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "sequence_pkey"
13:01 donsizemore
do all of these happen at deployment?
13:01 pvranckx
Yes.
13:01 donsizemore
(and more importantly, are there SQL errors in server.log after you've restarted Glassfish as the last step of the upgrade?)
13:03 pvranckx
looking on the server...
13:06 donsizemore
unless you find SQL errors in server.log ongoing, they're probably fine.
13:11 donsizemore
what's your target version? (just curious)
13:11 pvranckx
I find exactely the same error in server.log
13:12 pvranckx
I'd like to setup a new server, install dataverse 5, and migrate the data on it
13:13 pvranckx
BTW I find information in the docs on how to upgrade but few on how to restore or migrate from one server to another
13:14 donsizemore
Dataverse uses flyway since 4.12/13(?) so in theory you could set up a clean 5.0, import the DB into it, and redeploy the warfile. On a test server first, for sure, and @pdurbin may suggest a better path
13:14 pvranckx
Till now, I setup a new instance of dataverse with ansible, synchronize the storage between to S3 buckets, export and import a dump pf the pgsql database (after renaming the bucket name)
13:15 pvranckx
Is there a way to logically export the data and reimport it in an empy dataverse instance ?
13:16 pvranckx
AFAIK, I need to do all the upgrades sequentially from 4.14 to 5 because there are schema updates between versions. Is it correct ?
13:17 donsizemore
the DB and the filesystem/S3 bucket aren't necessarily linked. you could migrate the DB and point it at the same S3 bucket assuming you wouldn't make further modifications from the old server
13:17 pvranckx
Correct. But what about schema modifications between intermediate versions ?
13:18 donsizemore
Stefan Kasberger did an all-in-one upgrade from some older version to a later 4.1n release successfully, but I have too many grey hairs to attempt that myself. I'd step through each upgrade, personally.
13:19 pvranckx
That's what I plan to do... but I get errors from the first upgrade 4.14 -> 4.15...
13:22 donsizemore
those same duplicate errors, or different errors?
13:23 pvranckx
those ones.
13:24 pvranckx
I will go one this afternoon with the upgrades and see if I have other errors.
13:24 pvranckx
btw is there any doc on how to use flyway to migrate the dataverse db ?
13:30 donsizemore
flyway handles it for you
13:31 donsizemore
and i'm juggling a few tasks, if you will, give me a moment to ask the experts about any better upgrade path.
13:42 donsizemore
crickets all around. if and when i do hear back i'll let you know.
13:49 pvranckx
Perfect. Thank you !
14:10 donsizemore
@pvranckx: @pdurbin has nearly as many grey hairs as I: "I’m scared enough that I’d probably do step by step but yes, the upgrade script works fine, it seems."
14:12 pvranckx
OK. So I will go on will sequential upgrades.
14:15 pdurbin
pvranckx: either way, do a backup. :)
14:16 pvranckx
Of course ! I do that on a test server.
14:17 pdurbin
In practice, you need to read all the release notes anyway because sometimes there are extra steps to take.
14:18 pdurbin
I realize we could do a better job making upgrades easier. And like you said, we don't really have a concept of backup/export and then restore.
14:19 pdurbin
At least with Flyway (thank you, contributors!), you don't have to run database upgrade scripts manually anymore. They get executed when you deploy the war file.
14:19 donsizemore
"All you need is [the DB ]" - J. Lennon, P. McCartney
14:19 pdurbin
:)
14:27 donsizemore
@pvarnckx @pdurbin would it be worth documenting a proposed upgrade process in such case? (thinking Hacktoberfest t-shirt)
14:36 pvranckx67 joined #dataverse
15:53 dataverse-user joined #dataverse
16:58 pdurbin
donsizemore: please keep talkin'. I'm not sure I get it.
16:58 donsizemore
maybe a general outline of an upgrade process over multiple versions? compare/contrast paths
16:59 donsizemore
old skool: diligently step through versions. new skool: clean install and DB import, but list of config changes to watch out for? i suppose this is all in each set of release artifacts anyway
17:00 pdurbin
I'm glad we have enough installations out there to consider this. :)
17:28 donsizemore
i suggested similar "fuzzy" guidelines for the iRODS project but they responded that each installation was a snowflake and so it would be difficult to compose instructions for a majority of installations
17:28 donsizemore
but the essential components and design of Dataverse are much more homogenous
17:28 donsizemore
or predictable, I should say.
17:31 pdurbin
mostly monolithic
