You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,27 @@ All notable changes to this project will be documented in this file.
3
3
4
4
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/#semantic-versioning-200).
5
5
6
+
## [2.1.0] - 2023-5-11
7
+
### :magic_wand: Added
8
+
-`AuroraHostListProvider` to check for stale writer records obtained after writer-failover so that they are not used ([PR #435](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/435)).
9
+
10
+
### :bug: Fixed
11
+
- Potential security concern by ensuring that user specific connections in the connection pool are returned to the correct user ([PR #432](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/432)).
12
+
- Connection state transfer bug where switching from read-only connection to writer connection incorrectly triggers the failover process ([Issue #426](https://github.com/awslabs/aws-advanced-jdbc-wrapper/issues/426)).
13
+
- Incorrect invalidation of newly promoted writer and random readers after failover. EFM plugin to use instance endpoint as the monitoring endpoint in the case the initial connection is established using cluster endpoint ([PR #431](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/431)).
- Reader failover using shared Properties object resulting in race conditions ([PR #436](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/436) & [PR #438](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/438)).
16
+
- Temporarily set socket timeout for the topology query if it is not set, to avoid topology query from executing indefinitely ([PR #416](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/416)).
17
+
18
+
### :crab: Changed
19
+
- Removed logic that changes connection to a writer instance when `setReadOnly(false)` is called on a reader connection ([Issue #426](https://github.com/awslabs/aws-advanced-jdbc-wrapper/issues/426)).
20
+
- Removed Multi-writer cluster related code as they are no longer supported ([PR #435](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/435)).
21
+
- Clarified documentation on failover process to account for Aurora PostgerSQL clusters being offline during failover ([PR #437](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/437)).
22
+
-:warning: Breaking changes were introduced with the new `failoverMode` configuration parameter ([PR #434](https://github.com/awslabs/aws-advanced-jdbc-wrapper/pull/434)):
23
+
- The `failoverMode` parameter replaces the `enableFailoverStrictReader` configuration parameter.
24
+
- If you were previously using `enableFailoverStrictReader=true`, please update it to `failoverMode=strict-reader`.
25
+
- For more information, please check the ([documentation](https://github.com/awslabs/aws-advanced-jdbc-wrapper/blob/main/docs/using-the-jdbc-driver/using-plugins/UsingTheFailoverPlugin.md#failover-parameters))
0 commit comments