Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce the backoff mechanism for gRPC client #8047

Closed
4 of 6 tasks
CabinfeverB opened this issue Apr 10, 2024 · 0 comments · Fixed by #8679
Closed
4 of 6 tasks

Introduce the backoff mechanism for gRPC client #8047

CabinfeverB opened this issue Apr 10, 2024 · 0 comments · Fixed by #8679
Assignees
@JmPotato
Labels
type/development The issue belongs to a development tasks

Comments

@CabinfeverB
Copy link
Member

CabinfeverB commented Apr 10, 2024 •
edited by rleungx
Loading

Development Task
@CabinfeverB CabinfeverB added the type/development The issue belongs to a development tasks label Apr 10, 2024
This was referenced Apr 10, 2024
Closed
Merged
ti-chi-bot bot added a commit that referenced this issue Apr 11, 2024
@CabinfeverB @ti-chi-bot
client: introduce RPCClient (#8048)
67461dd 
ref #8047

Signed-off-by: Cabinfever_B <[email protected]>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
@JmPotato JmPotato self-assigned this Apr 15, 2024
@JmPotato JmPotato mentioned this issue Apr 23, 2024
Merged
ti-chi-bot bot added a commit that referenced this issue Apr 24, 2024
@JmPotato @ti-chi-bot
client/tso: organize the methods of TSO dispatcher (#8121)
b4f292d 
ref #8047

Organize the methods of the TSO dispatcher.

Signed-off-by: JmPotato <[email protected]>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
@JmPotato JmPotato mentioned this issue Apr 24, 2024
Merged
ti-chi-bot bot pushed a commit that referenced this issue Apr 28, 2024
@JmPotato
client/tso: improve the switching of TSO stream (#8123)
aae410f 
close #7997, ref #8047

Previously, without enabling the TSO Follower Proxy, we only passively update its stream when a TSO request fails.
This means that we cannot automatically and gradually complete the TSO stream update after a service switch.
This PR strengthens this logic, which can improve the success rate of TSO requests during service switching.

Signed-off-by: JmPotato <[email protected]>
This was referenced Apr 28, 2024
Merged
Merged
nolouch pushed a commit to nolouch/pd that referenced this issue Apr 29, 2024
@JmPotato @ti-chi-bot @nolouch
client/tso: organize the methods of TSO dispatcher (tikv#8121)
b0037f5 
ref tikv#8047

Organize the methods of the TSO dispatcher.

Signed-off-by: JmPotato <[email protected]>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
nolouch pushed a commit to nolouch/pd that referenced this issue Apr 29, 2024
@JmPotato @nolouch
client/tso: improve the switching of TSO stream (tikv#8123)
5437f5e 
close tikv#7997, ref tikv#8047

Previously, without enabling the TSO Follower Proxy, we only passively update its stream when a TSO request fails.
This means that we cannot automatically and gradually complete the TSO stream update after a service switch.
This PR strengthens this logic, which can improve the success rate of TSO requests during service switching.

Signed-off-by: JmPotato <[email protected]>
ti-chi-bot bot pushed a commit that referenced this issue Apr 30, 2024
@JmPotato
client/tso: decouple tsoClient and tsoDispatcher (#8134)
1679dbc 
ref #8047

- Decouple `tsoClient` and `tsoDispatcher` to appropriately categorize different methods.
- Update `connectionCtxsUpdater` to support the Local TSO.

Signed-off-by: JmPotato <[email protected]>
This was referenced Nov 27, 2024
Merged
Closed
@ti-chi-bot ti-chi-bot bot closed this as completed in #8679 Dec 2, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in 29dfaf9 Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JmPotato JmPotato

Labels
type/development The issue belongs to a development tasks
Projects
None yet
Milestone
No milestone
2 participants
@JmPotato @CabinfeverB