[CONTROLLER-871] Clustering: Make shard persistence configurable per data store Created: 20/Sep/14 Updated: 14/Oct/14 Resolved: 14/Oct/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tom Pantelis | Assignee: | Tom Pantelis |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 1996 | ||||||||
| Description |
|
Currently shard persistence is enabled by default and can be controlled globally via the shard.persistent system property. A system property isn't ideal plus there may be use cases for disabling persistence for just the operational store. So we need to make persistence configurable per data store via the config yang. |