yugabyte/yugabyte-db

[YW] Deleting a universe with a released node requires "force delete"

Open

#5,781 opened on Sep 23, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/platformgood first issuehelp wantedpriority/low

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Repro steps:

  1. Create a 3 node YW cloud universe (tested against GCP)
  2. Go to the nodes page at http://portal.dev.yugabyte.com/universes/e78b9592-0f2b-4e41-80e4-f30c94611b5b/nodes or equiv
  3. Pick one node, "Stop Processes"
  4. Pick same node, "Release Instance"
  5. Destroy/delete universe. Do not check "force delete" Universe deletion fails.

If "force delete" is set to true, universe deletion succeeds, so this is not a high pri issue. However, setting force delete can mask other errors, so it would be good to eventually fix this.

Contributor guide

Research direction
Investigate the universe deletion process to identify why a released node requires force delete and implement a fix to allow normal deletion.
Tech stack
None
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60