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

ctlv3: fix migration #6794

Merged
merged 1 commit into from
Nov 3, 2016
Merged

ctlv3: fix migration #6794

merged 1 commit into from
Nov 3, 2016

Conversation

xiang90
Copy link
Contributor

@xiang90 xiang90 commented Nov 3, 2016

/cc @wojtek-t @hongchaodeng

I tested the example data @wojtek-t provided. It fixed the problem. I do not really have time to test this with more extensive data set now.

Please try with more data set.

WAL + no snap (new k8s cluster); WAL+snap (long running k8s cluster); fresh snap (new cluster data forced by --snapshot-count==1)

Thanks!

@xiang90
Copy link
Contributor Author

xiang90 commented Nov 3, 2016

also cc @timothysc

@hongchaodeng
Copy link
Contributor

Tested and verified all three cases.

Code also LGTM.

@wojtek-t
Copy link
Contributor

wojtek-t commented Nov 3, 2016

OK - I also did some tests and it seems to fix my problems

@xiang90 - however, we need backport to 3.0 branch (fortunately backport seems to be trivial)

@xiang90
Copy link
Contributor Author

xiang90 commented Nov 3, 2016

@wojtek-t After we merge in this and #6793, we will do a new release.

@wojtek-t
Copy link
Contributor

wojtek-t commented Nov 3, 2016

Cool - that would be great.

@xiang90 xiang90 merged commit c5ac021 into etcd-io:master Nov 3, 2016
@xiang90 xiang90 deleted the fix_migration branch November 3, 2016 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants