-
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
roachtest: sqlsmith/setup=empty/setting=default failed #47541
Comments
|
I tried reproducing this problem by replaying the sqlsmith log on the given commit (with The logs of the crashed node contain a bunch of messages like
and the first one occurs about 62 seconds before the crash. Not sure whether it matters though. @rohany could you take a quick look at the stack trace and this issue since you updated some code in here recently? |
I can't repro it either, but the stack in the logs looks like the culprit. I'll take a closer look. |
Inactive. |
This crash doesn't seem related to the referenced issues. Is it indeed fixed in some version or another issue? |
@dpkirchner I agree that the referenced issues seem unrelated. I'm assuming that you hit a problem on a DELETE query with a similar stack trace? If so, please feel free to open another issue with reproduction steps if possible. |
@yuzefovich Yeah, similar stack trace. I'll need to upgrade to the latest version before I open an issue, but if I hit it again I definitely will and will reference this one. |
@yuzefovich The bug is still in the latest version. I'll try to come up with a repro case so I can submit it as an issue, but it looks like the above stack trace (at least the part we're able to see here) so I guess that's a good place to start. I was able to "fix" this by removing some indices from the table, so at least production nodes aren't crashing any more. Unfortunately this may mean I can't provide any information at all. |
(roachtest).sqlsmith/setup=empty/setting=default failed on release-20.1@575a5bd7a8714464a74f52f337dc5af33558ebb0:
More
Artifacts: /sqlsmith/setup=empty/setting=default
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: