[CONTROLLER-1884] Custom Akka Persistence Journal implementation Created: 18/Feb/19 Updated: 19/Mar/19 Resolved: 19/Mar/19 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | None |
| Fix Version/s: | Sodium, Neon SR1 |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Our current use of leveldb is not optimal, as the leveldb is not supported by upstream for production environments. atomix.io has a SegmentedJournal class, which looks like a very good match for Akka's persistence semantics, while potentially allowing direct integration into sal-akka-raft (as it really matches RAFT log semantics). Add a custom Akka Persistence Journal implementation based on SegmentedJournal to complement our custom SnapshotStore implementation. |