Klein is a Paxos based distributed tool library. Based on Paxos, it can realize KV storage, cache, lock, registry,
configuration center, etc.
We hope that Klein can be deployed independently or embedded in your project. You can use it just like Redis, or embed Klein into your project without relying on any middleware to ensure data consistency among members. Of course, this is still in the process of implementation. 😆😆😆
Look forward to your star⭐
- Control the number of buffers based on LRU
- Cache Automatic Expiration (TTL)
- Write request, disordered negotiation, sequential confirmation
- Read request, using negotiation log
- Batch negotiation
- Optimize the prepare phase
- Snapshot
- To split roles such as Group and proposer, you only need to isolate instance instead of isolating them
- Master role：
- Change of members
- The master promotion should have the most complete data (the master should be elected through negotiation with the proposal. If the promotion is successful, the previous instances must be applied)
- Keep data consistent
- Master heartbeat triggers data synchronization
- Snapshot synchronization (the heartbeat carries the checkpoint and the learn message returns the checkpoint)
-
New members join the cluster and actively learn from the master
- Optimize read requests (write requests must be copied to the master)
- Optimize write requests (write requests can only be executed by the master to avoid livelocks)
- Automatic member discovery (research)
- NWR
- Confirm Optimize read requests
- There is no interference key, so a round of Prepare is unnecessary
- Verified by jepsen
- Basic functions such as reading, writing, etc
- Implement LRU with persistence
- Cache Automatic Expiration (TTL)
- list
- map
- LogManager row lock
- Monitor negotiation efficiency
- Monitoring thread pool indicators (DefaultTimer, ThreadExecutor)
- ProposalNo全局唯一
- 状态机持久化（master、lock）
- How to generate ProposalNo?
- Can parallel negotiation really be supported?
- Which proposal will reach consensus?
- Can the Confirm phase (application state transition) really be executed asynchronously?
- How do I create a snapshot of a running system?
- Is it necessary to completely isolate the splitting of a group?
- Optimize the Prepare phase
- Batch negotiation (queue) to reduce RPC interaction