Fix logic in the code when setReadOnly(false) changes to a writer which causes a failover event. #426
Assignees
Labels
bug
Something isn't working
Comments
sergiyvamz
added a commit
that referenced
this issue
May 3, 2023
### Summary Fix issue with connection state transfer ### Description While switching from read-only connection to a writer connection (for instance, when calling connection.setReadOnly(false) on a connection to replica), transfer session state code raises an exception and that triggers a failover process rather than regular connecting process to a writer. #426 ### Additional Reviewers @karenc-bq @aaron-congo ### By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. Co-authored-by: sergiyv-bitquill <[email protected]>
sergiyvamz
added a commit
that referenced
this issue
May 3, 2023
### Summary Remove logic that changes connection to a writer when setReadOnly(false) is called on reader connection. #426 ### Additional Reviewers @karenc-bq @aaron-congo ### By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. Co-authored-by: sergiyv-bitquill <[email protected]>
|
Fixes were merged and released in version 2.1.0 through PR #427, we will be closing this ticket now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: