Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Bootstrap should continue after AuthenticationFailureException
Description
Create a cluster of 3 nodes
Remove or failover the first node
Start application with the removed node in the connection string
An AuthenticationFailureException will be thrown and the SDK will fail to use the next node in the connection string.
The SDK should continue attempting to bootstrap using the next node in the connection string only failing when attempts on all nodes have failed.
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
Jeffry Morris July 25, 2022 at 11:49 PM
Edited
It appears that this is a regression introduced in https://couchbasecloud.atlassian.net/browse/NCBC-3000#icft=NCBC-3000. The server does return an auth_error response as the node that has been removed no longer can be authenticated against the former credentials as it has been "reset" back to its original state.
The client must continue to authenticate when this happens using any other configured nodes. That is the bug; the client throws an AuthenticationException here and breaks out of the auth loop instead of trying the next node.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Create a cluster of 3 nodes
Remove or failover the first node
Start application with the removed node in the connection string
An AuthenticationFailureException will be thrown and the SDK will fail to use the next node in the connection string.
The SDK should continue attempting to bootstrap using the next node in the connection string only failing when attempts on all nodes have failed.