-
Notifications
You must be signed in to change notification settings - Fork 493
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' into 6919-preview-tools #6919
- Loading branch information
Showing
14 changed files
with
169 additions
and
67 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
# Dataverse 5.1.1 | ||
|
||
This minor release adds important scaling improvements for installations running on AWS S3. It is recommended that 5.1.1 be used in production instead of 5.1. | ||
|
||
## Release Highlights | ||
|
||
### Connection Pool Size Configuration Option, Connection Optimizations | ||
|
||
Dataverse 5.1 improved the efficiency of making S3 connections through use of an http connection pool. This release adds optimizations around closing streams and channels that may hold S3 http connections open and exhaust the connection pool. In parallel, this release increases the default pool size from 50 to 256 and adds the ability to increase the size of the connection pool, so a larger pool can be configured if needed. | ||
|
||
## Major Use Cases | ||
|
||
Newly-supported use cases in this release include: | ||
|
||
- Administrators of installations using S3 will be able to define the connection pool size, allowing better resource scaling for larger installations (Issue #7309, PR #7313) | ||
|
||
## Notes for Dataverse Installation Administrators | ||
|
||
### 5.1.1 vs. 5.1 for Production Use | ||
|
||
As mentioned above, we encourage 5.1.1 instead of 5.1 for production use. | ||
|
||
### New JVM Option for Connection Pool Size | ||
|
||
Larger installations may want to increase the number of open S3 connections allowed (default is 256). For example, to set the value to 4096: | ||
|
||
``./asadmin create-jvm-options "-Ddataverse.files.<id>.connection-pool-size=4096"` | ||
|
||
The JVM Options section of the [Configuration Guide](http://guides.dataverse.org/en/5.1.1/installation/config/) has more information. | ||
|
||
## Complete List of Changes | ||
|
||
For the complete list of code changes in this release, see the [5.1.1 Milestone](https://github.com/IQSS/dataverse/milestone/91?closed=1) in Github. | ||
|
||
For help with upgrading, installing, or general questions please post to the [Dataverse Google Group](https://groups.google.com/forum/#!forum/dataverse-community) or email support@dataverse.org. | ||
|
||
## Installation | ||
|
||
If this is a new installation, please see our [Installation Guide](http://guides.dataverse.org/en/5.1.1/installation/) | ||
|
||
## Upgrade Instructions | ||
|
||
0. These instructions assume that you've already successfully upgraded to Dataverse 5.1 following the instructions in the [Dataverse 5.1 Release Notes](https://github.com/IQSS/dataverse/releases/tag/v5.1). | ||
|
||
1. Undeploy the previous version. | ||
|
||
<payara install path>/payara/bin/asadmin list-applications | ||
<payara install path>/payara/bin/asadmin undeploy dataverse | ||
|
||
2. Stop payara and remove the generated directory, start. | ||
|
||
- service payara stop | ||
- remove the generated directory: rm -rf <payara install path>payara/payara/domains/domain1/generated | ||
- service payara start | ||
|
||
3. Deploy this version. | ||
<payara install path>/payara/bin/asadmin deploy <path>dataverse-5.1.1.war | ||
|
||
4. Restart payara |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.