Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.1.0, 1.2.0, 1.2.4
-
None
-
Security Level: Public
-
None
Description
I have found with a single valid IP in the list it works as expected when using 2 other invalid URIs also in the list, but fails consistently when using 3 invalid URIs preceding the valid IP. If the valid IP is listed first, it looks to always work. So URI position in the list looks to make a difference.
Succeeds:
couchbase.Couchbase.connect(bucket='beer-sample', host=[ '1.1.1.2', '1.1.1.3','172.31.44.xxx']).get('21st_amendment_brewery_cafe').success
true
Fails:
couchbase.Couchbase.connect(bucket='beer-sample', host=['1.1.1.1', '1.1.1.2', '1.1.1.3','172.31.44.xxx]).get('21st_amendment_brewery_cafe').success
timeout exception
I am using Python2.6 and Couchbase client version 1.2.4
There does look to be an issue when passing in invalid/inactive nodes with the Python SDK. This affects customers who have the Python client, but one or more of their nodes listed in the URI list are not available. The expectation is that the client should quickly identify and use a valid IP in the list for bootstrapping.