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.

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

Split clone using consistent snapshot #4541

Merged
merged 5 commits into from
Jan 29, 2019

Conversation

systay
Copy link
Collaborator

@systay systay commented Jan 22, 2019

No description provided.

@systay systay requested a review from sougou as a code owner January 22, 2019 17:40
@systay systay force-pushed the consistent-split-clone branch from 4564691 to 1d8fb20 Compare January 25, 2019 12:38
@systay systay changed the title Consistent split clone Split clone using consistent snapshot Jan 25, 2019
Copy link
Contributor

@sougou sougou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of nits. It looks like you've cleaned up some of the code. I'll trust the tests for the correctness. It will be good if @tirsen eyeballed them also.

@@ -55,7 +55,7 @@ func main() {
logutil.LogEvent(logger, e)
})
if err != nil {
log.Error(err)
log.Errorf("%+v", err)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentional? Or did you change this for troubleshooting?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did change it for trouble shooting, but that does not mean that it needs to go back. %+v includes the stacktrace, and I think that always makes sense to log for errors. I'll remove it from here and issue a separate PR with more of these changes.

@@ -23,6 +23,8 @@ import (
"strings"
"time"

"github.com/golang/glog"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should instead be vitess.io/vitess/go/vt/log. It allows us to remap the logging functions as needed.

@@ -424,6 +435,29 @@ func (scw *SplitCloneWorker) Run(ctx context.Context) error {
return nil
}

func (scw *SplitCloneWorker) disableUniquenessCheckOnDestinationTablets(ctx context.Context) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is still questionable. I don't see it used in this PR. Should we remove it until it becomes official?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please remove it. I think it would be good but it's currently hard to make work.

Signed-off-by: Andres Taylor <[email protected]>
…clone

* upstream/master:
  docker: don't chown nonexistent /vt dir
  mysqlctl: add backup test for rockdb and sdi files
  Adding a reset of the slave on blank restore
  Add a special plan type for impossible queries
  mysqlctl: add MyRocks dir/files to backups
  Use recommended version combination
  Remove trailing whitespace
<LABEL for="maxTPS">Maximum Write Transactions/second (If non-zero, writes on the destination will be throttled. Unlimited by default.): </LABEL>
<INPUT type="text" id="maxTPS" name="maxTPS" value="{{.DefaultMaxTPS}}"></BR>
<LABEL for="maxReplicationLag">Maximum Replication Lag Seconds (enables the adapative throttler. Disabled by default.): </LABEL>
<INPUT type="text" id="maxReplicationLag" name="maxReplicationLag" value="{{.DefaultMaxReplicationLag}}"></BR>
<INPUT type="hidden" name="keyspace" value="{{.Keyspace}}"/>
<INPUT type="hidden" name="shard" value="{{.Shard}}"/>
<LABEL for="useConsistentSnapshot">Use consistent snapshot during the offline cloning:</LABEL>
<INPUT type="checkbox" id="useConsistentSnapshot" name="useConsistentSnapshot" value="false"><a href="https://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_consistent_read" target="_blank">?</a></BR>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that value needs to be value="true"

@sougou sougou merged commit 86594dd into vitessio:master Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants