-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
Migration generates timestamps that are too high for inactive tables #4668
Comments
Workaround for the invalid timestamp is up in review 3146. We still need to handle the case of an inactive replica having a higher timestamp than all active replicas in the cluster. Also, we should create an issue to remove the workaround (and rewrite all invalid timestamps in the metadata) in v2.2.x. |
This fixes the remaining part of #4668
This fixes the remaining part of #4668
This fixes the remaining part of #4668
A second work-around to handle the case of an inactive server having a higher timestamp is now in This solution is temporary as well, but a cleaner solution is considerably more work and needs additional though. We will probably replace that code by a different logic in 2.2. |
The timestamp is set to
9223372036854775808
.The effect this has is that if you add a new replica to a table after migration, that replica will never come up because its timestamp is always going to be higher than any other timestamp.
There might be a second problem here that inactive tables do not synchronize their states correctly.
Once this is fixed, we're going to ship a 2.1.1 point release asap.
The text was updated successfully, but these errors were encountered: