Details
Description
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.
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.
Activity
Michael Nitschinger
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Java client does not recover when the bootstrap node is removed/failovered | Java Client does not recover when only bootstrap node provided and failovered |
| Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
| Fix Version/s | 1.1-dp5 [ 10410 ] | |
| Fix Version/s | 1.1-dp4 [ 10390 ] | |
| Affects Version/s | 1.1-dp4 [ 10390 ] | |
| Description |
Within the current implementation, when the bootstrap node is failovered/removed 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. |
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. |
Michael Nitschinger
made changes -
| Priority | Blocker [ 1 ] | Major [ 3 ] |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.1 [ 10430 ] | |
| Fix Version/s | 1.1-dp5 [ 10410 ] |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.2 [ 10480 ] | |
| Fix Version/s | 1.1.1 [ 10430 ] |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.3 [ 10496 ] | |
| Fix Version/s | 1.1.2 [ 10480 ] |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.4 [ 10514 ] | |
| Fix Version/s | 1.1.3 [ 10496 ] |
Michael Nitschinger
made changes -
| Planned Start | (set to new fixed version's start date) | |
| Planned End | (set to new fixed version's start date) |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.5 [ 10515 ] | |
| Fix Version/s | 1.1.4 [ 10514 ] |
Michael Nitschinger
made changes -
| Planned Start | (set to new fixed version's start date) | |
| Planned End | (set to new fixed version's start date) |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.6 [ 10531 ] | |
| Fix Version/s | 1.1.5 [ 10515 ] |
Michael Nitschinger
made changes -
| Fix Version/s | 1.1.7 [ 10532 ] | |
| Fix Version/s | 1.1.6 [ 10531 ] |