Skip to content

Commit 8564ff6

Browse files
authored
Merge pull request #7319 from IQSS/7318-5.1.1-Release-Notes
5.1.1 Release Notes
2 parents 1b59dac + 49af197 commit 8564ff6

File tree

2 files changed

+59
-9
lines changed

2 files changed

+59
-9
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# Dataverse 5.1.1
2+
3+
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.
4+
5+
## Release Highlights
6+
7+
### Connection Pool Size Configuration Option, Connection Optimizations
8+
9+
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.
10+
11+
## Major Use Cases
12+
13+
Newly-supported use cases in this release include:
14+
15+
- 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)
16+
17+
## Notes for Dataverse Installation Administrators
18+
19+
### 5.1.1 vs. 5.1 for Production Use
20+
21+
As mentioned above, we encourage 5.1.1 instead of 5.1 for production use.
22+
23+
### New JVM Option for Connection Pool Size
24+
25+
Larger installations may want to increase the number of open S3 connections allowed (default is 256). For example, to set the value to 4096:
26+
27+
``./asadmin create-jvm-options "-Ddataverse.files.<id>.connection-pool-size=4096"`
28+
29+
The JVM Options section of the [Configuration Guide](http://guides.dataverse.org/en/5.1.1/installation/config/) has more information.
30+
31+
## Complete List of Changes
32+
33+
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.
34+
35+
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 [email protected].
36+
37+
## Installation
38+
39+
If this is a new installation, please see our [Installation Guide](http://guides.dataverse.org/en/5.1.1/installation/)
40+
41+
## Upgrade Instructions
42+
43+
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).
44+
45+
1. Undeploy the previous version.
46+
47+
<payara install path>/payara/bin/asadmin list-applications
48+
<payara install path>/payara/bin/asadmin undeploy dataverse
49+
50+
2. Stop payara and remove the generated directory, start.
51+
52+
- service payara stop
53+
- remove the generated directory: rm -rf <payara install path>payara/payara/domains/domain1/generated
54+
- service payara start
55+
56+
3. Deploy this version.
57+
<payara install path>/payara/bin/asadmin deploy <path>dataverse-5.1.1.war
58+
59+
4. Restart payara

doc/release-notes/7308-connection-pool-size.md

Lines changed: 0 additions & 9 deletions
This file was deleted.

0 commit comments

Comments
 (0)