Conversation
Hack up just enough support for scans to see if we can perhaps tickle the release blocker here: cockroachdb#46652 No validation was added. We're just using kvnemeses to send random scans for us. Release note: None
|
Here's an example run: https://gist.github.com/tbg/aaa88d3f8dedf0aba4792b11fe21297a Not much to see other than that we're actually doing a bunch of scans, and they sometimes return data. (kvnemesis can't handle multiple results, so I'm pretending scans just return their first hit if any, and nothing is validated). |
|
❌ The GitHub CI (Cockroach) build has failed on 655c9eac. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. I am experimental - my owner is otan. |
|
I added reverse scans. @nvanbenschoten this might be of interest to you (full gist) and this is of interest as well: If I ignore both of those errors in the output during I'll try to avoid the reversescan+commit scenario in the generator. It's clear from the error why that fails. |
|
Oh, the "batch needs splitting" is similarly an artifact of committing a batch with an endtxn. Here, we allow the batch to consist of limited ops plus a commit: cockroach/pkg/kv/kvclient/kvcoord/dist_sender.go Lines 577 to 596 in 5ec87f1 This already makes me nervous, though I guess it's fine? But then it seems pretty possible that we'll pass cockroach/pkg/kv/kvclient/kvcoord/dist_sender.go Lines 692 to 695 in 5ec87f1 and that will happily split off the EndTxn from the scans. Oops, real bug. |
|
Ready for more, @nvanbenschoten? Here's another fatal: https://gist.github.com/tbg/0a793101e942a3e998d3967f3d68df10 panic: expected latches held, found none [recovered] |
Release note: None
|
❌ The GitHub CI (Cockroach) build has failed on ef5f93b8. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. I am experimental - my owner is otan. |
I'm happy you hit this. I saw this once a few weeks ago while working on #46639 but was unable to hit it again when I went back to try to reproduce. If you're still stressing this to hit the limit bug, do you mind applying the following diff: I'll also spin up some kvnemeses to assist the effort. |
This one is strange. We're calling |
Do you mind expanding? It's not so clear why it fails to me. I could understand if it failed during the |
Well, that's an interesting assertion to see fire. This is what's responsible for the |
|
Huh, the error is coming from |
|
I've filed this as #47219. |
Hack up just enough support for scans to see if we can perhaps tickle
the release blocker here:
#46652
No validation was added. We're just using kvnemeses to send random
scans for us.
Release note: None