-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
streamingest: unskip TestTenantStreamingUnavailableStreamAddress #107094
streamingest: unskip TestTenantStreamingUnavailableStreamAddress #107094
Conversation
bcf1f9c
to
954cada
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
If you wanted, there isn't really a need to call StartShaedProcessTenant again. We could open a connection to Server(2) which should still have a tenant running.
But, if you've already stressed this, let's stick with this.
954cada
to
6761983
Compare
thanks, good idea but it flakes with that :( bors r+ I'm happy to do followups, I think there are a few small things I want to cleanup here. |
This PR was included in a batch that was canceled, it will be automatically retried |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
It looks like bors r- |
Canceled. |
bummer. not ready indeed. thanks Nathan and sorry about that! I guess local stress was not enough here :( |
6761983
to
094ec29
Compare
@stevendanna it's ready for you.. not touching the source cluster at all now, after killing a server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try this again :D. Thanks for digging into it.
thanks! bors r+ |
Build failed (retrying...): |
Build failed: |
094ec29
to
af4f1c8
Compare
a rebase was needed, it should pass now. bors r+ |
Changing a few things to get this test to pass under stress: - use 50 ranges instead of 10, because there are already 50-ish system ranges, so if we write only 10 more ranges those might not get distributed on all servers. - avoid reading from the source cluster after stopping a node, it's flaky, see cockroachdb#107499 for more info. Epic: none Fixes: cockroachdb#107023 Fixes: cockroachdb#106865 Release note: None
af4f1c8
to
ce27952
Compare
Canceled. |
bors r+ |
Build succeeded: |
Changing a few things to get this test to pass under stress:
so if we write only 10 more ranges those might not get distributed on all
servers.
see multitenant: cannot query after stopping a server in a unit test #107499 for more info.
Epic: none
Fixes: #107023
Fixes: #106865
Release note: None