Details
Description
Attempting to open a bucket which does not exist causes the SDK to fail to connect and operations are cancelled with 'cluster object was closed' as opposed to continuing to retry the connection and then timing out the operation if it fails to connect in time.
Attachments
Issue Links
- blocks
-
JSCBC-752 WaitUntilReady() doc code sample
- Open
- depends on
-
CCBC-1200 lcb_connect does not retry on bucket missing error
- Resolved
-
CCBC-1384 Operation dispatch should be permitted before connect completes
- Resolved
- duplicates
-
JSCBC-738 Connection fails randomly
- Resolved
- is duplicated by
-
JSCBC-837 SDK nodejs 3.1.1 - cluster closed OR program not ending OR program stopping with no reason
- Resolved
-
JSCBC-852 Cluster object has been closed error doesn't give enough information back to the user
- Resolved
- relates to
-
CCBC-1288 LCB does not time out ops when lcb_open still in progress
- Open
-
JSCBC-843 Improve Getting Started example
- Open