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

roachtest: restore/tpce/400GB/aws/backupsIncluded=48/nodes=4/cpus=8 failed #98437

Closed
cockroach-teamcity opened this issue Mar 11, 2023 · 1 comment
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 11, 2023

roachtest.restore/tpce/400GB/aws/backupsIncluded=48/nodes=4/cpus=8 failed with artifacts on master @ 5b2a5670cbbe895d76602c230390816e783e0caa:

test artifacts and logs in: /artifacts/restore/tpce/400GB/aws/backupsIncluded=48/nodes=4/cpus=8/run_1
(test_runner.go:990).runTest: test timed out (1h0m0s)
(monitor.go:127).Wait: monitor failure: monitor task failed: output in run_145453.651016733_n1_cockroach-sql-insecu: ./cockroach sql --insecure -e "RESTORE  FROM LATEST IN 's3://cockroach-fixtures/backups/tpc-e/customers=25000/v22.2.0/inc-count=48?AUTH=implicit' AS OF SYSTEM TIME '2022-12-21T11:00:00Z' " returned: COMMAND_PROBLEM: ssh verbose log retained in ssh_145453.661011748_n1_cockroach-sql-insecu.log: exit status 137

Parameters: ROACHTEST_cloud=aws , ROACHTEST_cpu=8 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-25269

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Mar 11, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 11, 2023
@stevendanna stevendanna removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Mar 15, 2023
@rhu713
Copy link
Contributor

rhu713 commented May 11, 2023

Going to close this issue for now as I believe that parallelizing OpenSSTs by moving it inside each restore worker has helped the performance of this test. This test hasn't timed out in over a month and roachperf has shown a bump in throughput after the merge of the parallelization PR.

Screenshot 2023-05-11 at 1 30 47 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-disaster-recovery
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants