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: decommission test makes improper usage of --join flags #51652

Closed
irfansharif opened this issue Jul 21, 2020 · 4 comments
Closed

roachtest: decommission test makes improper usage of --join flags #51652

irfansharif opened this issue Jul 21, 2020 · 4 comments
Labels
A-kv-server Relating to the KV-level RPC server 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 T-server-and-security DB Server & Security X-stale

Comments

@irfansharif
Copy link
Contributor

irfansharif commented Jul 21, 2020

Observed in #51649 (review), fall out from #51245 (and I think similar to #51557).

Jira issue: CRDB-4020

@blathers-crl
Copy link

blathers-crl bot commented Jul 21, 2020

Hi @irfansharif, please add a C-ategory label to your issue. Check out the label system docs.

While you're here, please consider adding an A- label to help keep our repository tidy.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@irfansharif irfansharif self-assigned this Jul 21, 2020
@irfansharif
Copy link
Contributor Author

Hm, this test is written a bit strangely.

for i := 1; i <= numDecom; i++ {
c.Start(ctx, t, c.Node(i), startArgs(fmt.Sprintf("-a=--attrs=node%d", i)))
}

It starts nodes of one-by-one in order to configure specific attributes. Except that doesn't play well with #51329 and #51557, where in trying to avoid a --skip-init flag like was originally attempted in #51329, we auto-init through roachprod if (a) starting a single node cluster (roachprod uses start-single-node, which auto-inits) and (b) we init if starting n1 where n1 isn't already previously initialized.

I can either re-work this test to somehow work around roachprod's auto-init behavior (by starting all nodes and stopping them, and then restarting one-by-one in adding the attributes), but that feels dirty. Alternatively I can have the start-single-node through roachprod similarly persist the cluster-bootstrapped file to prevent re-auto-init? Both of these feel like hacks on hacks that I'd be a bit happier with --skip-init.

@irfansharif
Copy link
Contributor Author

Oh it's not just that, we're also wiping the entire node away, which wipes out the cluster-bootstrapped on-disk marker.

if err := c.RunE(ctx, c.Node(node), "rm -rf {store-dir}"); err != nil {
return err
}

@irfansharif irfansharif removed their assignment Dec 31, 2020
@mwang1026 mwang1026 added the A-kv-server Relating to the KV-level RPC server label May 27, 2021
@knz knz added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-testing Testing tools and infrastructure labels May 28, 2021
@jlinder jlinder added T-kv KV Team T-server-and-security DB Server & Security labels Jun 16, 2021
@github-actions
Copy link

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
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
@exalate-issue-sync exalate-issue-sync bot removed the T-kv KV Team label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-kv-server Relating to the KV-level RPC server 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 T-server-and-security DB Server & Security X-stale
Projects
No open projects
Status: Done 21.2
Archived in project
Development

No branches or pull requests

4 participants