[CONTROLLER-1099] Clustering : Do not allow config subsystem to proceed till datastore is ready Created: 14/Jan/15 Updated: 25/Jul/23 Resolved: 30/Mar/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Moiz Raja |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2584 |
| Priority: | High |
| Description |
|
Today the CDS instance creation goes through even when the datastore is not ready. This allows the broker that depends on the datastore to move forward and allows applications to start creating transactions which may fail. It may be better to initially block the creation of the datastore till the Shard Leaders are elected so that we do not run into transaction creation problems later on. Doing this will make applications using the CDS work similarly to when they work with the IMDS. |
| Comments |
| Comment by Moiz Raja [ 24/Feb/15 ] |
| Comment by Moiz Raja [ 25/Mar/15 ] |
|
This still does not work as expected. The initial state of all shards is Follower and because of that ShardManager always reports store state as ready even if the Follower is not really communicating with a Leader. |
| Comment by Moiz Raja [ 26/Mar/15 ] |