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

Spurious warning from vtgate healthcheck #8120

Closed
deepthi opened this issue May 13, 2021 · 0 comments · Fixed by #8121
Closed

Spurious warning from vtgate healthcheck #8120

deepthi opened this issue May 13, 2021 · 0 comments · Fixed by #8121

Comments

@deepthi
Copy link
Member

deepthi commented May 13, 2021 •
edited
Loading

Overview of the Issue

When running PlannedReparentShard, vtgate logs show a confusing warning. At this point tablet 100 is no longer "SERVING", so there is no reason to even attempt to mark it as "Up".

Reproduction Steps

Run local example and tail -f $VTDATAROOT/tmp/vtgate.out

$ ./101_initial_cluster.sh
...
$ vtctlclient PlannedReparentShard -keyspace_shard=commerce/0 -new_master=zone1-101

Binary version

Version: 11.0.0-SNAPSHOT (Git revision 125117e86d branch 'master') built on Thu May 13 15:16:07 PDT 2021

Operating system and Environment details

Ubuntu 18.04.5 LTS

Log Fragments

W0513 15:18:41.139387   16148 healthcheck.go:441] not marking healthy master zone1-0000000100 as Up for commerce/0 because its MasterTermStartTime is smaller than the highest known timestamp from previous MASTERs zone1-0000000101: 1620944271 < 1620944316
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

healthcheck: attempt to update primary only if the current tablet is serving planetscale/vitess
1 participant
@deepthi