[SXP-148] Shard leader is not elected after leader isolation and its re-run Created: 14/Sep/18 Updated: 28/Jan/19 Resolved: 28/Jan/19 |
|
| Status: | Resolved |
| Project: | sxp |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Ivan Hrasko | Assignee: | Ivan Hrasko |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | SXP Clustering bugs |
| Description |
|
Shard sync status is false on one of the cluster members or new leader is not elected.
It looks that it can be partially solved by waiting until cluster re-synchronizes again. There is a risk that we are facing controller clustering bugs. |
| Comments |
| Comment by Ivan Hrasko [ 17/Jan/19 ] |
|
Using of tell-based protocol does not help. |
| Comment by Ivan Hrasko [ 21/Jan/19 ] |
|
Debugging controller and mdsal clustering to discover root cause if cluster failures. |
| Comment by Ivan Hrasko [ 28/Jan/19 ] |
|
Owner is not elected - https://github.com/akka/akka/issues/24764 |