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: modules/project-docs/pages/sdk-release-notes.adoc
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,39 @@ For release notes, download links, and installation methods for 2.7 and earlier
15
15
16
16
The full installation instructions that were previously on this page can now be found xref:sdk-full-installation.adoc[here].
17
17
18
+
== Version 3.3.1 (29 April 2022)
19
+
20
+
Version 3.3.1 is the second release of the 3.2 series. It contains a single ticket (NCBC-3192) and is a re-release of 3.3.0 with (NCBC-3192) along with all of 3.3.0.
* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
29
+
The solution is to either upgrade to 3.2.9 or greater, or to quiesce application processing so there are no writes until you have upgraded all nodes.
30
+
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
31
+
32
+
=== Fixed Issues
33
+
34
+
* https://issues.couchbase.com/browse/NCBC-2543[NCBC-3192]: Erroneous InvalidArgumentException with default TLS settings
35
+
18
36
== Version 3.3.0 (27 April 2022)
19
37
20
-
Version 3.3.0 is the first release of the 3.3 series.
38
+
Version 3.3.0 is the first release of the 3.3 series (delisted from NuGet 4/28/2022).
* Do not use; use 3.3.1 instead due to NCBC-3192 which impacts TLS/SSL.
47
+
48
+
* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
49
+
The solution is to either upgrade to 3.2.9 or greater, or to quiesce application processing so there are no writes until you have upgraded all nodes.
50
+
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
0 commit comments