settings: increase number of cores test can use

[cthumuluru-crdb]

Clutser setting updates on one node occasionally take over 45 seconds to propagate to other nodes. This test has failed a few times recently. The issue is not reproducible, even under stress testing with 10,000 repetitions. Increasing the timeout to 60 seconds to determine if it resolves the problem.

Epic: None
Fixes: #133732
Release note: None

[cockroach-teamcity]

This change is 

[shubhamdhama]

Based on our offline discussions we see some other interesting logs too,

I241229 15:00:43.666504 35984 kv/kvserver/liveness/liveness.go:1067 ⋮ [T1,Vsystem,n2,liveness-hb] 478  retrying liveness update after ‹liveness.errRetryLiveness›: result is ambiguous: error=ba: ‹ConditionalPut [/System/NodeLiveness/2], EndTxn(commit modified-span (node-liveness)) [/System/NodeLiveness/2], [txn: 29d7ba85], [can-forward-ts]› RPC error: grpc: ‹node unavailable; try another peer› [code 2/Unknown] [exhausted] (last error: ‹failed to send RPC›: sending to all replicas failed; last error: ba: ‹ConditionalPut [/System/NodeLiveness/2], EndTxn(commit modified-span (node-liveness)) [/System/NodeLiveness/2], [txn: 29d7ba85], [can-forward-ts]› RPC error: grpc: ‹node unavailable; try another peer› [code 2/Unknown])
....
I241229 15:00:43.972075 41534 gossip/client.go:145 ⋮ [T1,Vsystem,n2] 484  closing client to n1 (‹127.0.0.1:34981›): stopping outgoing client to n1 (‹127.0.0.1:34981›); already have incoming

Rather than increasing timeout, maybe we can explore printing ack. Or, as the logs suggests the connection from n2 to n1 is broken. Did this impact the rangefeed?

[rimadeodhar]

Sending it back to your queue to address @shubhamdhama's comments.

[cthumuluru-crdb]

I didn't find anything suspicious from the logs. I spent sometime browsing rangefeed codebase but nothing stood out. Based on the discussion in #db-engineering and #db-server-team, with other DB engineers, I'm increasing the resources to the test for now and see if it fails again. I'm not adding the code to capture the profile just yet.

Reviewable status: complete! 0 of 0 LGTMs obtained

[cthumuluru-crdb]

bors r+

[craig]

Build succeeded:

• local_roachtest
• linux_amd64_fips_build
• linux_arm64_build
• acceptance
• macos_amd64_build
• lint
• examples_orms
• windows_build
• local_roachtest_fips
• check_generated_code
• macos_arm64_build
• docker_image_amd64
• unit_tests
• linux_amd64_build

[cthumuluru-crdb]

blathers backport 23.2 24.3

[blathers-crl]

Based on the specified backports for this PR, I applied new labels to the following linked issue(s). Please adjust the labels as needed to match the branches actually affected by the issue(s), including adding any known older branches.

---

Issue #133732: branch-release-23.2.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from f152a7a to blathers/backport-release-23.2-138717: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.2 failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}