Change tracker to use allprivs instead of dba#6720
Merged
deepthi merged 1 commit intovitessio:masterfrom Sep 16, 2020
Merged
Conversation
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR just changes the db user to allprivs instead of dba to prevent inadvertent writes into schema_version when a tablet transitions from master to replica.
We have a separate issue where reparent tests are failing with tracker on. But on further investigation it looks like that those tests are not setting up and tearing down the cluster correctly leading to tablets resuming from their earlier state and binlogs being thus in unexpected states. That is being fixed in #6726 and if any related tracker bugs are found we will fix them as part of that issue.
Signed-off-by: Rohit Nayak rohit@planetscale.com