Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign uproachtest/bank: don't start chaos until nodes are serving SQL #30989
Conversation
nvanbenschoten
requested a review
from
petermattis
Oct 4, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nvanbenschoten
Oct 4, 2018
Member
Please hold off on this. I thought it would fix the second class of failures we saw in #30064, but I just had a repro so it doesn't seem like it did.
|
Please hold off on this. I thought it would fix the second class of failures we saw in #30064, but I just had a repro so it doesn't seem like it did. |
tschottdorf
reviewed
Oct 5, 2018
I'm surprised why you didn't change the break on l156 into a return.
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nvanbenschoten
Oct 11, 2018
Member
I still have this cleanup on my plate, including the l156 fix, but I'd like to actually get this test working without flakes first, which is turning out to be surprisingly tricky.
|
I still have this cleanup on my plate, including the l156 fix, but I'd like to actually get this test working without flakes first, which is turning out to be surprisingly tricky. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nvanbenschoten
changed the title from
roachtest/bank: don't deadlock on teardown
to
roachtest/bank: don't start chaos until nodes are serving SQL
Oct 15, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
petermattis
approved these changes
Oct 15, 2018
Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Reviewable status:complete! 0 of 0 LGTMs obtained (and 1 stale)
pkg/cmd/roachtest/bank.go, line 210 at r1 (raw file):
consistentIdx int, ) { s.waitGroup.Add(1)
Is this kosher? You're calling Add from a goroutine and then calling Wait from the main routine. I think this would hit an internal assertion in WaitGroup, except that the Wait doesn't happen right away.
pkg/cmd/roachtest/bank.go, line 215 at r3 (raw file):
// Don't begin the chaos monkey until all nodes are serving SQL connections. // This ensures that we don't test cluster initialization under chaos. for i := 0; i < c.nodes; i++ {
Nit: for i := 0; i <= c.nodes; i++. Then in the body you can use i instead of i+1.
nvanbenschoten
reviewed
Oct 15, 2018
Reviewable status:
complete! 1 of 0 LGTMs obtained
pkg/cmd/roachtest/bank.go, line 210 at r1 (raw file):
Previously, petermattis (Peter Mattis) wrote…
Is this kosher? You're calling
Addfrom a goroutine and then callingWaitfrom the main routine. I think this would hit an internal assertion inWaitGroup, except that theWaitdoesn't happen right away.
Yeah, you're absolutely right.
pkg/cmd/roachtest/bank.go, line 215 at r3 (raw file):
Previously, petermattis (Peter Mattis) wrote…
Nit:
for i := 0; i <= c.nodes; i++. Then in the body you can useiinstead ofi+1.
Make it for i := 1; i <= c.nodes; i++ and you've got a deal.
tschottdorf
approved these changes
Oct 15, 2018
mod Peter's comments which it looks you're fixing up right now.
Reviewed 1 of 1 files at r1, 1 of 1 files at r2, 1 of 1 files at r3.
Reviewable status:complete! 1 of 0 LGTMs obtained (and 1 stale)
nvanbenschoten
reviewed
Oct 15, 2018
Reviewable status:
complete! 0 of 0 LGTMs obtained (and 2 stale)
pkg/cmd/roachtest/bank.go, line 210 at r1 (raw file):
Previously, nvanbenschoten (Nathan VanBenschoten) wrote…
Yeah, you're absolutely right.
Done.
pkg/cmd/roachtest/bank.go, line 215 at r3 (raw file):
Previously, nvanbenschoten (Nathan VanBenschoten) wrote…
Make it
for i := 1; i <= c.nodes; i++and you've got a deal.
Done.
petermattis
approved these changes
Oct 15, 2018
Reviewable status:
complete! 0 of 0 LGTMs obtained (and 2 stale)
a-robinson
approved these changes
Oct 15, 2018
Having just read through the recent comments on #30064 I agree this is the right change to make. We should also reduce the migration lease duration, though. There's no need for it to be so long given that we renew it in the background while running migrations.
nvanbenschoten
added some commits
Oct 4, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nvanbenschoten
Oct 15, 2018
Member
TFTRs.
We should also reduce the migration lease duration, though.
I was hoping for a quick fix here, but it looks like this is tied to the sql.LeaseManager, which uses the same duration for all leases. This will have to wait on other improvements to the leasing system, like #24041.
bors r+
|
TFTRs.
I was hoping for a quick fix here, but it looks like this is tied to the bors r+ |
bot
pushed a commit
that referenced
this pull request
Oct 15, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
craig
bot
commented
Oct 15, 2018
Build succeeded |
nvanbenschoten commentedOct 4, 2018
•
edited
Informs #30064.
Release note: None