-
Notifications
You must be signed in to change notification settings - Fork 535
8947 Update to Payara 5.2022.3 #8949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
41c8f61
db4e82c
b6a502f
46f6066
71e4912
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,76 @@ | ||
| # Update to Payara 5.2022.3 highly recommended | ||
|
|
||
| *NOTE: this might be rephrased to "required" depending on https://github.com/IQSS/dataverse/pull/8915 being merged.* | ||
|
|
||
| With lots of bug and security fixes included, we encourage everyone to update to Payara 5.2022.3 as soon as possible. | ||
|
|
||
| **Note:** with the approaching EOL for the Payara 5 Community release train it's likely we will switch to a | ||
| yet-to-be-released Payara 6 in the not-so-far-away future. | ||
|
|
||
| We recommend you ensure you followed all update instructions from the past releases regarding Payara. | ||
| (latest Payara update was for [v5.6](https://github.com/IQSS/dataverse/releases/tag/v5.6)) | ||
|
|
||
| Upgrading requires a maintenance window and downtime. Please plan ahead, create backups of your database, etc. | ||
|
|
||
| The steps below are a simple matter of reusing your existing domain directory with the new distribution. | ||
| But we also recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting: | ||
| [Payara Release Notes](https://docs.payara.fish/community/docs/Release%20Notes/Release%20Notes%205.2022.3.html) | ||
|
|
||
| If you are running Payara as a non-root user (and you should be!), remember not to execute the commands below as root. | ||
| Use `sudo` to change to that user first. For example, `sudo -i -u dataverse` if `dataverse` is your dedicated | ||
| application user. | ||
|
|
||
| In the following commands we assume that Payara 5 is installed in `/usr/local/payara5`. If not, adjust as needed. | ||
|
|
||
poikilotherm marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Please note that the deletion of the `lib/databases` directory below is only required once, for this upgrade (see Issue #8230 for details). | ||
|
|
||
| ```shell | ||
| export PAYARA=/usr/local/payara5 | ||
| ``` | ||
|
|
||
| (or `setenv PAYARA /usr/local/payara5` if you are using a `csh`-like shell) | ||
|
|
||
| 1. Undeploy the previous version | ||
|
|
||
| ```shell | ||
| $PAYARA/bin/asadmin list-applications | ||
| $PAYARA/bin/asadmin undeploy dataverse<-version> | ||
| ``` | ||
|
|
||
| 2. Stop Payara | ||
|
|
||
| ```shell | ||
| service payara stop | ||
| rm -rf $PAYARA/glassfish/domains/domain1/generated | ||
| rm -rf $PAYARA/glassfish/domains/domain1/osgi-cache | ||
| rm -rf $PAYARA/glassfish/domains/domain1/lib/databases | ||
| ``` | ||
|
|
||
| 3. Move the current Payara directory out of the way | ||
|
|
||
| ```shell | ||
| mv $PAYARA $PAYARA.MOVED | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where does PAYARA.MOVED get set/exported?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh this was just copy-pasta from the v5.6 instructions. The shell expansion will stop at the ".", so if |
||
| ``` | ||
|
|
||
| 4. Download the new Payara version (5.2022.3), and unzip it in its place | ||
|
|
||
| 5. Replace the brand new payara/glassfish/domains/domain1 with your old, preserved domain1 | ||
|
|
||
| 6. Start Payara | ||
|
|
||
| ```shell | ||
| service payara start | ||
| ``` | ||
|
|
||
| 7. Deploy this version. | ||
|
|
||
| ```shell | ||
| $PAYARA/bin/asadmin deploy dataverse-5.12.war | ||
| ``` | ||
|
|
||
| 8. Restart payara | ||
|
|
||
| ```shell | ||
| service payara stop | ||
| service payara start | ||
| ``` | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| #!/bin/sh | ||
| curl -L -O https://s3-eu-west-1.amazonaws.com/payara.fish/Payara+Downloads/5.2021.6/payara-5.2021.6.zip | ||
| curl -L -O https://s3-eu-west-1.amazonaws.com/payara.fish/Payara+Downloads/5.2022.3/payara-5.2022.3.zip | ||
| curl -L -O https://archive.apache.org/dist/lucene/solr/8.11.1/solr-8.11.1.tgz | ||
| curl -L -O https://search.maven.org/remotecontent?filepath=org/jboss/weld/weld-osgi-bundle/2.2.10.Final/weld-osgi-bundle-2.2.10.Final-glassfish4.jar | ||
| curl -s -L http://sourceforge.net/projects/schemaspy/files/schemaspy/SchemaSpy%205.0.0/schemaSpy_5.0.0.jar/download > schemaSpy_5.0.0.jar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expect others will want to wordsmith the release notes more, but I'll note that we should probably not make this optional - while I think v5.12 will be compatible with earlier versions, after this PR we're not testing that anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I absolutely agree!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pdurbin WDYT - should we make a bold statement? (Especially as it seems to be another good reason to update because of #8823)