Skip to content

roachtest: decommission roachtests conform to new output#98113

Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom
AlexTalks:dpf_fix_roachtests
Mar 7, 2023
Merged

roachtest: decommission roachtests conform to new output#98113
craig[bot] merged 1 commit intocockroachdb:masterfrom
AlexTalks:dpf_fix_roachtests

Conversation

@AlexTalks
Copy link
Copy Markdown
Contributor

This change fixes decommission roachtests to properly be aware of the new output introduced by #96100, and to utilize the decommission pre-checks accordingly. In some places, the decommission pre-checks are skipped, especially because the decommission used in the test is not expected to be completeable.

Fixes: #98026, #98018, #98017.

Release note: None

@AlexTalks AlexTalks requested review from kvoli and nvb March 7, 2023 01:38
@AlexTalks AlexTalks requested a review from a team as a code owner March 7, 2023 01:38
@AlexTalks AlexTalks requested review from herkolategan and renatolabs and removed request for a team March 7, 2023 01:38
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

Copy link
Copy Markdown
Contributor

@kvoli kvoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Csn you open an issue to add prechecks back to the roachtest in the future?

This change fixes decommission roachtests to properly be aware of the
new output introduced by cockroachdb#96100, and to utilize the decommission
pre-checks accordingly. In some places, the decommission pre-checks are
skipped, especially because the decommission used in the test is not
expected to be completeable.

Fixes: cockroachdb#98026, cockroachdb#98018, cockroachdb#98017.

Release note: None
@AlexTalks
Copy link
Copy Markdown
Contributor Author

bors r=kvoli

@craig
Copy link
Copy Markdown
Contributor

craig bot commented Mar 7, 2023

Build failed (retrying...):

@craig
Copy link
Copy Markdown
Contributor

craig bot commented Mar 7, 2023

Build succeeded:

@craig craig bot merged commit cb36e3b into cockroachdb:master Mar 7, 2023
AlexTalks added a commit to AlexTalks/cockroach that referenced this pull request Jul 14, 2023
Once decommission pre-checks were introduced, in cockroachdb#98113 the roachtests
were updated to handle the new output in certain cases. Despite this,
it was not handled in all cases and in the `decommission/mixed-versions`
test, which upgrades and restarts nodes, decommission requests that
happen shortly after restart could fail the pre-checks because nodes are
considered "suspect" for 30s after being unavailable. This change
decreases the suspect time limit and ensures that the nodes are
considered fully available before decommissioning, with pre-checks
enabled.

Fixes: cockroachdb#101620

Release note: None
craig bot pushed a commit that referenced this pull request Jul 17, 2023
106642: geos: update GEOS to 3.11 r=sumeerbhola,rickystewart a=otan

All test changes are due to a change in Polygon output ordering, or GEOS
outputting a different yet valid result. Note we stop supporting windows
as a result.

Release note (general change): Spatial libraries from Cockroach
now rely on GEOS 3.11 instead of GEOS 3.8.

Epic: none
Release note (general change): Stop distributing `libgeos`
for (experimental) Windows build. Users can instead install GEOS
directly from source: https://libgeos.org/usage/download/.




106859: roachtest: avoid decommissioning suspect nodes in mixed version test r=AlexTalks a=AlexTalks

Once decommission pre-checks were introduced, in #98113 the roachtests were updated to handle the new output in certain cases. Despite this, it was not handled in all cases and in the `decommission/mixed-versions` test, which upgrades and restarts nodes, decommission requests that happen shortly after restart could fail the pre-checks because nodes are considered "suspect" for 30s after being unavailable. This change decreases the suspect time limit and ensures that the nodes are considered fully available before decommissioning, with pre-checks enabled.

Fixes: #101620

Release note: None

Co-authored-by: Oliver Tan <otan@cockroachlabs.com>
Co-authored-by: Alex Sarkesian <sarkesian@cockroachlabs.com>
AlexTalks added a commit that referenced this pull request Jul 18, 2023
Once decommission pre-checks were introduced, in #98113 the roachtests
were updated to handle the new output in certain cases. Despite this,
it was not handled in all cases and in the `decommission/mixed-versions`
test, which upgrades and restarts nodes, decommission requests that
happen shortly after restart could fail the pre-checks because nodes are
considered "suspect" for 30s after being unavailable. This change
decreases the suspect time limit and ensures that the nodes are
considered fully available before decommissioning, with pre-checks
enabled.

Fixes: #101620

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

roachtest: decommission/randomized failed

3 participants