Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Jeffry Morris
Jeffry MorrisReporter
Jeffry Morris
Jeffry MorrisStory Points
1
Components
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
Sentry
Sentry
Zendesk Support
Zendesk Support
Created March 31, 2022 at 11:09 PM
Updated April 5, 2022 at 5:30 PM
Resolved April 5, 2022 at 5:30 PM
Scenario: Mixed node upgrade (Enterprise Edition 6.6.3 build 9808 and Enterprise Edition 7.0.3 build 7032). First bootstrap to 6.6.3 and run a load. Then add 7.0.3 and hit rebalance; the server will not return the AlternateAddress for the 7.0.3 node.
During a rebalance of a cluster using alternate addresses, its possible for the server to not return an alternative address:
If the NRE is handled (check for null AlternateAddress) in the SDK, this is in turn leads up to NMVB being returned after rebalance completes:
If the application is then stopped and restarted, then bootstrapping fails with the following socket exception (because there is no alternate address to use for the second node "cb2.lan"):