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

Reparenting endtoend testcases in Go migrated from Python [+ github actions] #5604

Merged
merged 13 commits into from
Dec 31, 2019

Conversation

ajeetj
Copy link
Contributor

@ajeetj ajeetj commented Dec 20, 2019

  1. Migrated Reparent python test cases in Go
  2. Split Github actions for cluster_endtoend into 3 nodes so that tests can run in parallel.
  3. Added WaitForTabletTypes new function in vttablet_process to check if tablet status is any of the give statuses. [This was done as we are stopping and starting the same tablet instances, so their status were unpredictable. Sometimes few of them comes in SERVING mode while others comes in NOT_SERVING mode]

@deepthi This is ready for review and can be merged after all checks are passed.

Signed-off-by: Ajeet jain ajeet@planetscale.com

Signed-off-by: Ajeet jain <ajeet@planetscale.com>
@ajeetj ajeetj requested a review from sougou as a code owner December 20, 2019 05:21
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
This reverts commit d03d3a1.
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
go/test/endtoend/reparent/reparent_range_based_test.go Outdated Show resolved Hide resolved
go/test/endtoend/reparent/reparent_test.go Outdated Show resolved Hide resolved
go/test/endtoend/binlog/binlog_test.go Outdated Show resolved Hide resolved
go/test/endtoend/reparent/reparent_test.go Show resolved Hide resolved
go/test/endtoend/reparent/reparent_test.go Outdated Show resolved Hide resolved
tmClient *tmc.Client
keyspaceName = "ks"
shardName = "0"
shard1Name = "0000000000000000-ffffffffffffffff"
Copy link
Member

Choose a reason for hiding this comment

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

Is there a reason to use this instead of just 0?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, copied from Python ones. Will test with 0-f

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated it to -80. Let me know if that works for the test

Copy link
Member

Choose a reason for hiding this comment

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

I looked at the original python test case. I think this does need to be the same as it was in python.
Also, in the python test, we basically run the same scenario for shard0 and shard1, the only difference is how the shard is represented: 0 vs 0000...-ffff.... We should preserve that while porting rather than changing the test to only have 1 master + 1 replica when the shard is represented as 0000...-ffff...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have reverted the range to 000...-ffff....
As wrt to replica counts I have only used master-replica as we just need to verify replication in a replica in range-based test.
As opposed to other Tests like TestChangeTypeSemiSync and TestReparentFromOutside need 4 replicas setup which is already present in Shard0.

Signed-off-by: Ajeet jain <ajeet@planetscale.com>
@ajeetj ajeetj changed the title Resharding endtoend testcases in Go migrated from Python Reparenting endtoend testcases in Go migrated from Python Dec 23, 2019
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
@ajeetj
Copy link
Contributor Author

ajeetj commented Dec 23, 2019

@deepthi This is ready for another review.
Unit tests are failing after I rebased with the master. I guess Morgan is already working on it.

Signed-off-by: Ajeet jain <ajeet@planetscale.com>
@ajeetj ajeetj changed the title Reparenting endtoend testcases in Go migrated from Python Reparenting endtoend testcases in Go migrated from Python [+ github actions] Dec 26, 2019
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
@morgo
Copy link
Contributor

morgo commented Dec 30, 2019

LGTM I have changed cluster_endtoend test to not be required.

Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Signed-off-by: Ajeet jain <ajeet@planetscale.com>
Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

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

LGTM

@deepthi deepthi merged commit 1ae74b1 into vitessio:master Dec 31, 2019
@ajeetj ajeetj deleted the tal_reparent_new branch December 31, 2019 06:04
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.

3 participants