[JCBC-138] Java Client does not recover when only bootstrap node provided and failovered Created: 05/Nov/12  Updated: 16/Dec/13  Resolved: 16/Dec/13

Status: Resolved
Project: Couchbase Java Client
Component/s: Core
Affects Version/s: None
Fix Version/s: 1.2
Security Level: Public

Type: Improvement Priority: Major
Reporter: Michael Nitschinger Assignee: Michael Nitschinger
Resolution: Fixed Votes: 0
Labels: unibrow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks JCBC-308 Trouble in resubscribing to primary n... Closed
blocks JCBC-344 allow for setting bootstrap nodes via... Resolved

Within the current implementation, when the bootstrap node is failovered/removed (and only that one is provided in the list) it gets correctly removed from the SDK, but either a new try to get a different streaming connection fails or something else is wrong.

Even when the node is added back into the cluster no new view connection is created (most arguably because no map updates are received anymore).

This issue may also be the cause for other bugs related to failover scenarios reported.

Comment by Michael Nitschinger [ 19/Jul/13 ]
This is how it will work in the 1.1 series. if we decide for changes in the 1.2 branch (CCCP), then this will change as well. For now wont fix.
Comment by Michael Nitschinger [ 04/Sep/13 ]
Generated at Thu Dec 18 08:45:50 CST 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.