1 comment (1 comment)0 reactions (0 reactions)0 assignees (0 assignees)Java4,212 stars (4,212 stars)1,469 forks (1,469 forks)batch import
featureshelp wantedquestion
Description
为了控制事务提交时间,将从最终一致性跨越成为强一致性。
Contributor guide
- Tech stack
- java
- Domain
- backenddatabase
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 5
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- Knowledge of distributed systemsUnderstanding consensus algorithmsFamiliarity with Java
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 10
- Research direction
- This issue proposes implementing an atomic clock algorithm to transition from eventual consistency to strong consistency in transaction commit times. The description is high level and lacks specific technical requirements. A newcomer should first review existing atomic clock algorithms (e.g., Google's TrueTime, Hybrid Logical Clocks) and consider how they could be integrated into the tx lcn framework. Additionally, examining the single comment in the issue and related repository discussions may provide context. No concrete design or implementation details are provided, so the initial step would be to propose a detailed design document.