[CONTROLLER-842] Clustering : On recovery all replicated log entries should not be applied to state Created: 16/Sep/14 Updated: 18/Sep/14 Resolved: 18/Sep/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Kamal Rameshan |
| 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: | 1903 |
| Priority: | High |
| Description |
|
On recovery we immediately apply all replicated log entries to state. This is incorrect as some of those entries may not have been applied to state during the normal course of operation (for example if a leader did not get consensus on it). We need to separately keep track of which entry was applied to state in the journal and only apply those to the state during recovery. |
| Comments |
| Comment by Moiz Raja [ 18/Sep/14 ] |