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

Local TSO Allocator might be unknown for PD Leader after working #3124

Closed
Yisaer opened this issue Oct 30, 2020 · 0 comments · Fixed by #3134
Closed

Local TSO Allocator might be unknown for PD Leader after working #3124

Yisaer opened this issue Oct 30, 2020 · 0 comments · Fixed by #3134
Labels
component/tso Timestamp Oracle. type/bug The issue is confirmed as a bug.

Comments

@Yisaer
Copy link
Contributor

Yisaer commented Oct 30, 2020

Bug Report

What did you do?

When a Local TSO Allocator start running with new dc-location, the newly dc-location might be aware by PD Leader after at most 1 minute (refreshing dclocation cache from etcd). Before PD leader be aware of new dclocation, the newly Local TSO Allocator could already provide generating TSO ability.

What did you expect to see?

The newly dc-location should be aware by PD leader before the local tso allocator start working.

What did you see instead?

What version of PD are you using (pd-server -V)?
@Yisaer Yisaer added type/bug The issue is confirmed as a bug. component/tso Timestamp Oracle. labels Oct 30, 2020
@Yisaer Yisaer changed the title Local TSO Allocator might be unknown for PD Leader Local TSO Allocator might be unknown for PD Leader after working Oct 30, 2020
@Yisaer Yisaer mentioned this issue Nov 2, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/tso Timestamp Oracle. type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
1 participant
@Yisaer