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
* 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
26
32
27
=== Fixed Issues
33
28
34
-
* https://issues.couchbase.com/browse/NCBC-2543[NCBC-2543]: QueryIndexManager fails to create indexes in Linq2Couchbase integration tests
35
-
36
-
* https://issues.couchbase.com/browse/NCBC-2847[NCBC-2847]: AuthenticationFailureException is suppressed if invalid credentials are supplied
37
-
38
-
* https://issues.couchbase.com/browse/NCBC-3054[NCBC-3054]: DependencyInjection tests fail due to Moq with .NET 5.0 and 6.0
39
-
40
-
* https://issues.couchbase.com/browse/NCBC-3115[NCBC-3115]: EventingFunctionManager GetFunctionAsync throws generic HttpRequestException on error
41
-
42
-
* https://issues.couchbase.com/browse/NCBC-3123[NCBC-3123]: BucketNotFoundException thrown when Cluster.BucketAsync fails
Made it simpler to diagnose failures by ensuring that various exceptions including `AuthenticationFailureException`, `BucketNotFoundException`, `EventingFunctionNotFoundException`, FTS exceptions, `ScopeNotFoundException`, `BucketExistsException`, `AuthenticationFailedException` are correctly thrown.
* 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.
97
-
The solution is to either upgrade to 3.2.9, or to quiesce application processing so there are no writes until you have upgraded all nodes.
95
+
The solution is to either upgrade to 3.2.9, or to pause application processing so there are no writes until you have upgraded all nodes.
98
96
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
99
97
100
98
* Between bug fixes and performance improvements, the `ChannelConnectionPool` will be made the default in a future release.
0 commit comments