[CONTROLLER-1404] Make persistence configurable at the Shard level Created: 18/Aug/15 Updated: 17/Nov/15 Resolved: 17/Nov/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Lithium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Moiz Raja | Assignee: | Tom Pantelis |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Currently we allow configuration of persistence only at the datastore level. In datastore.cfg you have the following configuration options. persistent=true Some people may want operational inventory to also be persisted. It would be nice if they could configure it like so in the datastore.cfg. operational.inventory.persistent=true This would override the persistence option for the inventory operational shard. |
| Comments |
| Comment by Tom Pantelis [ 18/Aug/15 ] |
|
We should also make any option configurable at the shard level as we do at the datastore level. I think we can add a DatastoreContext builder that takes a shard name that the ShardManager can use to build a DatastoreContext from the base DatastoreContext for each Shard. That way the Shard just accesses the DatastoreContext as it does now. |
| Comment by Tom Pantelis [ 27/Oct/15 ] |