yugabyte/yugabyte-db

[Platform] Instance change from instances using IO1 storage type is not being handled correctly

Open

#6,078 opened on Oct 16, 2020

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/platformgood first issuekind/bug

Repository metrics

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

Description

  1. Create a universe using c5 instance types adnd IO1 storage on AWS
  2. Do Edit Universe and change instance type to i3.

You will still see Storage as EBS IO1 with the provisioned IOPs. i3 nodes come with their own local storage and do not use EBS.

Contributor guide

Research direction
Find the code path that handles instance type changes in the platform. Look for logic that determines storage type based on instance family. Investigate why i3 instances (local NVMe) still show EBS IO1 storage.
Tech stack
go
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70