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: workload fails to connect to a node - connection timed out #37070

Closed
cockroach-teamcity opened this issue Apr 24, 2019 · 2 comments
Closed
Labels
A-testing Testing tools and infrastructure C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity O-robot Originated from a bot. X-stale

Comments

@cockroach-teamcity
Copy link
Member

SHA: https://github.com/cockroachdb/cockroach/commits/a22a3780ebb5482be04b6f31344c764b2fb5f765

Parameters:

To repro, try:

# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
stdbuf -oL -eL \
make stressrace TESTS=kv0/enc=false/nodes=3/cpu=96 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log

Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1257365&tab=buildLog

The test failed on release-19.1:
	cluster.go:1423,kv.go:69,cluster.go:1761,errgroup.go:57: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1257365-kv0-enc-false-nodes-3-cpu-96:4 -- ./workload run kv --init --splits=1000 --histograms=logs/stats.json --concurrency=192 --duration=10m --read-percent=0 {pgurl:1-3} returned:
		stderr:
		
		stdout:
		Error: dial tcp 10.12.41.6:26257: connect: connection timed out
		Error:  exit status 1
		: exit status 1
	cluster.go:1782,kv.go:72,kv.go:137,test.go:1245: Goexit() was called

@cockroach-teamcity cockroach-teamcity added this to the 19.2 milestone Apr 24, 2019
@cockroach-teamcity cockroach-teamcity added C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. labels Apr 24, 2019
@andreimatei andreimatei changed the title roachtest: kv0/enc=false/nodes=3/cpu=96 failed roachtest: workload fails to connect to a node Apr 25, 2019
@andreimatei andreimatei changed the title roachtest: workload fails to connect to a node roachtest: workload fails to connect to a node - connection timed out Apr 25, 2019
@kenliu kenliu added A-testing Testing tools and infrastructure C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. and removed O-roachtest C-test-failure Broken test (automatically or manually discovered). labels Jul 12, 2019
@kenliu kenliu removed this from the 19.2 milestone Jul 12, 2019
@github-actions
Copy link

github-actions bot commented Jun 4, 2021

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
5 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testing Testing tools and infrastructure C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity O-robot Originated from a bot. X-stale
Projects
None yet
Development

No branches or pull requests

2 participants