Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Goals
- Improving performance of single Tephra Transaction Server
- Make Tephra Transaction server scale horizontally
- Make Tephra Transaction server Highly Available (HA) with Isolation
- Improve operational aspects of Transaction Server
- Improve performance of Workflow scheduling to schedule 1000s of jobs / second
Areas of Focus
- Transaction Invalid List Management
- Tephra Single Server Performance Improvements
- Isolation and Scalability of Tephra Transaction Server
- Improving scheduling performance of Workflow system
High Level Requirements
Transaction Invalid List Management
- System should automatically handle pruning of the transaction invalid list
- Reduce operational complexity for running manual steps to prune invalid transaction list
- Applied during major and striped compaction
- Metrics around the current invalid list size
- Tool to inspect the invalid list
Tephra Performance Improvement
- Single Tephra Server should be able to support up-to ~ 10K transactions/second
- Support read-only and hierarchical conflict detection
Scale and Isolation
- Run multiple instances of Tephra Transaction Server in active-active in single DC or multiple DC
- Isolation at namespace level
Technical Breakdown
P&S-001 : Performance improvements of Single Transaction Server
P&S-002 : Invalid List Pruning with major compaction
P&S-003 : Invalid List Pruning with striped compaction
P&S-004 : Tool to inspect Invalid List
P&S-005 : Support for running multiple instance of Transaction Server in Active-Active mode
P&S-006 : Transaction Server per namespace for Resource Isolation
Open Questions
Action Items
Table of Contents |
---|